Description
I was unit testing the serialization of ZooKeeperInstance settings in a mapreduce job, and discovered that I couldn't deserialize and construct the ZooKeeperInstance unless the hostnames were valid and ZK was running.
It should be possible to construct an instance of ZooKeeperInstance without trying to connect.
It is unintuitive that it immediately tries to connect to ZooKeeper when it is constructed, instead of waiting until getInstanceId() is called.
The constructor should only construct the object... not do work.
Attachments
Issue Links
- relates to
-
ACCUMULO-1694 ZooKeeperInstance constructor should avoid throwing RuntimeExceptions
-
- Resolved
-