{"action":"opened","issue":{"url":"https://api.github.com/repos/apple/foundationdb/issues/317","repository_url":"https://api.github.com/repos/apple/foundationdb","labels_url":"https://api.github.com/repos/apple/foundationdb/issues/317/labels{/name}","comments_url":"https://api.github.com/repos/apple/foundationdb/issues/317/comments","events_url":"https://api.github.com/repos/apple/foundationdb/issues/317/events","html_url":"https://github.com/apple/foundationdb/issues/317","id":320932515,"number":317,"title":"Monitor leader should not wait for a majority before attempting to communicate with the cluster controller","user":{"login":"etschannen","id":36455792,"avatar_url":"https://avatars0.githubusercontent.com/u/36455792?v=4","gravatar_id":"","url":"https://api.github.com/users/etschannen","html_url":"https://github.com/etschannen","followers_url":"https://api.github.com/users/etschannen/followers","following_url":"https://api.github.com/users/etschannen/following{/other_user}","gists_url":"https://api.github.com/users/etschannen/gists{/gist_id}","starred_url":"https://api.github.com/users/etschannen/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/etschannen/subscriptions","organizations_url":"https://api.github.com/users/etschannen/orgs","repos_url":"https://api.github.com/users/etschannen/repos","events_url":"https://api.github.com/users/etschannen/events{/privacy}","received_events_url":"https://api.github.com/users/etschannen/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":0,"created_at":"2018-05-07T19:49:33Z","updated_at":"2018-05-07T19:49:33Z","closed_at":null,"author_association":"COLLABORATOR","body":"This is an optimization which will improve client and server connection times to the cluster controller, especially in multiple DC configurations. Currently, we ask all coordinators for who the cluster controller is, and once we have a majority answer we know that server if the cluster controller. \r\n\r\nInstead, we should optimistically assume the first reply we get from the coordinators is the correct answer and begin contacting them as if they were the cluster controller.\r\n\r\nThis should be done in both MonitorLeader.actor.cpp for clients and LeaderElection.actor.cpp for servers."}}
{"actor":{"display_login":"etschannen"}}