[
https://issues.apache.org/jira/browse/ACCUMULO-3631?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14341840#comment-14341840
]
Sean Busbey commented on ACCUMULO-3631:
---------------------------------------
Sorry I didn't explain this well enough. CM does centralize the client
configuration for users, it just does it via accumulo-site.xml in
/etc/accumulo/conf/. All of the server processes get a custom
ACCUMULO_CONF_DIR for their version of the accumulo-site.xml, since their
lifecycle and config is already controlled. In such a set up, there is no need
for the clients to have access to any of the configuration associated with the
servers.
The client configuration is a good improvement, no doubt. Just wanted to point
out that so long as you have a change management + deployment system you can do
things now without requiring the end user of the cluster to do any of these
hacky work arounds.
> Exclude 'slf4j' artifacts from classpath in default value for
> general.classpaths
> --------------------------------------------------------------------------------
>
> Key: ACCUMULO-3631
> URL: https://issues.apache.org/jira/browse/ACCUMULO-3631
> Project: Accumulo
> Issue Type: Bug
> Affects Versions: 1.6.0, 1.6.1, 1.6.2
> Reporter: Josh Elser
> Assignee: Josh Elser
> Priority: Blocker
> Fix For: 1.7.0, 1.6.3
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> Was testing out some Ambari integration for Accumulo that [~billie.rinaldi]
> and [~mwaineo] have been working on (AMBARI-5265) and found that, despite
> accumulo-site.xml having jars starting with slf4j excluded from the
> classpath, the shell would complain about duplicate slf4j-log4j12 jars on the
> classpath.
> Turns out, because access to accumulo-site.xml was restricted (and we only
> had client.conf to use), we fell back on the default value for
> general.classpaths defined in AccumuloClassLoader. A short-term fix is to
> update the value there to match what's in our site template.
> I'll add another issue for a long term fix to add classpath support to client
> configuration.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
