{"action":"opened","issue":{"url":"https://api.github.com/repos/pires/kubernetes-elasticsearch-cluster/issues/2","labels_url":"https://api.github.com/repos/pires/kubernetes-elasticsearch-cluster/issues/2/labels{/name}","comments_url":"https://api.github.com/repos/pires/kubernetes-elasticsearch-cluster/issues/2/comments","events_url":"https://api.github.com/repos/pires/kubernetes-elasticsearch-cluster/issues/2/events","html_url":"https://github.com/pires/kubernetes-elasticsearch-cluster/issues/2","id":56254308,"number":2,"title":"How would we use GCE PersistentDisk?","user":{"login":"jasonkuhrt","id":284476,"avatar_url":"https://avatars.githubusercontent.com/u/284476?v=3","gravatar_id":"","url":"https://api.github.com/users/jasonkuhrt","html_url":"https://github.com/jasonkuhrt","followers_url":"https://api.github.com/users/jasonkuhrt/followers","following_url":"https://api.github.com/users/jasonkuhrt/following{/other_user}","gists_url":"https://api.github.com/users/jasonkuhrt/gists{/gist_id}","starred_url":"https://api.github.com/users/jasonkuhrt/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/jasonkuhrt/subscriptions","organizations_url":"https://api.github.com/users/jasonkuhrt/orgs","repos_url":"https://api.github.com/users/jasonkuhrt/repos","events_url":"https://api.github.com/users/jasonkuhrt/events{/privacy}","received_events_url":"https://api.github.com/users/jasonkuhrt/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":0,"created_at":"2015-02-02T16:00:32Z","updated_at":"2015-02-02T16:00:32Z","closed_at":null,"body":"The Kubernetes `volumes` docs have information about the currently supported source types:\r\n\r\nhttps://github.com/GoogleCloudPlatform/kubernetes/blob/master/docs/volumes.md#gcepersistentdisk\r\n\r\nWhat we want is the Elasticsearch cluster to have a data node that has *lots* of disk space. We need a persistent disk for this. The only one supported right now is GCE PD. But there is a limitation with it, right now:\r\n\r\n> avoid creating multiple pods that use the same Volume\r\nif multiple pods refer to the same Volume and both are scheduled on the same machine, regardless of whether they are read-only or read-write, then the second pod scheduled will fail.\r\nReplication controllers can only be created for pods that use read-only mounts.\r\n\r\nThis means that your pattern of a data node behind a `replicationController` would fail because by design it tries to replicate multiple pods sharing a disk. That works with the current `emptyDir` setup but that same setup fails the use-case of needing a *persistent* and *large* disk.\r\n\r\nMy suggestion right now is to limit the `replicationController` replica count to `1` and switch over to use a GCE PD."}}