-
Notifications
You must be signed in to change notification settings - Fork 61
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
[BUG] Settings should be synced before syncing mappings #992
Comments
Able to reproduce this locally
Then indexing documents
|
HI @soosinha,
|
If the user closes the index and opens it again, it is possible that getChanges request comes in during this time and Auto-pause the replication. However it is also possible that close and open is done so quickly and the there is no getChanges request between them, hence leaving the replication in syncing state. If a user does the following
if the above is performed instantaneously, then we see that the replication goes to auto pause with a different reason
|
To overcome the above the user must simply pause the replicaiton and then update the index settings on leader index and then resume the replication. This will lead to leader index settings to be replicated on follower index. Testing details
When resume replication is triggered new persistent tasks are spinned up and the leader index settings are synced by IndexReplicationTask. Adding testing details below:
As we can see from the last output, replication is in SYNCING state and the leader index mapping |
Thanks @monusingh-1 for working on this and verifying the behavior. |
What is the bug?
When customer adds new mappings in the leader index and these mappings are dependent on analyzers which are newly defined in the settings, the replay fails on the follower side.
As per this logic, the follower tries to apply the operations directly. If the operations need mapping update, it then tries to sync remote mapping. But the syncing of remote mapping will fail if the settings have not been synced by the metadata polling task which happens every 1 minute.
How can one reproduce the bug?
Steps to reproduce the behavior:
What is the expected behavior?
The replication should work successfully by syncing all the settings and mappings
Do you have any additional context?
This problem can be solved by syncing the remote settings before syncing the mappings here
The text was updated successfully, but these errors were encountered: