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

cloud: fix(lease): prevent ID lease overflow #7802

Merged
merged 2 commits into from
May 11, 2021

Conversation

NamanJain8
Copy link
Contributor

@NamanJain8 NamanJain8 commented May 11, 2021

Cherry-picks:


This change is Reviewable

…id (#7743)

This PR fixes the following case:
If we have a cluster that cannot lease out new UIDs because it has already leased upto its
max limit. Now, we try to live load the data with the given UIDs and the AssignIds complains
that the limit has reached. Hence, update the xidmap's maxSeenUid and make progress.

(cherry picked from commit ad64c01)
@NamanJain8 NamanJain8 changed the title Naman/cp/uidlease cloud: fix(lease): prevent ID lease overflow May 11, 2021
@NamanJain8 NamanJain8 merged commit 1235438 into release/v21.03-slash May 11, 2021
@NamanJain8 NamanJain8 deleted the naman/cp/uidlease branch May 11, 2021 11:48
ahsanbarkati pushed a commit that referenced this pull request May 27, 2021
* fix(lease): prevent ID lease overflow (#7724)

(cherry picked from commit d4c6b7c)

* fix(live): make live loader progress on a cluster with very high maxUid  (#7743)

This PR fixes the following case:
If we have a cluster that cannot lease out new UIDs because it has already leased upto its
max limit. Now, we try to live load the data with the given UIDs and the AssignIds complains
that the limit has reached. Hence, update the xidmap's maxSeenUid and make progress.

(cherry picked from commit ad64c01)
(cherry picked from commit 1235438)
ahsanbarkati pushed a commit that referenced this pull request May 27, 2021
* fix(lease): prevent ID lease overflow (#7724)

(cherry picked from commit d4c6b7c)

* fix(live): make live loader progress on a cluster with very high maxUid  (#7743)

This PR fixes the following case:
If we have a cluster that cannot lease out new UIDs because it has already leased upto its
max limit. Now, we try to live load the data with the given UIDs and the AssignIds complains
that the limit has reached. Hence, update the xidmap's maxSeenUid and make progress.

(cherry picked from commit ad64c01)
(cherry picked from commit 1235438)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

Successfully merging this pull request may close these issues.

2 participants