{"action":"created","issue":{"url":"https://api.github.com/repos/chrislusf/vasto/issues/9","repository_url":"https://api.github.com/repos/chrislusf/vasto","labels_url":"https://api.github.com/repos/chrislusf/vasto/issues/9/labels{/name}","comments_url":"https://api.github.com/repos/chrislusf/vasto/issues/9/comments","events_url":"https://api.github.com/repos/chrislusf/vasto/issues/9/events","html_url":"https://github.com/chrislusf/vasto/issues/9","id":372191597,"node_id":"MDU6SXNzdWUzNzIxOTE1OTc=","number":9,"title":"Vasto primary/replica failure restore problem","user":{"login":"abv76","id":13469993,"node_id":"MDQ6VXNlcjEzNDY5OTkz","avatar_url":"https://avatars2.githubusercontent.com/u/13469993?v=4","gravatar_id":"","url":"https://api.github.com/users/abv76","html_url":"https://github.com/abv76","followers_url":"https://api.github.com/users/abv76/followers","following_url":"https://api.github.com/users/abv76/following{/other_user}","gists_url":"https://api.github.com/users/abv76/gists{/gist_id}","starred_url":"https://api.github.com/users/abv76/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/abv76/subscriptions","organizations_url":"https://api.github.com/users/abv76/orgs","repos_url":"https://api.github.com/users/abv76/repos","events_url":"https://api.github.com/users/abv76/events{/privacy}","received_events_url":"https://api.github.com/users/abv76/received_events","type":"User","site_admin":false},"labels":[],"state":"closed","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":3,"created_at":"2018-10-20T09:12:52Z","updated_at":"2018-10-25T01:14:24Z","closed_at":"2018-10-20T18:24:18Z","author_association":"NONE","body":"I tried to test vasto primary/replica failure restore latency with create cluster ks1 dc1 2 2.\r\nHowever，the created primary/replica store is both on the same store/process even I had added more than one store to the cluster，both primary/replica shard will shutdown in machine failure situation. \r\nIs it intentional setting？\r\nIn that case，how can I test the primary/replica failure restore latency？\r\n\r\nI manage to read the code，it seems that vasto client is only send its rocksDB requests to primary shard by default.\r\nIn case of primary hitch，vasto will update primary/replica using the PeriodicTask to synchronize the new rocksDB requests and replica router information to the client.\r\nSo the minimum failure restore latency will be time for primary/replica sync plus the PeriodicTask gap？\r\nCould you explain the primary/replica sync mechanism if I miss some thing？"},"comment":{"url":"https://api.github.com/repos/chrislusf/vasto/issues/comments/432879678","html_url":"https://github.com/chrislusf/vasto/issues/9#issuecomment-432879678","issue_url":"https://api.github.com/repos/chrislusf/vasto/issues/9","id":432879678,"node_id":"MDEyOklzc3VlQ29tbWVudDQzMjg3OTY3OA==","user":{"login":"abv76","id":13469993,"node_id":"MDQ6VXNlcjEzNDY5OTkz","avatar_url":"https://avatars2.githubusercontent.com/u/13469993?v=4","gravatar_id":"","url":"https://api.github.com/users/abv76","html_url":"https://github.com/abv76","followers_url":"https://api.github.com/users/abv76/followers","following_url":"https://api.github.com/users/abv76/following{/other_user}","gists_url":"https://api.github.com/users/abv76/gists{/gist_id}","starred_url":"https://api.github.com/users/abv76/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/abv76/subscriptions","organizations_url":"https://api.github.com/users/abv76/orgs","repos_url":"https://api.github.com/users/abv76/repos","events_url":"https://api.github.com/users/abv76/events{/privacy}","received_events_url":"https://api.github.com/users/abv76/received_events","type":"User","site_admin":false},"created_at":"2018-10-25T01:14:24Z","updated_at":"2018-10-25T01:14:24Z","author_association":"NONE","body":"> by default, the client always goes to the primary\r\n\r\nYes，I made a mistake，it should be  \r\n\r\n> It seems that **primary** will accumulate certain entries or wait for some time to push update queue instead of real time sync.\r\n\r\nTherefore，vasto is eventual consistency and require client to handle inconsistent situation？ @chrislusf "}}
{"actor":{"display_login":"abv76"}}