elastic/elasticsearch
Vedi su GitHubBulk requests to an alias based on an old cluster state can cause strange rejection message
Open
#27.767 aperta il 12 dic 2017
:Distributed/CRUD>bugTeam:Distributedhelp wantedhigh hanging fruit
Metriche repository
- Star
- (76.700 star)
- Metriche merge PR
- (Merge medio 2g) (1000 PR mergiate in 30 g)
Descrizione
When a bulk request is based on an older state (where the index appears to need to be created) or where the node has not yet joined the cluster, and the request is issued using an alias instead of a concrete index, the node can send the request, then receive a confusing message about there already being an alias for that name, such as:
[RemoteTransportException[[node-1][127.0.0.1:9300][indices:admin/create]];
nested: InvalidIndexNameException[Invalid index name [current], already exists as
alias];]
There are really two things that should happen in this situation:
- We should check that the node is in a ready state before continuing with the bulk processing (ie, there are no WRITE blocks in the cluster state)
- When we receive a message about the alias already existing, we should not fail the bulk operation(s)
Relates to https://discuss.elastic.co/t/invalid-index-name/111131