| Status | Subtype | Assigned | Task | ||
|---|---|---|---|---|---|
| Resolved | bd808 | T137400 Logstash elasticsearch mapping does not allow err.code to be a string | |||
| Resolved | dcausse | T138608 Vagrant role provisions wrong elasticsearch version | |||
| Resolved | debt | T136001 [EPIC] Upgrade elasticsearch cluster supporting logging to 2.3 | |||
| Resolved | EBernhardson | T136003 Upgrade logstash*.eqiad.wmnet elasticsearch servers to 2.3 | |||
| Resolved | EBernhardson | T136002 Test logstash 1.5.3 and kibana 3.1.2 against elasticsearch 2.3 | |||
| Resolved | EBernhardson | T138330 Update logstash mapping templates to work with elasticsearch 2.x | |||
| Resolved | EBernhardson | T138335 Backport de_dot plugin for logstash to 1.5.3 | |||
| Resolved | EBernhardson | T138539 Restbase math server and mediawiki EventBus have conflicting log mappings for "response" |
Event Timeline
Ideally we would do this this quarter, but it doesn't really block anything and isn't directly in for our goals.
As long as the production Puppet and apt configuration for the Elasticsearch modules continue to support the 1.7.x series that is probably true. As soon as your engineers need to make a breaking change however it will become someone's problem.
Couple issues when attempting to convert a test instance in labs with 2 days of data from 1.7 to 2.3. Installed the 1.x->2.0 migration plugin to check, we have a few issues that need to be resolved (probably by munging things in logstash before sending them on):
Mapping for field hhvm:line conflicts with: restbase:line. Check parameters: norms.enabled, type
Mapping for field hhvm:line conflicts with: mw-ocg-service:line. Check parameters: norms.enabled, type
Mapping for field apache2:pid conflicts with: citoid:pid. Check parameters: norms.enabled, type
Mapping for field apache2:pid conflicts with: cxserver:pid. Check parameters: norms.enabled, type
Mapping for field apache2:pid conflicts with: mw-ocg-service:pid. Check parameters: norms.enabled, type
Mapping for field apache2:pid conflicts with: parsoid:pid. Check parameters: norms.enabled, type
Mapping for field apache2:pid conflicts with: restbase:pid. Check parameters: norms.enabled, type
Mapping for field apache2:timestamp conflicts with: mediawiki:timestamp. Check parameters: format, norms.enabled, type
Similar to when we deployed es 2.3 for search, the elasticsearch::publish_host hiera variable needs to be set appropriately, or it will only bind to the lo interface