-
Notifications
You must be signed in to change notification settings - Fork 24.6k
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
NullPointerException failed to dynamically refresh the mapping in cluster_state from shard #2633
Comments
Deleting the index is not the solution:
|
What I understand is that the cluster state is in a poor state. Finally the Exception is catched at MetaDataMappingService.java#L145 and the state is rolled back to the previsous one (the bad one). Index creation and deletion are very slow:
But once created, indexation are fast:
And querying works:
|
Ok now, I have a better understanding of what happens on the cluster. The long index creation time is not related to the NullPointerException : https://groups.google.com/d/msg/elasticsearch/hHniXBx8su8/VfEArmcpqQgJ I am now able to reproduce the NullPointerException:
The same logs in DEBUG : https://gist.github.com/Filirom1/4943162. I use a 4 nodes cluster in 0.19.11 |
Can you reproduce the NullPointerException issue with 0.20.5 or master? |
Closing this as it is quite stale. Happy to reopen, if this still happens with a current 0.90.3 release. Please tell us! |
I can't reproduce this locally but I can confirm that we see this error in 0.90.5: |
do you have a stack trace as you could paste here? |
I think the NPE here might be related to |
I'm working on getting the stack but I haven't been able to reproduce this in an environment that allows me to do this. Regarding the "toString()" fix we don't use templates so I don't think that is the problem. My working hypothesis at the moment after looking at the mappings for indices that fails is that they all contain mappings where we have the same property name at different levels and that this also makes the merging of mappings to fail, causing a refresh-mapping giving the same NPE. |
For a maintenance operation we disabled allocation and restart one node.
Unfortunately, something went wrong with ES:
And now, I have a lot of WARN
When I say a lot, I mean it ;)
The text was updated successfully, but these errors were encountered: