we have recently upgraded our ES cluster (12 nodes, ~900GB data) from
0.90.9 to 1.4.2. We did a restart-upgrade, so backup data and then start
the new ES version with the old data directories.
Since then we're seeing lot of messages like "re-syncing mappings with
cluster state for types ..." in the log of the master node, about 5-10
every second (Once for each index). The load and network traffic on the
machines also seems to have increased quite a bit.
Some googling showed me various older (0.17/0.18) questions about this, and
that it's related to serialization of the mapping. Our mapping is here:
One suggested quick fix i found was to close/re-open the affected indices.
Other suggestions? Or tips how to debug why this is going wrong, and what
to change in the mapping?
How serious is this? Does this need immediate attention, or should the
cluster survive for a while?
You received this message because you are subscribed to the Google Groups "elasticsearch" group.
To unsubscribe from this group and stop receiving emails from it, send an email to email@example.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/elasticsearch/de51ebc3-ca47-475c-914d-91d7a747e69e%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.