{"action":"created","issue":{"url":"https://api.github.com/repos/coreos/etcd/issues/7032","repository_url":"https://api.github.com/repos/coreos/etcd","labels_url":"https://api.github.com/repos/coreos/etcd/issues/7032/labels{/name}","comments_url":"https://api.github.com/repos/coreos/etcd/issues/7032/comments","events_url":"https://api.github.com/repos/coreos/etcd/issues/7032/events","html_url":"https://github.com/coreos/etcd/issues/7032","id":196305946,"number":7032,"title":"cluster-health reports healthy with contradictory output","user":{"login":"stresler","id":1053894,"avatar_url":"https://avatars.githubusercontent.com/u/1053894?v=3","gravatar_id":"","url":"https://api.github.com/users/stresler","html_url":"https://github.com/stresler","followers_url":"https://api.github.com/users/stresler/followers","following_url":"https://api.github.com/users/stresler/following{/other_user}","gists_url":"https://api.github.com/users/stresler/gists{/gist_id}","starred_url":"https://api.github.com/users/stresler/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/stresler/subscriptions","organizations_url":"https://api.github.com/users/stresler/orgs","repos_url":"https://api.github.com/users/stresler/repos","events_url":"https://api.github.com/users/stresler/events{/privacy}","received_events_url":"https://api.github.com/users/stresler/received_events","type":"User","site_admin":false},"labels":[],"state":"closed","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":14,"created_at":"2016-12-18T23:11:17Z","updated_at":"2016-12-19T00:59:49Z","closed_at":"2016-12-18T23:23:53Z","body":"I don't see how this can be a logical output: \r\n\r\n```\r\n/ # etcdctl --ca-file /etc/kubernetes/ssl/ca.pem  --endpoint https://etcd0.DOMAIN.com:2379 cluster-health\r\nmember 7641137365309009 is unhealthy: got unhealthy result from https://etcd1.DOMAIN.com:2379\r\nmember 7e51c10fd2e88c9c is unreachable: no available published client urls\r\nmember abeec58727dc4111 is healthy: got healthy result from https://etcd2.DOMAIN.com:2379\r\nmember c5decd33b4e6bcf9 is unhealthy: got unhealthy result from https://etcd0.DOMAIN.com:2379\r\nmember fb7b0b7455c4e5df is unreachable: no available published client urls\r\ncluster is healthy\r\n```"},"comment":{"url":"https://api.github.com/repos/coreos/etcd/issues/comments/267860748","html_url":"https://github.com/coreos/etcd/issues/7032#issuecomment-267860748","issue_url":"https://api.github.com/repos/coreos/etcd/issues/7032","id":267860748,"user":{"login":"xiang90","id":4479947,"avatar_url":"https://avatars.githubusercontent.com/u/4479947?v=3","gravatar_id":"","url":"https://api.github.com/users/xiang90","html_url":"https://github.com/xiang90","followers_url":"https://api.github.com/users/xiang90/followers","following_url":"https://api.github.com/users/xiang90/following{/other_user}","gists_url":"https://api.github.com/users/xiang90/gists{/gist_id}","starred_url":"https://api.github.com/users/xiang90/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/xiang90/subscriptions","organizations_url":"https://api.github.com/users/xiang90/orgs","repos_url":"https://api.github.com/users/xiang90/repos","events_url":"https://api.github.com/users/xiang90/events{/privacy}","received_events_url":"https://api.github.com/users/xiang90/received_events","type":"User","site_admin":false},"created_at":"2016-12-19T00:59:49Z","updated_at":"2016-12-19T00:59:49Z","body":"> For a point of comparison, suppose you have a RAID6 and two drives are toast, do you want your RAID to happily chirp \"healthy\"?\r\n\r\nI do not say it is the best way to define \"healthy\". It is the expected output based on the current definition.\r\n\r\n> Going by this health analogy, isn't it more useful to know you're sick before waiting until you drop dead?\r\n\r\nI agree the whole thing (cluster healthy) lacks clear definition.\r\n\r\nNeither\r\n\r\n- 1 member healthy -> cluster healthy \r\n\r\nnor\r\n\r\n- only member healthy from the client POV -> cluster healthy\r\n\r\nmake sense to me.\r\n\r\nI feel that simply giving the output from each member checking to users is good enough. Thus we have endpoint status instead of cluster health command in v3.\r\n\r\nI do not really want etcdctl to interpret the meaning of the combined output to generate one simple sentence, which will be hard to understand without providing additional context.\r\n\r\nIf you want to have that cluster healthy output and ensure it make sense, I would suggest that we document its meaning somewhere before move forward.\r\n\r\n"}}
{"actor":{"display_login":"xiang90"}}