Return-Path: 
 <issues-return-126462-apmail-hbase-issues-archive=hbase.apache.org@hbase.apache.org>
X-Original-To: apmail-hbase-issues-archive@www.apache.org
Delivered-To: apmail-hbase-issues-archive@www.apache.org
Received: from mail.apache.org (hermes.apache.org [140.211.11.3])
	by minotaur.apache.org (Postfix) with SMTP id 6028710160
	for <apmail-hbase-issues-archive@www.apache.org>;
 Fri,  6 Dec 2013 06:22:35 +0000 (UTC)
Received: (qmail 38137 invoked by uid 500); 6 Dec 2013 04:27:42 -0000
Delivered-To: apmail-hbase-issues-archive@hbase.apache.org
Received: (qmail 38091 invoked by uid 500); 6 Dec 2013 04:27:41 -0000
Mailing-List: contact issues-help@hbase.apache.org; run by ezmlm
Precedence: bulk
List-Help: <mailto:issues-help@hbase.apache.org>
List-Unsubscribe: <mailto:issues-unsubscribe@hbase.apache.org>
List-Post: <mailto:issues@hbase.apache.org>
List-Id: <issues.hbase.apache.org>
Delivered-To: mailing list issues@hbase.apache.org
Received: (qmail 37947 invoked by uid 99); 6 Dec 2013 04:27:38 -0000
Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28)
    by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 06 Dec 2013 04:27:38 +0000
Date: Fri, 6 Dec 2013 04:27:38 +0000 (UTC)
From: "Andrew Purtell (JIRA)" <jira@apache.org>
To: issues@hbase.apache.org
Message-ID: <JIRA.12682505.1386101462817.83073.1386304058357@arcas>
In-Reply-To: <JIRA.12682505.1386101462817@arcas>
References: <JIRA.12682505.1386101462817@arcas>
Subject: [jira] [Commented] (HBASE-10073) [Hadoop1]: hbase zkcli broken due
 to slf4j incompatibility
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394


    [ https://issues.apache.org/jira/browse/HBASE-10073?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13840960#comment-13840960 ] 

Andrew Purtell commented on HBASE-10073:
----------------------------------------

Do we care about calling zkcli from with HBase? Should ZK users call ZK CLI from their separate ZK install?

> [Hadoop1]: hbase zkcli broken due to slf4j incompatibility
> ----------------------------------------------------------
>
>                 Key: HBASE-10073
>                 URL: https://issues.apache.org/jira/browse/HBASE-10073
>             Project: HBase
>          Issue Type: Bug
>          Components: Zookeeper
>    Affects Versions: 0.96.1
>         Environment: Centos6, sun-jdk-64bit-1.7.0.25
>            Reporter: Aleksandr Shulman
>            Assignee: Andrew Purtell
>             Fix For: 0.98.0, 0.96.1, 0.99.0
>
>
> Observed behavior:
> In my automation, I have a call to hbase zkcli. That call recently broke with this checkin: https://github.com/apache/hbase/commit/5af0a60efed91ac2084f25f13edb21db0f510e7c
> The error that is reported is:
> {code}++ ./hbase zkcli
> 11:19:58  Warning: $HADOOP_HOME is deprecated.
> 11:19:58  
> 11:20:00  Exception in thread "main" java.lang.IllegalAccessError: tried to access field org.slf4j.impl.StaticLoggerBinder.SINGLETON from class org.slf4j.LoggerFactory
> 11:20:00  	at org.slf4j.LoggerFactory.<clinit>(LoggerFactory.java:60)
> 11:20:00  	at org.apache.zookeeper.ZooKeeperMain.<clinit>(ZooKeeperMain.java:50)
> 11:20:00  	at org.apache.hadoop.hbase.zookeeper.ZooKeeperMainServer.main(ZooKeeperMainServer.java:78)
> 11:20:00  Build step 'Execute shell' marked build as failure{code}
> That said, this checkin is perfectly valid as each component should be allowed to specify its own dependencies.
> The issue is a deeper one of dependency mismatches.
> Note: This issue only affects hadoop1, not hadoop2. It also appears in trunk, where there is a similar checkin, but since trunk is not required to work against hadoop1, this is not an issue for trunk.



--
This message was sent by Atlassian JIRA
(v6.1#6144)