{"action":"created","issue":{"url":"https://api.github.com/repos/openvstorage/framework/issues/1617","repository_url":"https://api.github.com/repos/openvstorage/framework","labels_url":"https://api.github.com/repos/openvstorage/framework/issues/1617/labels{/name}","comments_url":"https://api.github.com/repos/openvstorage/framework/issues/1617/comments","events_url":"https://api.github.com/repos/openvstorage/framework/issues/1617/events","html_url":"https://github.com/openvstorage/framework/issues/1617","id":224837504,"number":1617,"title":"ArakoonClient does not report new master after re-election but still reports old one","user":{"login":"jtorreke","id":18348187,"avatar_url":"https://avatars2.githubusercontent.com/u/18348187?v=3","gravatar_id":"","url":"https://api.github.com/users/jtorreke","html_url":"https://github.com/jtorreke","followers_url":"https://api.github.com/users/jtorreke/followers","following_url":"https://api.github.com/users/jtorreke/following{/other_user}","gists_url":"https://api.github.com/users/jtorreke/gists{/gist_id}","starred_url":"https://api.github.com/users/jtorreke/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/jtorreke/subscriptions","organizations_url":"https://api.github.com/users/jtorreke/orgs","repos_url":"https://api.github.com/users/jtorreke/repos","events_url":"https://api.github.com/users/jtorreke/events{/privacy}","received_events_url":"https://api.github.com/users/jtorreke/received_events","type":"User","site_admin":false},"labels":[{"id":239189397,"url":"https://api.github.com/repos/openvstorage/framework/labels/state_question","name":"state_question","color":"c2e0c6","default":false}],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":3,"created_at":"2017-04-27T16:14:05Z","updated_at":"2017-04-28T07:52:38Z","closed_at":null,"body":"I found this whilst fiddling with the arakoon support tools part. The ArakoonClient does not report the current/new master after a re-election. The situation at the start:\r\n\r\nIn [68]: arakoonclient.whoMaster()\r\nOut[68]: 'Zuaq8gS2erJqNM0N'\r\n\r\n2017-04-27 17:59:41 026184 +0200 - ovs-node03-1604 - 6961/0000 - arakoon - 1467 - info - Zuaq8gS2erJqNM0N is master\r\n\r\nAfter using the --drop-master functionality of arakoon, a new master is elected:\r\n\r\n2017-04-27 18:04:44 215042 +0200 - ovs-node03-1604 - 6961/0000 - arakoon - 1494 - info - connection=10.100.199.183:client_service_41 DROP_MASTER\r\n2017-04-27 18:05:43 185928 +0200 - ovs-node03-1604 - 6961/0000 - arakoon - 1564 - info - wRvFcy0LkY3TOHXD is master\r\n\r\nChecking again with the ArakoonClient:\r\n\r\nIn [72]: arakoonclient.whoMaster()\r\nOut[72]: 'Zuaq8gS2erJqNM0N'\r\n\r\nIn [73]: arakoonclient = ArakoonClient(conf)\r\n\r\nIn [74]: arakoonclient.whoMaster()\r\nOut[74]: 'wRvFcy0LkY3TOHXD'\r\n\r\nOnly after re-creating the ArakoonClient, I was able to retrieve the current master. I'm assuming this is not expected behavior or am I missing something?"},"comment":{"url":"https://api.github.com/repos/openvstorage/framework/issues/comments/297932847","html_url":"https://github.com/openvstorage/framework/issues/1617#issuecomment-297932847","issue_url":"https://api.github.com/repos/openvstorage/framework/issues/1617","id":297932847,"user":{"login":"toolslive","id":1249832,"avatar_url":"https://avatars3.githubusercontent.com/u/1249832?v=3","gravatar_id":"","url":"https://api.github.com/users/toolslive","html_url":"https://github.com/toolslive","followers_url":"https://api.github.com/users/toolslive/followers","following_url":"https://api.github.com/users/toolslive/following{/other_user}","gists_url":"https://api.github.com/users/toolslive/gists{/gist_id}","starred_url":"https://api.github.com/users/toolslive/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/toolslive/subscriptions","organizations_url":"https://api.github.com/users/toolslive/orgs","repos_url":"https://api.github.com/users/toolslive/repos","events_url":"https://api.github.com/users/toolslive/events{/privacy}","received_events_url":"https://api.github.com/users/toolslive/received_events","type":"User","site_admin":false},"created_at":"2017-04-28T07:52:38Z","updated_at":"2017-04-28T07:52:38Z","body":"It can happen a client thinks the wrong node is master. \r\nThe next call that uses that assumed master node and needs it to be master will fail on server side, \r\nand that exception should be picked up by the client which should then correct its inner state. \r\nThus far, the reported behaviour does not look like a bug."}}
{"actor":{"display_login":"toolslive"}}