{"action":"created","issue":{"url":"https://api.github.com/repos/open-iscsi/tcmu-runner/issues/366","repository_url":"https://api.github.com/repos/open-iscsi/tcmu-runner","labels_url":"https://api.github.com/repos/open-iscsi/tcmu-runner/issues/366/labels{/name}","comments_url":"https://api.github.com/repos/open-iscsi/tcmu-runner/issues/366/comments","events_url":"https://api.github.com/repos/open-iscsi/tcmu-runner/issues/366/events","html_url":"https://github.com/open-iscsi/tcmu-runner/issues/366","id":292669785,"number":366,"title":"[ERROR] tcmu_rbd_lock_break:580 rbd/rbd.suse-disk1: Could not break lock from 1.1.1.15:0/2742851101","user":{"login":"vatelzh","id":5194775,"avatar_url":"https://avatars0.githubusercontent.com/u/5194775?v=4","gravatar_id":"","url":"https://api.github.com/users/vatelzh","html_url":"https://github.com/vatelzh","followers_url":"https://api.github.com/users/vatelzh/followers","following_url":"https://api.github.com/users/vatelzh/following{/other_user}","gists_url":"https://api.github.com/users/vatelzh/gists{/gist_id}","starred_url":"https://api.github.com/users/vatelzh/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/vatelzh/subscriptions","organizations_url":"https://api.github.com/users/vatelzh/orgs","repos_url":"https://api.github.com/users/vatelzh/repos","events_url":"https://api.github.com/users/vatelzh/events{/privacy}","received_events_url":"https://api.github.com/users/vatelzh/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":9,"created_at":"2018-01-30T06:43:42Z","updated_at":"2018-02-02T01:34:25Z","closed_at":null,"author_association":"NONE","body":"I'm usring ceph12.2.2 and tcmu-runner master branch and multipath for suse11, after I run fio for one night, logout the sessiones and login again, one path can not be logged in successfully, check the tcmu log, this log message is printed per second."},"comment":{"url":"https://api.github.com/repos/open-iscsi/tcmu-runner/issues/comments/362458308","html_url":"https://github.com/open-iscsi/tcmu-runner/issues/366#issuecomment-362458308","issue_url":"https://api.github.com/repos/open-iscsi/tcmu-runner/issues/366","id":362458308,"user":{"login":"mikechristie","id":1063316,"avatar_url":"https://avatars2.githubusercontent.com/u/1063316?v=4","gravatar_id":"","url":"https://api.github.com/users/mikechristie","html_url":"https://github.com/mikechristie","followers_url":"https://api.github.com/users/mikechristie/followers","following_url":"https://api.github.com/users/mikechristie/following{/other_user}","gists_url":"https://api.github.com/users/mikechristie/gists{/gist_id}","starred_url":"https://api.github.com/users/mikechristie/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/mikechristie/subscriptions","organizations_url":"https://api.github.com/users/mikechristie/orgs","repos_url":"https://api.github.com/users/mikechristie/repos","events_url":"https://api.github.com/users/mikechristie/events{/privacy}","received_events_url":"https://api.github.com/users/mikechristie/received_events","type":"User","site_admin":false},"created_at":"2018-02-02T01:34:25Z","updated_at":"2018-02-02T01:34:25Z","author_association":"COLLABORATOR","body":">okay... from the initiator side, using multipath -ll, we can see the weight of one path is 50, and another one is 10, I want to re-weight them to such as 200: 10.\r\n\r\nBy default when we use ALUA, the weights are based on the ALUA state. You can override this on the initiator side. Check out the weighteddeph prio in the multipath.conf man page. You can basically set the prio to whatever you want based on whatever values are available to you like ip address, port state, target/image name, etc.\r\n\r\n> Is there any known issue if using kernel 4.14 without your patch sets?\r\n\r\nIf you send more data than can fit in the tcmu device ring, commands will get put on a internal queue until other commands complete and free enough space. If we were to failover to another node at this time, the commands sitting in that internal queue might not get flushed and they might execute after new commands have completed on the new node we failed over too. You will probably not hit this normally because the default buffer side is like 1 gig, so you have plenty of memory for normal commands.\r\n\r\nThe patches basically allow you to configure the ring buffer size, how long you want commands to wait on that internal queue and allow tcmu-runner to flush/kill those commands.\r\n\r\nSo they should not actually help the issue you are seeing.\r\n\r\nI am trying to replicate the problem here now.\r\n"}}
{"actor":{"display_login":"mikechristie"}}