There have been several comments on the document. I will be porting discussions from the document back to the mailing list each day.
Alex Shraer makes a good point that with the design as stated, there is no provision for dealing with the rebalancing of client connections during dynamic reconfiguration. I am very curious whether this needs to be addressed in the design since it seems that if connections are redirected, the same connection logic should apply. I suppose the text needs an update, regardless, even if there is no effect. But is there something I missed here? Will there be a code effect? Another comment points out that if you don't have symmetrical hardware for the servers (i.e. more network interfaces on some), then client connections are likely to be more numerous on servers with more network connections. This is undoubtedly true. I have a question, however, about this. Is this situation actually important enough to make the first version of this change? My own experience is that production settings typically involve Zookeeper servers with very consistent hardware where this would not be an issue. What experience do others have, particularly in production situations? On 2018/10/23 02:02:12, Ted Dunning <[email protected]> wrote: > ... > I have started a collaborative document to work on the design approach. > Once that is judged by the community to be sufficiently mature, I will move > it to a JIRA. > > That document is at > https://docs.google.com/document/d/1iGVwxeHp57qogwfdodCh9b32P2_kOQaJZ2GDo7j36fI/edit?usp=sharing > > The design document is currently open to the world for commenting so that > anybody can suggest changes or ask questions. I will act as a bit of a > moderator so that the document can remain completely open. >
