|Resolved||EBernhardson||T183281 [epic] ELK upgrade to 6.x (elasticsearch, kibana, logstash)|
|Resolved||None||T183282 [epic] Search cluster upgrade to 6.x|
|Resolved||None||T194199 [Epic] Prepare for Elasticsearch 6 upgrade|
|Resolved||EBernhardson||T192614 Resolve current deprecation warnings in elasticsearch 5|
Surprisingly some of these warnings are simply for very old indices. Somehow commonswiki_general is dated feb 2017, although we've certainly done full reindexes since then. It's possible reindex failed somewhere and we never noticed, the logs for a reindex are so large we don't actually check they all succeed.
eqiad elasticsearch cluster (not logstash) was out of sync with the apifeatureusage template in puppet causing it to create indices with deprecation warnings. I've updated the template from the one in puppet and new indices going forward should not log deprecation warnings. Some day we have to figure out how those templates get from logstash to elasticsearch, somehow or another it wasn't auto-magically deployed (should it be?).
upgraded metastore on eqiad and codfw from 0.2 to 0.3 to fix more deprecation warnings about "index": "not_analyzed" which should be "index": "no". I'm not sure why but the minor upgrade didn't work so i forced a major (re-create and reindex) upgrade.
I think i've gone through all the deprecation warnings from the last week and either resolved or submitted patches for them. There is one remaining that I haven't been able to track down:
Native scripts are deprecated. Use a custom ScriptEngine to write scripts in java.
This is only being reported by nodes in the codfw cluster.
Rechecked the last weeks worth of logs, there are only 2 deprecation warnings both of which are acceptable. One is the phabricator index, it specifies an index property that has been removed in 6. It isn't a problem though, the index will continue to work in 6 and they are aware mappings need to be updated to work in 6. The other warning is related to our plugins, when a server starts it complains about using native scripts. This will be delt with when we upgrade the plugin to work with 6.