hadoop-hdfs-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Todd Lipcon (JIRA)" <j...@apache.org>
Subject [jira] [Updated] (HDFS-3375) Put client name in DataXceiver thread name for readBlock and keepalive
Date Mon, 07 May 2012 21:36:49 GMT

     [ https://issues.apache.org/jira/browse/HDFS-3375?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel

Todd Lipcon updated HDFS-3375:

       Resolution: Fixed
    Fix Version/s: 2.0.0
     Hadoop Flags: Reviewed
           Status: Resolved  (was: Patch Available)

Committed to 2.0 and trunk. Thanks for reviewing, Aaron.
> 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
>             Fix For: 2.0.0
>         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


View raw message