Mailing-List: contact issues-help@hbase.apache.org; run by ezmlm
Precedence: bulk
Date: Wed, 4 Jun 2014 17:11:01 +0000 (UTC)
From: "Andrew Purtell (JIRA)" <jira@apache.org>
To: issues@hbase.apache.org
Message-ID: <JIRA.12683027.1386288180417.71276.1401901861873@arcas>
In-Reply-To: <JIRA.12683027.1386288180417@arcas>
References: <JIRA.12683027.1386288180417@arcas>
Subject: [jira] [Commented] (HBASE-10092) Move up on to log4j2
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Andrew Purtell commented on HBASE-10092:
----------------------------------------

bq.  Need to make tgzs and see that stuff lands in right place. Add some excludes for transitive includes of old log4js.

I did this and checked mvn dependency:tree. It looks good. I then had to add back log4j 1 in test scope so we could actually instantiate Hadoop classes for running unit tests, not sure what that is going to do in an assembly.

bq. Need to try in standalone, pseudo, and cluster and bring up shell to make sure logs are ending up in right place

Yes, the new log4j2.xml files are untested and I'm sure need work. 

> Move up on to log4j2
> --------------------
>
>                 Key: HBASE-10092
>                 URL: https://issues.apache.org/jira/browse/HBASE-10092
>             Project: HBase
>          Issue Type: Sub-task
>            Reporter: stack
>            Assignee: stack
>         Attachments: 10092.txt, 10092v2.txt, HBASE-10092.patch
>
>
> Allows logging with less friction.  See http://logging.apache.org/log4j/2.x/  This rather radical transition can be done w/ minor change given they have an adapter for apache's logging, the one we use.  They also have and adapter for slf4j so we likely can remove at least some of the 4 versions of this module our dependencies make use of.
> I made a start in attached patch but am currently stuck in maven dependency resolve hell courtesy of our slf4j.  Fixing will take some concentration and a good net connection, an item I currently lack.  Other TODOs are that will need to fix our little log level setting jsp page -- will likely have to undo our use of hadoop's tool here -- and the config system changes a little.
> I will return to this project soon.  Will bring numbers.
>  


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