You are viewing a plain text version of this content. The canonical link for it is here.

Posted to hdfs-issues@hadoop.apache.org by "Mike Drob (Jira)" <ji...@apache.org> on 2022/03/07 18:21:00 UTC

[jira] [Commented] (HDFS-16478) Multiple command processor threads have same name

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

Mike Drob commented on HDFS-16478:
----------------------------------

Hi folks, there was a lot of discussion on the PR (and definitely more than I expected for a one line change) but it's not clear what the outstanding requested changes or impediments to merging are at this point.

[~ayushtkn] [~elgoiri] - is this good to go?

> Multiple command processor threads have same name
> -------------------------------------------------
>
>                 Key: HDFS-16478
>                 URL: https://issues.apache.org/jira/browse/HDFS-16478
>             Project: Hadoop HDFS
>          Issue Type: Task
>          Components: datanode
>            Reporter: Mike Drob
>            Priority: Minor
>              Labels: pull-request-available
>          Time Spent: 2h 10m
>  Remaining Estimate: 0h
>
> When running an in-process MiniDFSCluster with multiple data nodes, the command processor threads all share the same name, making them more difficult to get debug and logging information from.



--
This message was sent by Atlassian Jira
(v8.20.1#820001)

---------------------------------------------------------------------
To unsubscribe, e-mail: hdfs-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-help@hadoop.apache.org