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

Uma Maheswara Rao G updated HDFS-12152:
---------------------------------------
       Resolution: Fixed
     Hadoop Flags: Reviewed
    Fix Version/s: HDFS-10285
           Status: Resolved  (was: Patch Available)

I have just pushed it to branch!

> [SPS]: Re-arrange StoragePolicySatisfyWorker stopping sequence to improve 
> thread cleanup time
> ---------------------------------------------------------------------------------------------
>
>                 Key: HDFS-12152
>                 URL: https://issues.apache.org/jira/browse/HDFS-12152
>             Project: Hadoop HDFS
>          Issue Type: Sub-task
>          Components: datanode, namenode
>            Reporter: Rakesh R
>            Assignee: Rakesh R
>            Priority: Minor
>             Fix For: HDFS-10285
>
>         Attachments: HDFS-12152-HDFS-10285-01.patch, 
> HDFS-12152-HDFS-10285-02.patch, HDFS-12152-HDFS-10285-03.patch
>
>
> This jira to improve the StoragePolicySatisfyWorker#stop sequence of steps to 
> improve the thread interruption and graceful shutdown quickly.
> I have observed that 
> [TestDataNodeUUID#testUUIDRegeneration|https://builds.apache.org/job/PreCommit-HDFS-Build/20271/testReport/org.apache.hadoop.hdfs.server.datanode/TestDataNodeUUID/testUUIDRegeneration/]
>  test case is getting timed out frequently. When analyzing, it looks like the 
> below function is always taking 3 secs waiting period. Probably, we could 
> improve the thread interruption sequence so that the thread should finish 
> #run method quickly.
> {code}
> StoragePolicySatisfyWorker.java
>   void waitToFinishWorkerThread() {
>     try {
>       movementTrackerThread.join(3000);
>     } catch (InterruptedException ignore) {
>       // ignore
>     }
>   }
> {code}



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to