Skip to content
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] Encountered a failure while executing in org.opensearch.replication.action.changes.GetChangesRequest #898

Open
zalseryani opened this issue May 28, 2023 · 3 comments
Labels
bug Something isn't working

Comments

@zalseryani
Copy link

What is the bug?

  • 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

image

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.

@zalseryani zalseryani added bug Something isn't working untriaged labels May 28, 2023
@zalseryani zalseryani changed the title [BUG] [BUG] Encountered a failure while executing in org.opensearch.replication.action.changes.GetChangesRequest May 28, 2023
@soosinha
Copy link
Member

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 ?

@zalseryani
Copy link
Author

@soosinha

Yes, I am checking the doc count, knowing that the index refresh interval is 1 second.

@hm2thr33
Copy link

Hi,
have the same issue with OpenSearch 2.8.0

@soosinha how can i increase the parameter GetChangesAction?

and it seems to me that this option is being ignored:

    "plugins": {
      "replication": {
        "follower": {
          "metadata_sync_interval": "60s"
        }

because the index that I synchronize is updated every ~10 seconds

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
Status: 🆕 New
Development

No branches or pull requests

3 participants