This can be done as a rolling upgrade as we are currently running 1.7.5
which shares a majory version with 1.7.6.
Change-Id: Icd759967dc8a6a09d4db0a78d2dfef72042c171e
There have been a couple bug fix release between latest 1.7.x and 1.7.3
which we are running. Pull in this fixes in hopes that it makes shard
allocation more reliable.
Change-Id: I48f46663c73cb178ca3cf95a166b3df2ea121459
Instead of running curl in a cron, switch to the logstash::curator class
that runs a slightly more intelligent script with logging in /var/log.
Change-Id: Iba3c0726b789dcbcf58f2da071e6fa93d4cd67ae
Depends-On: Ic49c8649a0ad849a8d72900425e589e40b82a37f
We had to bump indices.breaker.fielddata.limit to 70% against the
running cluster in order for the elastic-recheck queries to run without
erroring due to not enough memory for the @timestamp field. Add this to
the config so that it persists across cluster installs.
Change-Id: Ia2f9c2ffff166bf3cc8f32c90b230249b3392406
Depends-On: I46c0cb5157aae40a0029ff1b425ecc663d171768
Since we do fine grained access control to the API via a proxy that
limits what requests can be made from anywhere go ahead and allow CORS
requests from anywhere as they won't be able to write data anyways.
This is useful so that you can test a new version of $tool hosted
locally against the actual cluster or for admins to run admin tools
hosted locally against the cluster.
Change-Id: I774d0ad0b246315794ab387acc39c41c7cfac3cd
Depends-On: I0aa8d5167c770c1024b7596da582d6cc089b1b47
The actual upgrade is handled by ansible but this will enforce the
correct version for any new host builds. This should be merged after the
ansible managed upgrade is complete.
Change-Id: Ieda9cdffe7486d24f17012de5fc094d18a45ec78
We were keeping 14 days of elasticsearch indexes. Unfortunately we are
running out of available disk space on our elasticsearch nodes and do
not have quota to add more volumes to increase available disk. Shift to
10 days of retention while we sort out how to get more disk.
Change-Id: I011d4f16f9a74e2eb7665ef66d2193e5fda476b7
Temporarily leave the old node names in place with an override to
16g heap size, but pass the openstack_project default of 30g into
the elasticsearch module as a new variable. Also don't actually
configure the new servers to install and run elasticsearch yet,
since there are manual steps needed to prep the additional block
devices on them.
Change-Id: I9fca2115c8996ae2f1a6c605bcdf16a8b6342a24
Upgrade to logstash 1.3.3 and ElasticSearch 0.90.9. Logstash 1.3.3 comes
with many performance improvements and bug fixes and needs ElasticSearch
0.90.9 to use the ElasticSearch output so upgrade ES as well. These
upgrades come with config changes for logstash as well to use new
features and disable others that are not wanted.
Change-Id: Ia180c5edfa755214a801f2cad06f091125814b0e
* modules/openstack_project/manifests/elasticsearch.pp: Upgrade
elasticsearch to 0.90.3 to support logstash 1.2.1. This version is
required to use the elasticsearch output in logstash 1.2.1.
* modules/elasticsearch/files/elasticsearch.mapping.json: Add setting
for new "message" field in logstash 1.2.1's new schema.
Change-Id: Ice1a8613ea11aeb954c600752a2de745dd56ef4b
To avoid namespace issues, rename openstack_project::elasticsearch
to openstack_project::elasticsearch_node.
Change-Id: Icd215cd0c13f06d279a477d0885d33665ce125ae
