accumulo-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Josh Elser (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (ACCUMULO-1067) InstanceOperations.setProperty / getSystemConfiguration inconsistent state
Date Wed, 19 Nov 2014 22:07:33 GMT

     [ https://issues.apache.org/jira/browse/ACCUMULO-1067?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Josh Elser resolved ACCUMULO-1067.
----------------------------------
    Resolution: Duplicate

Thanks for filing, [~jklucar]. This is a known issue with how we use ZooKeeper for configuration
(specifically ZooCache). ACCUMULO-1568 would be the proper solution to avoid getting stale
information from caches around ZooKeeper.

> InstanceOperations.setProperty / getSystemConfiguration inconsistent state
> --------------------------------------------------------------------------
>
>                 Key: ACCUMULO-1067
>                 URL: https://issues.apache.org/jira/browse/ACCUMULO-1067
>             Project: Accumulo
>          Issue Type: Bug
>          Components: client
>         Environment: Found when testing 1.5/trunk MiniAccumuloCluster, but could exist
in real clusters.
>            Reporter: Jim Klucar
>            Priority: Minor
>
> Performing an InstanceOperations.setProperty followed by an InstanceOperations.getSystemConfiguration
can show that the property set wasn't actually set. This is most likely due to the fact that
getSystemConfiguration contacts a random tserver to get the configuration, and that request
could be received before the pub/sub event from Zookeeper is received.  Potential solution
is to have this method contact the Master directly.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message