{"action":"closed","issue":{"url":"https://api.github.com/repos/gluster/glusterd2/issues/1046","repository_url":"https://api.github.com/repos/gluster/glusterd2","labels_url":"https://api.github.com/repos/gluster/glusterd2/issues/1046/labels{/name}","comments_url":"https://api.github.com/repos/gluster/glusterd2/issues/1046/comments","events_url":"https://api.github.com/repos/gluster/glusterd2/issues/1046/events","html_url":"https://github.com/gluster/glusterd2/issues/1046","id":342971740,"node_id":"MDU6SXNzdWUzNDI5NzE3NDA=","number":1046,"title":"Need consistent gluster volume status","user":{"login":"pranithk","id":450543,"node_id":"MDQ6VXNlcjQ1MDU0Mw==","avatar_url":"https://avatars3.githubusercontent.com/u/450543?v=4","gravatar_id":"","url":"https://api.github.com/users/pranithk","html_url":"https://github.com/pranithk","followers_url":"https://api.github.com/users/pranithk/followers","following_url":"https://api.github.com/users/pranithk/following{/other_user}","gists_url":"https://api.github.com/users/pranithk/gists{/gist_id}","starred_url":"https://api.github.com/users/pranithk/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/pranithk/subscriptions","organizations_url":"https://api.github.com/users/pranithk/orgs","repos_url":"https://api.github.com/users/pranithk/repos","events_url":"https://api.github.com/users/pranithk/events{/privacy}","received_events_url":"https://api.github.com/users/pranithk/received_events","type":"User","site_admin":false},"labels":[{"id":131833775,"node_id":"MDU6TGFiZWwxMzE4MzM3NzU=","url":"https://api.github.com/repos/gluster/glusterd2/labels/duplicate","name":"duplicate","color":"cccccc","default":true}],"state":"closed","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":2,"created_at":"2018-07-20T04:44:32Z","updated_at":"2018-07-20T07:11:32Z","closed_at":"2018-07-20T07:11:32Z","author_association":"MEMBER","body":"For monitoring glusterfs volumes, we need gluster volume status output every X seconds (at the moment X is 30 seconds) Based on my discussions with @prashanthpai, at the moment volume status doesn't take any lock while getting the status of the bricks etc, so there is a possibility of getting a snapshot of status that is not consistent while say volume stop is in progress. Goal is to be able to build alerts to the admin/users based on this output and if for any reason we capture volume status while a volume stop is in progress, there is a chance of seeing some bricks that are down and that can lead to alerts to the user which are not intended. It is also important to not fail volume status command when another transaction is in progress as that will also prevent monitoring from happening. I want to understand if we can make changes in gd2 to achieve this goal of easier integration by monitoring tools for observing volume status continuously and add alerts that won't give any false +ves.\r\n\r\n@kshlm @aravindavk @atinmu @prashanthpai Any thoughts?"}}
{"actor":{"display_login":"pranithk"}}