summaryrefslogtreecommitdiffstats
path: root/.yamllint
diff options
context:
space:
mode:
authorPeter Portante <peter.portante@redhat.com>2017-06-15 14:08:45 -0400
committerPeter Portante <peter.portante@redhat.com>2017-06-16 10:37:32 -0400
commitfd165fe201abb5fbd76306a16febaf1cb3c8ad0b (patch)
treedad357c31f092177aa5265a4b574158d2a685e7c /.yamllint
parent0862f7b6f1448d6ea1fe6c836b3ba1de0afb4485 (diff)
downloadopenshift-fd165fe201abb5fbd76306a16febaf1cb3c8ad0b.tar.gz
openshift-fd165fe201abb5fbd76306a16febaf1cb3c8ad0b.tar.bz2
openshift-fd165fe201abb5fbd76306a16febaf1cb3c8ad0b.tar.xz
openshift-fd165fe201abb5fbd76306a16febaf1cb3c8ad0b.zip
Ensure only one ES pod per PV
bug 1460564. Fixes [BZ #1460564](https://bugzilla.redhat.com/show_bug.cgi?id=1460564). Unfortunately, the defaults for Elasticsearch prior to v5 allow more than one "node" to access the same configured storage volume(s). This change forces this value to 1 to ensure we don't have an ES pod starting up accessing a volume while another ES pod is shutting down when reploying. This can lead to "1" directories being created in `/elasticsearch/persistent/${CLUSTER_NAME}/data/${CLUSTER_NAME}/nodes/`. By default ES uses a "0" directory there when only one node is accessing it.
Diffstat (limited to '.yamllint')
0 files changed, 0 insertions, 0 deletions