hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Aaron T. Myers (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HDFS-3375) Put client name in DataXceiver thread name for readBlock and keepalive
Date Mon, 07 May 2012 02:50:51 GMT

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

Aaron T. Myers commented on HDFS-3375:
--------------------------------------

+1, the patch looks good to me.
                
> Put client name in DataXceiver thread name for readBlock and keepalive
> ----------------------------------------------------------------------
>
>                 Key: HDFS-3375
>                 URL: https://issues.apache.org/jira/browse/HDFS-3375
>             Project: Hadoop HDFS
>          Issue Type: Improvement
>          Components: data-node
>    Affects Versions: 2.0.0
>            Reporter: Todd Lipcon
>            Assignee: Todd Lipcon
>            Priority: Trivial
>         Attachments: hdfs-3375.txt
>
>
> Currently the datanode thread names include the client for write operations, but not
for read. We should include the client name for read ops. Additionally, in the keepalive phase,
we should include the client name that initiated the previous request as well.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message