Mailing-List: contact hdfs-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: hdfs-issues@hadoop.apache.org
Date: Tue, 4 Aug 2015 08:58:05 +0000 (UTC)
From: "Li Bo (JIRA)" <jira@apache.org>
To: hdfs-issues@hadoop.apache.org
Message-ID: <JIRA.12844548.1436763956000.364844.1438678685174@Atlassian.JIRA>
In-Reply-To: <JIRA.12844548.1436763956000@Atlassian.JIRA>
References: <JIRA.12844548.1436763956000@Atlassian.JIRA>
 <JIRA.12844548.1436763956976@arcas>
Subject: [jira] [Commented] (HDFS-8762) Erasure Coding: the log of each
 streamer should show its index
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Li Bo commented on HDFS-8762:
-----------------------------

Move this jira from HDFS-8031 to HDFS-7285. Because there're 9 data streamers in striped writing, it's difficult to find the error if you don't know which streamer the log is generated from.

> Erasure Coding: the log of each streamer should show its index
> --------------------------------------------------------------
>
>                 Key: HDFS-8762
>                 URL: https://issues.apache.org/jira/browse/HDFS-8762
>             Project: Hadoop HDFS
>          Issue Type: Sub-task
>            Reporter: Li Bo
>            Assignee: Li Bo
>         Attachments: HDFS-8762-HDFS-7285-001.patch
>
>
> The log in {{DataStreamer}} doesn't show which streamer it's generated from. In order to make log information more convenient for debugging, each log should include the index of the streamer it's generated from. 


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