accumulo-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Michael Berman (JIRA)" <>
Subject [jira] [Commented] (ACCUMULO-1699) ZooKeeperInstance lazy load instanceId
Date Fri, 01 Nov 2013 18:55:17 GMT


Michael Berman commented on ACCUMULO-1699:

This is addressed as a side effect of my refactors of ZooKeeperInstance constructors as part
of SSL (ACCUMULO-1009).  I was able to uncomment the relevant lines in ConfiguratorBaseTest
and it seems like it works fine.  I don't see any path where the ZooKeeperInstance constructor
actually talks to ZK any more, following that changeset.

Assigning to me so I remember to mark it resolved once the SSL patch is accepted.

> ZooKeeperInstance lazy load instanceId
> --------------------------------------
>                 Key: ACCUMULO-1699
>                 URL:
>             Project: Accumulo
>          Issue Type: Improvement
>          Components: client
>    Affects Versions: 1.5.0
>            Reporter: Christopher Tubbs
>             Fix For: 1.7.0
> 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
> 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.

This message was sent by Atlassian JIRA

View raw message