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]RetentionLeaseInvalidRetainingSeqNoException is coming when retention lease already present on leader for follower index #882

Closed
nisgoel-amazon opened this issue May 23, 2023 · 1 comment
Labels
bug Something isn't working v2.8.0

Comments

@nisgoel-amazon
Copy link
Contributor

What is the bug?
RetentionLeaseInvalidRetainingSeqNoException is coming when leader cluster is having retention lease and on follower cluster someone try to start replication with same index name.

[2023-04-02T22:50:40,816][ERROR][o.o.r.r.RemoteClusterRepository] [4c49dc0e6b723fdade00f0e3b35fe316] Restore of shard from remote cluster repository failed permanently after all retries due to RetentionLeaseInvalidRetainingSeqNoException[the current retention lease with [replication:613844886458:aid-mktplce:[compteamprimary][1]] is retaining a higher sequence number [13301] than the new retaining sequence number [13296] from [replication:613844886458:aid-mktplce]]
    at org.opensearch.index.seqno.ReplicationTracker.renewRetentionLease(ReplicationTracker.java:430)
    at org.opensearch.index.shard.IndexShard.renewRetentionLease(IndexShard.java:2607)
    at org.opensearch.index.seqno.RetentionLeaseActions$Renew$TransportAction.doRetentionLeaseAction(RetentionLeaseActions.java:219)
    at org.opensearch.index.seqno.RetentionLeaseActions$Renew$TransportAction.doRetentionLeaseAction(RetentionLeaseActions.java:194)
    at org.opensearch.index.seqno.RetentionLeaseActions$TransportRetentionLeaseAction.lambda$asyncShardOperation$0(RetentionLeaseActions.java:111)

How can one reproduce the bug?
Steps to reproduce the behavior:

  1. Create connection between follower and leader domain
  2. Start the replication on index1
  3. Delete the connection between cluster, replication went to autopause and lease on leader will not be deleted as there is no connection.
  4. Create the connection again with same alias name
  5. Then start the replication of same index after deleting index from follower.

What is the expected behavior?
Replication should start successfully without giving RetentionLeaseInvalidRetainingSeqNoException

What is your host/environment?

  • OS: linux
  • Version OS-1.3
  • Plugins CCR
@monusingh-1
Copy link
Collaborator

Closing as resolved

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working v2.8.0
Projects
None yet
Development

No branches or pull requests

3 participants