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 "Ahmed Hussein (Jira)" <ji...@apache.org> on 2020/10/07 23:10:00 UTC

[jira] [Assigned] (HDFS-9409) DataNode shutdown does not guarantee full shutdown of all threads due to race condition.

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

Ahmed Hussein reassigned HDFS-9409:
-----------------------------------

    Assignee: Ahmed Hussein

> DataNode shutdown does not guarantee full shutdown of all threads due to race condition.
> ----------------------------------------------------------------------------------------
>
>                 Key: HDFS-9409
>                 URL: https://issues.apache.org/jira/browse/HDFS-9409
>             Project: Hadoop HDFS
>          Issue Type: Bug
>          Components: datanode
>            Reporter: Chris Nauroth
>            Assignee: Ahmed Hussein
>            Priority: Major
>
> {{DataNode#shutdown}} is documented to return "only after shutdown is complete".  Even after completion of this method, it's possible that threads started by the DataNode are still running.  Race conditions in the shutdown sequence may cause it to skip stopping and joining the {{BPServiceActor}} threads.
> This is likely not a big problem in normal operations, because these are daemon threads that won't block overall process exit.  It is more of a problem for tests, because it makes it impossible to write reliable assertions that these threads exited cleanly.  For large test suites, it can also cause an accumulation of unneeded threads, which might harm test performance.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

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