Skip to content

Add autoStepDownWhenLeader to MemberInfo [CORE-216] #545

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

Open
wants to merge 4 commits into
base: master
Choose a base branch
from

Conversation

gareth-johnston
Copy link
Contributor

Adds autoStepDownWhenLeader boolean added to MemberInfo

@gareth-johnston gareth-johnston requested a review from Copilot April 11, 2025 07:19
Copilot

This comment was marked as spam.

@@ -828,6 +828,10 @@ customTypes:
type: Map_EndpointQualifier_Address
nullable: false
since: 2.0.1
- name: autoStepDownWhenLeader
Copy link
Collaborator

Choose a reason for hiding this comment

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

Suggested change
- name: autoStepDownWhenLeader
- name: cpAutoStepDownWhenLeader

Copy link
Member

Choose a reason for hiding this comment

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

agree that prefixing with cp makes it more understandable, especially for the future readers.

@gareth-johnston gareth-johnston force-pushed the CORE-216/abdicating-leadership branch from daccd74 to 83d5aaa Compare April 28, 2025 16:12
Copy link
Contributor

@JamesHazelcast JamesHazelcast left a comment

Choose a reason for hiding this comment

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

I agree with @ihsandemir that prefixing with cp makes sense, to provide extra clarity - approving in advance though 👍

@gareth-johnston
Copy link
Contributor Author

I agree with @ihsandemir that prefixing with cp makes sense, to provide extra clarity - approving in advance though 👍

Do you think that is still relevant now? That comment was relating to when we were changing memberInfo - absolutely in that case. But now we are only changing CPMember -- I believe it is clear enough in this case, do you feel strongly?

@JamesHazelcast
Copy link
Contributor

Do you think that is still relevant now? That comment was relating to when we were changing memberInfo - absolutely in that case. But now we are only changing CPMember -- I believe it is clear enough in this case, do you feel strongly?

Ah, apologies - no I don't think it's relevant in that case, all good to go from my POV

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

Successfully merging this pull request may close these issues.

4 participants