accumulo-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "John Vines (JIRA)" <>
Subject [jira] [Updated] (ACCUMULO-1699) ZooKeeperInstance lazy load instanceId
Date Fri, 29 Nov 2013 18:25:35 GMT


John Vines updated ACCUMULO-1699:

    Resolution: Fixed
        Status: Resolved  (was: Patch Available)

Resolved with ACCUMULO-1009 patch

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