You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
After creating a cross-cluster replication for one index, I started getting this error knowing that the replication is happening but why this error is occurring ?
Encountered a failure while executing in org.opensearch.replication.action.changes.GetChangesRequest
How can one reproduce the bug?
just create cross-site replication between 2 k8s clusters where the service of opensearch is exposed with LoadBalancer on GKE
What is the expected behavior?
replication without log errors.
What is your host/environment?
k8s cluster on GKE v1.24.11
helm chart version --> 2.12.0
AppVersion --> 2.7.0
Do you have any additional context?
Also I noticed that opensearch takes more time to update/flush its indices in order to have the data available when executing
GET _cat/indices/leader-test-follower?v
How to decrease the flush time of opensearch ? and when it is being done ?
Thanks in advance.
The text was updated successfully, but these errors were encountered:
zalseryani
changed the title
[BUG]
[BUG] Encountered a failure while executing in org.opensearch.replication.action.changes.GetChangesRequest
May 28, 2023
OpenSearchTimeoutException is an expected exception thrown when no new operations are available in the leader cluster. The GetChangesAction waits for 1 minute for the global checkpoint to advance before throwing the exception.
Also I noticed that opensearch takes more time to update/flush its indices in order to have the data available when executing
Can you provide details whether this is regarding the indices on leader or the follower? And are you are looking at the doc count to infer that the indices are updated ?
What is the bug?
How can one reproduce the bug?
What is the expected behavior?
What is your host/environment?
Do you have any additional context?
Thanks in advance.
The text was updated successfully, but these errors were encountered: