{"action":"created","issue":{"url":"https://api.github.com/repos/openshift/mongodb/issues/140","repository_url":"https://api.github.com/repos/openshift/mongodb","labels_url":"https://api.github.com/repos/openshift/mongodb/issues/140/labels{/name}","comments_url":"https://api.github.com/repos/openshift/mongodb/issues/140/comments","events_url":"https://api.github.com/repos/openshift/mongodb/issues/140/events","html_url":"https://github.com/openshift/mongodb/issues/140","id":141039493,"number":140,"title":"Replica Set initialization without election","user":{"login":"rhcarvalho","id":88819,"avatar_url":"https://avatars.githubusercontent.com/u/88819?v=3","gravatar_id":"","url":"https://api.github.com/users/rhcarvalho","html_url":"https://github.com/rhcarvalho","followers_url":"https://api.github.com/users/rhcarvalho/followers","following_url":"https://api.github.com/users/rhcarvalho/following{/other_user}","gists_url":"https://api.github.com/users/rhcarvalho/gists{/gist_id}","starred_url":"https://api.github.com/users/rhcarvalho/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/rhcarvalho/subscriptions","organizations_url":"https://api.github.com/users/rhcarvalho/orgs","repos_url":"https://api.github.com/users/rhcarvalho/repos","events_url":"https://api.github.com/users/rhcarvalho/events{/privacy}","received_events_url":"https://api.github.com/users/rhcarvalho/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":1,"created_at":"2016-03-15T17:10:23Z","updated_at":"2016-03-15T21:05:26Z","closed_at":null,"body":"In a conversation with @php-coder today he brought an excellent question and idea:\r\n\r\nWhy does the pod running the replica set initiation code starts as a PRIMARY member, and then it steps down and triggers an election among the other members?\r\n\r\nIt would be much simpler if the post-deployment-hook pod simply pick one of the deployed pods and make it the primary, run all the initialization steps, add the other pods to the replica set, and quit. The hook pod don't need to run `mongod`.\r\n\r\nThis idea could simplify matters greatly, reduce the startup time, and reduce the surface area for bugs."},"comment":{"url":"https://api.github.com/repos/openshift/mongodb/issues/comments/197018763","html_url":"https://github.com/openshift/mongodb/issues/140#issuecomment-197018763","issue_url":"https://api.github.com/repos/openshift/mongodb/issues/140","id":197018763,"user":{"login":"grdryn","id":442386,"avatar_url":"https://avatars.githubusercontent.com/u/442386?v=3","gravatar_id":"","url":"https://api.github.com/users/grdryn","html_url":"https://github.com/grdryn","followers_url":"https://api.github.com/users/grdryn/followers","following_url":"https://api.github.com/users/grdryn/following{/other_user}","gists_url":"https://api.github.com/users/grdryn/gists{/gist_id}","starred_url":"https://api.github.com/users/grdryn/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/grdryn/subscriptions","organizations_url":"https://api.github.com/users/grdryn/orgs","repos_url":"https://api.github.com/users/grdryn/repos","events_url":"https://api.github.com/users/grdryn/events{/privacy}","received_events_url":"https://api.github.com/users/grdryn/received_events","type":"User","site_admin":false},"created_at":"2016-03-15T21:05:26Z","updated_at":"2016-03-15T21:05:26Z","body":"Sounds good. There's an issue that I've seen a sometimes where the initiator details are still in the members list even after it drops out. This should at least cover that! :+1: "}}