{"action":"opened","issue":{"url":"https://api.github.com/repos/openvstorage/volumedriver/issues/267","repository_url":"https://api.github.com/repos/openvstorage/volumedriver","labels_url":"https://api.github.com/repos/openvstorage/volumedriver/issues/267/labels{/name}","comments_url":"https://api.github.com/repos/openvstorage/volumedriver/issues/267/comments","events_url":"https://api.github.com/repos/openvstorage/volumedriver/issues/267/events","html_url":"https://github.com/openvstorage/volumedriver/issues/267","id":207556084,"number":267,"title":"Volumedriver fails to steal volume because volume DTL is not in sync while it is","user":{"login":"kinvaris","id":4190375,"avatar_url":"https://avatars.githubusercontent.com/u/4190375?v=3","gravatar_id":"","url":"https://api.github.com/users/kinvaris","html_url":"https://github.com/kinvaris","followers_url":"https://api.github.com/users/kinvaris/followers","following_url":"https://api.github.com/users/kinvaris/following{/other_user}","gists_url":"https://api.github.com/users/kinvaris/gists{/gist_id}","starred_url":"https://api.github.com/users/kinvaris/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/kinvaris/subscriptions","organizations_url":"https://api.github.com/users/kinvaris/orgs","repos_url":"https://api.github.com/users/kinvaris/repos","events_url":"https://api.github.com/users/kinvaris/events{/privacy}","received_events_url":"https://api.github.com/users/kinvaris/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":0,"created_at":"2017-02-14T15:57:13Z","updated_at":"2017-02-14T15:57:13Z","closed_at":null,"body":"In this situation we have 4 nodes with a vPool. The DTL is in sync. 2 Nodes are living in the same domain so between those nodes we are performing HA (Node 2 -> Node 4).\r\n* A vdisk is present on the vpool on node 2\r\n* The vdisk is expected to HA migrate to node 4\r\n* Node 2 is cleanly shutdown\r\n* The vdisk is not being stolen from Node 2 because the DTL is not in sync\r\n\r\n@redlicha has the following hypothesis: \r\n```\r\n* client is connected to .192\r\n* .192 is shut down cleanly -> first the xio server\r\n* client connects to .194, is able to open the volume, redirection between .192 and .194 while the former is not fully down yet. the dtl-in-sync status is not transferred for redirected requests (by default for backward compat purposes, can / should be switched on) -> \"false\" is assumed. \r\n* eventually the interprocess comm is also shut down -> stealing is now attempted, but the dtl-in-sync status doesn't allow it\r\n```\r\n\r\nPossible solution:\r\n```\r\n* what I think is happening in your test is the above race. So, what you can do is either kill the voldrv (or the complete node) hard\r\n* and/or also set volume_router/vrouter_send_sync_response to 'true' in the config of all nodes. (that one defaults to false for backward compat purposes)\r\n\r\nnew voldrvs should be able to deal with it, i.e. anything >= 6.3.0 (minus bugs) if the second solution is performed\r\n```\r\n\r\n"}}
{"actor":{"display_login":"kinvaris"}}