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.

Sign up for GitHub

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

Jump to bottom

Encapsulate difficulties with sorted sets of members #23308

Open
patriknw opened this issue Jul 7, 2017 · 1 comment
Open

Encapsulate difficulties with sorted sets of members #23308

patriknw opened this issue Jul 7, 2017 · 1 comment
Assignees
@ktoso
Labels
1 - triaged Tickets that are safe to pick up for contributing in terms of likeliness of being accepted t:cluster:dc t:cluster
Milestone
2.5.x

Comments

@patriknw
Copy link
Member

patriknw commented Jul 7, 2017

In several places we maintain a set of cluster Member with different ordering. Since Member.leaderStatusOrdering Member.ageOrdering are not stable (e.g. member status may change) ordinary - can't be used when removing (or replacing).

We should encapsulate those difficulties in a data structure. It should support adding, replacing and removing a member. Preferably with O(1) operations (e.g. Map lookup via UniqueAddress).

See #23297
@patriknw patriknw added 1 - triaged Tickets that are safe to pick up for contributing in terms of likeliness of being accepted t:cluster t:cluster:dc labels Jul 7, 2017
@ktoso ktoso added 3 - in progress Someone is working on this ticket and removed 1 - triaged Tickets that are safe to pick up for contributing in terms of likeliness of being accepted labels Jul 14, 2017
@ktoso ktoso added this to the 2.5.x milestone Jul 14, 2017
@ktoso
Copy link
Member

ktoso commented Jul 19, 2017

Worked a bit on it, putting it back for now (as different sprint focus)

@ktoso ktoso added 1 - triaged Tickets that are safe to pick up for contributing in terms of likeliness of being accepted and removed 3 - in progress Someone is working on this ticket labels Jul 19, 2017
@ktoso ktoso self-assigned this Jul 19, 2017
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@ktoso ktoso

Labels
1 - triaged Tickets that are safe to pick up for contributing in terms of likeliness of being accepted t:cluster:dc t:cluster
Projects
None yet
Milestone
2.5.x
Development

No branches or pull requests
2 participants
@ktoso @patriknw