Mailing-List: contact common-dev-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: common-dev@hadoop.apache.org
Date: Tue, 18 Mar 2014 21:32:46 +0000 (UTC)
From: "Arpit Agarwal (JIRA)" <jira@apache.org>
To: common-dev@hadoop.apache.org
Message-ID: <JIRA.12702257.1395178343639.100339.1395178366577@arcas>
In-Reply-To: <JIRA.12702257.1395178343639@arcas>
References: <JIRA.12702257.1395178343639@arcas>
Subject: [jira] [Created] (HADOOP-10413) Log statements must include pid and
 tid information
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

Arpit Agarwal created HADOOP-10413:
--------------------------------------

             Summary: Log statements must include pid and tid information
                 Key: HADOOP-10413
                 URL: https://issues.apache.org/jira/browse/HADOOP-10413
             Project: Hadoop Common
          Issue Type: Improvement
    Affects Versions: 2.3.0, 3.0.0
            Reporter: Arpit Agarwal


Log statements do not include process IDs and thread IDs which makes debugging hard when the output of multiple requests is interleaved. It's even worse when looking at the output of test runs because the logs from multiple daemons are interleaved in the same file.

Log4j does not provide a builtin mechanism for this, so we'd likely have to write some extra code. One possible solution is to initialize the IDs in the [MDC|https://logging.apache.org/log4j/1.2/apidocs/org/apache/log4j/MDC.html] and extract by updating the {{ConversionPattern}} as [described here|http://stackoverflow.com/a/12202124].


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