You are viewing a plain text version of this content. The canonical link for it is here.

Posted to notifications@accumulo.apache.org by "Keith Turner (JIRA)" <ji...@apache.org> on 2014/05/11 00:13:04 UTC

[jira] [Updated] (ACCUMULO-1067) InstanceOperations.setProperty / getSystemConfiguration inconsistent state

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

Keith Turner updated ACCUMULO-1067:
-----------------------------------

    Assignee:     (was: Keith Turner)

> 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.2#6252)