Community
Participate
Working Groups
It seems that the current way of initializing and loading the ZooKeeper based cloud preferences does not fly. I did a code review (again) and I think a few changes should be implemented in order to remove some of the implementation complexity and to improve the loading reliability. * connect and load synchronously (instead of async) on first access * fail early *and always* if not connected
Fix committed to HEAD. I also noticed a missing connect/load call when performing a node/child exist check. This could have caused a few issues down the road (at least one in Jetty initialization).