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] [Commented] (HDFS-3375) Put client name in DataXceiver thread name for readBlock and keepalive
Date Mon, 07 May 2012 20:46:52 GMT

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

Todd Lipcon commented on HDFS-3375:
-----------------------------------

Since this just changes thread names, no new unit tests. I did verify manually on a cluster
with jstack output:


- While uploading a file:

"DataXceiver for client DFSClient_NONMAPREDUCE_-769101204_1 at /127.0.0.1:45087 [Receiving
block BP-1115842170-127.0.0.1-1336423035296:blk_1601307317176587197_1002]" daemon prio=10
tid=0x0000000040ff6000 nid=0x6215 runnable [0x00007fe5188c8000]

- While downloading the same file

"DataXceiver for client DFSClient_NONMAPREDUCE_-412315870_1 at /127.0.0.1:51891 [Sending block
BP-1115842170-127.0.0.1-1336423035296:blk_1601307317176587197_1002]" daemon prio=10 tid=0x0000000040bb8000
nid=0xa83 runnable [0x00007fe5188c9000]

- During keepalive:
"DataXceiver for client DFSClient_NONMAPREDUCE_-1536450876_1 at /127.0.0.1:51896 [Waiting
for operation #111]" daemon prio=10 tid=0x00000000409a3000 nid=0x38f3 runnable [0x00007fe5188c9000]

                
> 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