summaryrefslogtreecommitdiffstats
path: root/roles/openshift_logging_elasticsearch/templates/elasticsearch.yml.j2
Commit message (Collapse)AuthorAgeFilesLines
* Adding support for ES 5.x tech preview opt inEric Wolinetz2018-02-051-87/+0
|
* elasticsearch: reintroduce readiness probeJan Wozniak2017-08-291-1/+2
|
* configure kibana index modeJeff Cantrill2017-08-101-0/+2
|
* Merge pull request #4364 from jcantrill/bz1457642_set_name_to_dcOpenShift Bot2017-06-211-1/+2
|\ | | | | Merged by openshift-bot
| * bug 1457642. Use same SG index to avoid seeding timeoutJeff Cantrill2017-06-141-1/+2
| |
* | Ensure only one ES pod per PVPeter Portante2017-06-161-0/+1
|/ | | | | | | | | | | | | | 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.
* specify all logging index mappings for kibanaJeff Cantrill2017-06-061-0/+1
|
* Pulling changes from master branchewolinetz2017-05-221-6/+5
|
* Adding some missing changesewolinetz2017-05-221-1/+3
|
* Pulling in changes from masterewolinetz2017-05-221-2/+2
|
* Decomposing openshift_logging role into subcomponent rolesewolinetz2017-05-221-0/+80