New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Endless mapping re-sync problem #7215
Comments
Hi @AVVS How many nodes are you running? Could you add the relevant logs from the other nodes? Do you have the same version of ES on all nodes? And the same version of the JVM? Same version of the ICU plugin? I presume you are actively indexing into this index? Does this message stop if you stop indexing? |
I'm indexing a lot, but this message has, sadly, nothing to do with it. If I stop it persists. One easy way to trigger it sooner is to add more replicas to the index. Other nodes dont really have anything interesting: Master nodes have last messages from the 4 days ago about adding a node to the cluster except for the actual elected master. HTTP nodes dont have anything, data nodes have GC message from some 8 hours ago |
One more thing: if I look at
|
If you close the dangling indices, does it stop then? Probably not, but worth a try. For some reason the code in question thinks that your mapping has changed. I'm wondering if there is something that you've specified which isn't properly handled by the equals() method. |
I cant really close those dangling indices, they are not yet available:
What data can I provide to help with testing this? |
Not sure yet - I'll come back to you with more. |
I've reduced this to the following, which reproduces the problem:
When it tries to compare the mappings here https://github.com/elasticsearch/elasticsearch/blob/master/src/main/java/org/elasticsearch/cluster/metadata/MetaDataMappingService.java#L270 the fields are in a different order.
|
Ok, any easy fix to temporarily allow it to sync properly? i.e., put same mapping with different field order |
@AVVS that may work, or changing field names might work as well. We're working on a fix. |
…der to ensure that the source is always the same. Closes elastic#7215
…der to ensure that the source is always the same. Closes #7215
…der to ensure that the source is always the same. Closes #7215
…der to ensure that the source is always the same. Closes #7215
@AVVS Thanks for reporting this issue, the re-syncing of the mapping was causing by multi-fields not being serialised consistently and this is fixed now. |
Thanks, when should I expect 1.3.2 to be released? :) |
@AVVS I expect a 1.3.2 release in the coming days. |
…der to ensure that the source is always the same. Closes #7215
I'm not entirely clear on the status of this bug, but wanted to report that under 1.5 and now 1.5.1 (potentially under 1.4.x as well, but I can't confirm that) we've run into the endless re-syncing mappings issue. I can provide any further details you'd like, let me know. |
@heffergm please could you open a new bug, and upload your mappings? |
…der to ensure that the source is always the same. Closes elastic#7215
…der to ensure that the source is always the same. Closes elastic#7215
Corresponding mapping and index settings: https://gist.github.com/AVVS/bef59f42760256e2b5e8
Basically it looks like this and can last forever:
The text was updated successfully, but these errors were encountered: