Commit message (Collapse) | Author | Age | Files | Lines | |
---|---|---|---|---|---|
* | configure kibana index mode | Jeff Cantrill | 2017-08-10 | 1 | -0/+2 |
| | |||||
* | Merge pull request #4364 from jcantrill/bz1457642_set_name_to_dc | OpenShift Bot | 2017-06-21 | 1 | -1/+2 |
|\ | | | | | Merged by openshift-bot | ||||
| * | bug 1457642. Use same SG index to avoid seeding timeout | Jeff Cantrill | 2017-06-14 | 1 | -1/+2 |
| | | |||||
* | | Ensure only one ES pod per PV | Peter Portante | 2017-06-16 | 1 | -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 kibana | Jeff Cantrill | 2017-06-06 | 1 | -0/+1 |
| | |||||
* | Pulling changes from master branch | ewolinetz | 2017-05-22 | 1 | -6/+5 |
| | |||||
* | Adding some missing changes | ewolinetz | 2017-05-22 | 1 | -1/+3 |
| | |||||
* | Pulling in changes from master | ewolinetz | 2017-05-22 | 1 | -2/+2 |
| | |||||
* | Decomposing openshift_logging role into subcomponent roles | ewolinetz | 2017-05-22 | 1 | -0/+80 |