Skip to content
This repository has been archived by the owner on Jun 20, 2024. It is now read-only.

resolve inconsistencies detected during ring merge #3637

Merged
merged 7 commits into from
Jun 14, 2019
Merged

Conversation

murali-reddy
Copy link
Contributor

implements tie-breaker suggestions in #1962 and unit-tests to test the behaviour

Fixes #1962

Copy link
Contributor

@bboreham bboreham left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks promising, but can you check the case where we receive an update to our own data?

ipam/ring/ring.go Show resolved Hide resolved
…newer version, set our version to the one received plus one, effectively imposing our existing entry
@bboreham bboreham added this to the 2.6 milestone May 10, 2019
@bboreham
Copy link
Contributor

Appears to be removing the debug logging added in #3627 - is that intended?

ipam/ring/ring.go Outdated Show resolved Hide resolved
@murali-reddy
Copy link
Contributor Author

Appears to be removing the debug logging added in #3627 - is that intended?

Unintended change due to rebase. Fixed it.

ipam/ring/ring.go Outdated Show resolved Hide resolved
Copy link
Contributor

@bboreham bboreham left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

lgtm

@bboreham
Copy link
Contributor

Does this fix #2084 ?

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

resolve inconsistencies detected during ring merge
2 participants