-
Notifications
You must be signed in to change notification settings - Fork 7.3k
ZOOKEEPER-4257: learner.asyncSending and learner.closeSocketAsync should be configurable in zoo.cfg #1645
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
Conversation
…uld be configurable in zoo.cfg
|
Lets wait for the 3.7.0 releases. We have to update the change for branch-3.7. Have to change the property in backward compatible way. |
|
@arshadmohammad @ayushmantri Thanks for the commit. This configuration is important and helpful for #1582, and I appreciate it. However, the description for |
|
sure @functioner |
|
@functioner please raise PR to backport ZOOKEEPER-3575 in branch-3.6 |
eolivelli
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It looks like that this is a breaking change.
Do we really need to change the name of the property?
What about adding a compatibility layer (reading the old and the new name)
yes, it is required to make it configurable in configuration file zoo.cfg. Currently it is not configurable in zoo.cfg. it must be configured as java system property in some shell script file. For example, before this PR change, if I configure learner.asyncSending=true in zoo.cfg It will not be effective as in ZooKeeper before use this configured property is converted to zookeeper.learner.asyncSending. |
yes, compatibility layer can be added. Only thing is now there will three properties for the same thing
and normal configuration property, configurable in zoo.cfg
|
@arshadmohammad I raised the PR in #1653. |
…uld be configurable in zoo.cfg
property name change done in backward compatible way
|
handled property name change in backward compatible way |
arshadmohammad
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM +1
eolivelli
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Great
+1
…ader.closeSocketAsync should be configurable in zoo.cfg Properties learner.asyncSending , learner.closeSocketAsync and leader.closeSocketAsync made configurable in zoo.cfg Author: Ayush Mantri <[email protected]> Reviewers: Enrico Olivelli <[email protected]>, Mohammad Arshad <[email protected]> Closes #1645 from ayushmantri/ZK-4257 and squashes the following commits: 8ff5523 [Ayush Mantri] ZOOKEEPER-4257: learner.asyncSending and learner.closeSocketAsync should be configurable in zoo.cfg property name change done in backward compatible way 5929312 [Ayush Mantri] ZOOKEEPER-4257: learner.asyncSending and learner.closeSocketAsync should be configurable in zoo.cfg (cherry picked from commit acbfb2d) Signed-off-by: Mohammad Arshad <[email protected]>
Properties learner.asyncSending , learner.closeSocketAsync and leader.closeSocketAsync made configurable in zoo.cfg