Return-Path: X-Original-To: archive-asf-public-internal@cust-asf2.ponee.io Delivered-To: archive-asf-public-internal@cust-asf2.ponee.io Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183]) by cust-asf2.ponee.io (Postfix) with ESMTP id B13D5200B74 for ; Thu, 18 Aug 2016 00:11:22 +0200 (CEST) Received: by cust-asf.ponee.io (Postfix) id AFC39160ABF; Wed, 17 Aug 2016 22:11:22 +0000 (UTC) Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by cust-asf.ponee.io (Postfix) with SMTP id 0DC92160AB5 for ; Thu, 18 Aug 2016 00:11:21 +0200 (CEST) Received: (qmail 86192 invoked by uid 500); 17 Aug 2016 22:11:21 -0000 Mailing-List: contact common-issues-help@hadoop.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Delivered-To: mailing list common-issues@hadoop.apache.org Received: (qmail 86137 invoked by uid 99); 17 Aug 2016 22:11:21 -0000 Received: from arcas.apache.org (HELO arcas) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 17 Aug 2016 22:11:21 +0000 Received: from arcas.apache.org (localhost [127.0.0.1]) by arcas (Postfix) with ESMTP id D3EBF2C02B1 for ; Wed, 17 Aug 2016 22:11:20 +0000 (UTC) Date: Wed, 17 Aug 2016 22:11:20 +0000 (UTC) From: "Chris Nauroth (JIRA)" To: common-issues@hadoop.apache.org Message-ID: In-Reply-To: References: 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 X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 archived-at: Wed, 17 Aug 2016 22:11:22 -0000 [ https://issues.apache.org/jira/browse/HADOOP-12956?page=3Dcom.atlassi= an.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=3D15= 425483#comment-15425483 ]=20 Chris Nauroth commented on HADOOP-12956: ---------------------------------------- [~mikaelstaldal], backward-compatibility with the Log4J 1 properties file f= ormat would be hugely beneficial for us. Thank you. I'm linking to LOG4J2= -63, which seems to be the master JIRA tracking that effort against Log4J 2= .7. > 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) --------------------------------------------------------------------- To unsubscribe, e-mail: common-issues-unsubscribe@hadoop.apache.org For additional commands, e-mail: common-issues-help@hadoop.apache.org