Mailing-List: contact notifications-help@accumulo.apache.org; run by ezmlm
Precedence: bulk
Reply-To: jira@apache.org
Date: Fri, 1 Aug 2014 18:45:39 +0000 (UTC)
From: "Eric Newton (JIRA)" <jira@apache.org>
To: notifications@accumulo.apache.org
Message-ID: <JIRA.12706232.1396458825919.97164.1406918739219@arcas>
In-Reply-To: <JIRA.12706232.1396458825919@arcas>
References: <JIRA.12706232.1396458825919@arcas>
Subject: [jira] [Resolved] (ACCUMULO-2615) Simplify server configuration
 caching and ZK watchers
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Eric Newton resolved ACCUMULO-2615.
-----------------------------------

    Resolution: Fixed

> Simplify server configuration caching and ZK watchers
> -----------------------------------------------------
>
>                 Key: ACCUMULO-2615
>                 URL: https://issues.apache.org/jira/browse/ACCUMULO-2615
>             Project: Accumulo
>          Issue Type: Improvement
>            Reporter: Bill Havanki
>            Assignee: Eric Newton
>             Fix For: 1.6.1, 1.7.0
>
>          Time Spent: 1h
>  Remaining Estimate: 0h
>
> The mechanism used for caching server-related configuration objects and processing ZK events could do with some simplification. For example:
> * The watcher objects obtain their corresponding configuration objects by reaching through the {{ServerConfiguration}} cache, instead of just having a more direct reference.
> * The watcher objects set log4j logging levels for both ZK and o.a.hadoop.io.compress to WARN, which prohibits debugging when needed. That should be done in log4j properties/XML instead.
> * Possible bug: {{NamespaceConfWatcher}} expires table configuration observers, not namespace configuration observers.
> * There is high duplication between the static and instance methods of {{ServerConfiguration}}. The class serves as both a cache container and a factory. Moreover, despite its name, it isn't actually a configuration object.
> I may be missing some subtleties of why things are as they are, so please fill me in as needed.


--
This message was sent by Atlassian JIRA
(v6.2#6252)