Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Use Persistent Volumes by default for ES nodes #913

Closed
nkvoll opened this issue May 23, 2019 · 0 comments · Fixed by #1028
Closed

Use Persistent Volumes by default for ES nodes #913

nkvoll opened this issue May 23, 2019 · 0 comments · Fixed by #1028
Assignees

Comments

@nkvoll
Copy link
Member

nkvoll commented May 23, 2019

By default, we're currently using emptyDir, which isn't particularly suitable for ES. The tradeoff is generally that emptyDir is not safe, PersistentVolumes by default may have worse performance.

Since most (all?) K8s distributions come with a default storage class, we can make it the default (i.e if nothing regarding data volumes are specified, we'll create a PVC).

@nkvoll nkvoll self-assigned this Jun 8, 2019
nkvoll added a commit to nkvoll/cloud-on-k8s that referenced this issue Jun 8, 2019
By default they will get a 1Gi volume, which is chosen because matches roughly 1:1 vs the default heap.

Users can opt out of this behavior by specifying the data volume in the Elasticsearch resource directly

```yaml
apiVersion: elasticsearch.k8s.elastic.co/v1alpha1
kind: Elasticsearch
metadata:
  name: elasticsearch-sample
spec:
  version: "7.1.0"
  nodes:
  - nodeCount: 1
    podTemplate:
      spec:
        volumes:
        - name: elasticsearch-data
          emptyDir: {}
```

Builds on top of elastic#1024

Closes: elastic#913
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant