I have a question here. When a node receives an indexation query and doesn't have the primary shard. What is it's behavior?
Does it transfert the request to the master node that ships it to the dedicated node to answer it?
Or does it already know where the primary shard is and directly transfert it to the dedicated node that has the primary shard?
It goes to the node which is holding the primary.
Thanks @dadoonet for your reply. Then I have another question...
Lets say I have 5 nodes on different servers on which my app can send requests. I have 4 requests at the same time that updates a document and all 4 nodes ships the request to the 5th one.
How is that handled. There is for sure an order based on timestamp (in micro or nano seconds for example).
How does Elasticsearch handles document versioning and timestamping in case of multiple indexation on the same document of a shard?
The last request will most likely overwrite all the previous ones.
But you might want to read https://www.elastic.co/blog/elasticsearch-versioning-support although it's a bit old.
Yes, that's what I'm suppose to see happening considering that all the updates from the 3 other nodes have been made before and so my document version would have been increased 4 times right?
Thanks for the blog, I'll check it.
This topic was automatically closed 28 days after the last reply. New replies are no longer allowed.