Mailing-List: contact common-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: common-issues@hadoop.apache.org
Date: Mon, 28 Mar 2016 00:42:25 +0000 (UTC)
From: "Andrew Purtell (JIRA)" <jira@apache.org>
To: common-issues@hadoop.apache.org
Message-ID: <JIRA.12952690.1458709758000.61326.1459125745704@Atlassian.JIRA>
In-Reply-To: <JIRA.12952690.1458709758000@Atlassian.JIRA>
References: <JIRA.12952690.1458709758000@Atlassian.JIRA>
 <JIRA.12952690.1458709758083@arcas>
Subject: [jira] [Commented] (HADOOP-12956) Inevitable Log4j2 migration via
 slf4j
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable


    [ https://issues.apache.org/jira/browse/HADOOP-12956?page=3Dcom.atlassi=
an.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=3D15=
213694#comment-15213694 ]=20

Andrew Purtell commented on HADOOP-12956:
-----------------------------------------

We also evaluated a move to log4j2 for HBase on HBASE-10092, and likewise c=
ame to the conclusion it is impossible to achieve backwards compatibility f=
or operators and tools. A change like this can't go in on a minor release. =
(At least, HBase cannot do that, according to our published version compati=
bility guidelines.) The killer issue is no backwards compatibility for the =
properties based configuration files. Operators, not unreasonably, expect a=
 minor or patch version increment should continue to "just work" with exist=
ing configuration files and tooling, not completely break all logging.=20

I see after LOG4J2-952 there is a "PropertiesConfigurationFactory", so _a_ =
properties based configuration file format is again possible, but this isn'=
t helpful and probably not desired because you get the limitations of a pro=
perties file format without v1 compatibility.

> Inevitable Log4j2 migration via slf4j
> -------------------------------------
>
>                 Key: HADOOP-12956
>                 URL: https://issues.apache.org/jira/browse/HADOOP-12956
>             Project: Hadoop Common
>          Issue Type: Improvement
>            Reporter: Gopal V
>
> {{5 August 2015 --The Apache Logging Services=E2=84=A2 Project Management=
 Committee (PMC) has announced that the Log4j=E2=84=A2 1.x logging framewor=
k has reached its end of life (EOL) and is no longer officially supported.}=
}
> https://blogs.apache.org/foundation/entry/apache_logging_services_project=
_announces
> A whole framework log4j2 upgrade has to be synchronized, partly for impro=
ved performance brought about by log4j2.
> https://logging.apache.org/log4j/2.x/manual/async.html#Performance


--
This message was sent by Atlassian JIRA
(v6.3.4#6332)