howzi commented on PR #5147: URL: https://github.com/apache/hadoop/pull/5147#issuecomment-1319852875
> > Thank you for reply, it exactly create more pressure on zk for some moment, but didn't create more read/write requests. Maybe it shouldn't be a default configuration > > From my personal point of view, ZK is not a high-concurrency component. At the same time, ZK plays a role in HDFS, YARN HA, YARN App management, etc. If we have no obvious performance problems, it is not recommended to modify this part of the code. > > Let's wait for other partners' suggestions. > > Thanks again for your contribution! > > Thank you for reply, it exactly create more pressure on zk for some moment, but didn't create more read/write requests. Maybe it shouldn't be a default configuration > > From my personal point of view, ZK is not a high-concurrency component. At the same time, ZK plays a role in HDFS, YARN HA, YARN App management, etc. If we have no obvious performance problems, it is not recommended to modify this part of the code. > > Let's wait for other partners' suggestions. > > Thanks again for your contribution! Actually it is an obvious performance problem, it takes over 3 mins to refresh the state store cache in our enviroment. Different deployment of ZK may cause a diffrent choice. For example, we have a exclusive ZK cluster for router, it's not a big problem for us. Anyway, I realized this is not a good feature for everyone, I will change it to an optional configuration, that must be better. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: common-issues-unsubscr...@hadoop.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org --------------------------------------------------------------------- To unsubscribe, e-mail: common-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: common-issues-h...@hadoop.apache.org
