{"action":"closed","issue":{"url":"https://api.github.com/repos/coreos/etcd/issues/2800","labels_url":"https://api.github.com/repos/coreos/etcd/issues/2800/labels{/name}","comments_url":"https://api.github.com/repos/coreos/etcd/issues/2800/comments","events_url":"https://api.github.com/repos/coreos/etcd/issues/2800/events","html_url":"https://github.com/coreos/etcd/issues/2800","id":74193166,"number":2800,"title":"Request ignored due to cluster ID mismatch?","user":{"login":"hookenz","id":6227712,"avatar_url":"https://avatars.githubusercontent.com/u/6227712?v=3","gravatar_id":"","url":"https://api.github.com/users/hookenz","html_url":"https://github.com/hookenz","followers_url":"https://api.github.com/users/hookenz/followers","following_url":"https://api.github.com/users/hookenz/following{/other_user}","gists_url":"https://api.github.com/users/hookenz/gists{/gist_id}","starred_url":"https://api.github.com/users/hookenz/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/hookenz/subscriptions","organizations_url":"https://api.github.com/users/hookenz/orgs","repos_url":"https://api.github.com/users/hookenz/repos","events_url":"https://api.github.com/users/hookenz/events{/privacy}","received_events_url":"https://api.github.com/users/hookenz/received_events","type":"User","site_admin":false},"labels":[],"state":"closed","locked":false,"assignee":null,"milestone":null,"comments":3,"created_at":"2015-05-08T01:50:56Z","updated_at":"2015-05-08T06:20:40Z","closed_at":"2015-05-08T06:20:40Z","body":"I'm attempting to get etcd working correctly on 633.1.0 with an initial cluster of 5 machines.\r\n\r\nAs suggested previously I'm using etcd2 running inside a docker container.  In order to override the inbuilt etcd in 633.1.0 I created a service file in /etc/systemd/system\r\n\r\nI set my initial cluster size to 5 when creating the URL. So extra machines should fall into a proxy mode.  Does that work?\r\n\r\n/etc/systemd/system/etcd.service:\r\n\r\n    [Unit]\r\n    Description=etcd container\r\n    After=docker.service\r\n    Before=fleet.service\r\n\r\n    [Service]\r\n    Restart=always\r\n    RestartSec=10s\r\n    LimitNOFILE=40000\r\n    EnvironmentFile=/etc/environment\r\n    ExecStartPre=-/usr/bin/docker kill etcd\r\n    ExecStartPre=-/usr/bin/docker rm etcd\r\n    #ExecStartPre=/usr/bin/docker pull quay.io/coreos/etcd:v2.0.8\r\n    ExecStart=/usr/bin/docker run \\\r\n      -v /var/lib/etcd:/var/lib/etcd \\\r\n      -v /usr/share/ca-certificates/:/etc/ssl/certs \\\r\n      -p 4001:4001 -p 2380:2380 -p 2379:2379 --name etcd quay.io/coreos/etcd:v2.0.8 \\\r\n      -name %H \\\r\n      -data-dir /var/lib/etcd \\\r\n      -initial-advertise-peer-urls http://${COREOS_PRIVATE_IPV4}:2380 \\\r\n      -listen-peer-urls http://0.0.0.0:2380 \\\r\n      -discovery=https://***my unique discovery url***\r\n    ExecStop=/usr/bin/docker stop etcd\r\n\r\n    [Install]\r\n    WantedBy=multi-user.target\r\n\r\nIn order to allow restarting etcd, I'm setting the data directory and mounting it locally so it's not lost and it will allow me to hopefully switch to etcd2 when the native version comes out and I won't be needing to put it into docker.\r\n\r\nThe problem is however, it doesn't work.  The discovery URL is being populated, but I have these errors on my nodes repeated over and over again.\r\n\r\n    May 08 01:37:34 service2-3 docker[957]: 2015/05/08 01:37:34 rafthttp: request ignored due to cluster ID mismatch got a7c6bb9a1ba51b7d want 29ac8734ae277c83\r\n    May 08 01:37:45 service2-3 docker[957]: 2015/05/08 01:37:45 rafthttp: request ignored due to cluster ID mismatch got a7c6bb9a1ba51b7d want 29ac8734ae277c83\r\n\r\nCan someone please please write a recipe, or tell me what is the recommended way to start a cluster from CoreOS stable using etcd2 without switching to Alpha channel.  Or tell me what's wrong with the above.  \r\n\r\nIdeally, write some documentation on how to do it.  Since to switch to Alpha means to migrate my entire cluster.  I'm not going to do that.  I just want etcd2.   I can't use 0.4x, I don't think anyone can possibly run it for more than a few days without it crashing your hosts.  So how do I do it?  \r\n\r\nAnd please, more examples of running bare metal.  I'm using some scripts to populate COREOS_PRIVATE_IPV4 and doing the double-init thing.  That works."}}