accumulo-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Josh Elser (JIRA)" <>
Subject [jira] [Commented] (ACCUMULO-3631) Exclude 'slf4j' artifacts from classpath in default value for general.classpaths
Date Sat, 28 Feb 2015 02:29:05 GMT


Josh Elser commented on ACCUMULO-3631:

bq. Which recommendations are you referring to?

accumulo-site.xml is chmod 600 and owned by the Accumulo use. The file must be protected to
ensure that instance.secret is not compromised. The cornerstone of the deployment security.

bq. which brokenness are you referring to, specifically

While this issue was opened specifically about an irritation (duplicate slf4j bindings on
the classpath), it is representative of a much larger problems which forces Accumulo to only
be functional under a single filesystem layout of Hadoop. If the hadoop install doesn't match
the single layout that we have defined, there is no way that I see for non-Accumulo users
to leverage the {{accumulo}} command. In short, there is no way to allow full client access
to Accumulo while protecting necessary Accumulo configuration presently.

bq. It is not my intention to be brash; it is to be direct and precise. I apologize if it
came across that way.

Thank you. It came across very anti-social to -1 and threaten a revert without having any
discussion. Happy to work through this.

> Exclude 'slf4j' artifacts from classpath in default value for general.classpaths
> --------------------------------------------------------------------------------
>                 Key: ACCUMULO-3631
>                 URL:
>             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

View raw message