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

Rakesh R commented on HDFS-11338:
---------------------------------

[~umamaheswararao], [~zhouwei]  Many tests are failing due to time out. This is 
due to the extra joining time out added to gracefully shutdown SPS threads. 

{code}
BlockStorageMovementAttemptedItems.java
      timerThread.interrupt();
      try {
        timerThread.join(3000);
      } catch (InterruptedException ie) {
      }
{code}

Below is already mentioned in the jira desc.
{code}
StoragePolicySatisfier.java
    storagePolicySatisfierThread.interrupt();
    try {
      storagePolicySatisfierThread.join(3000);
    } catch (InterruptedException ie) {
    }
{code}

Presently, we are enabling SPS feature by default, so that all these test cases 
are affected and spends extra time while stopping the server. IMHO, we could 
disable the SPS for these test cases rather than increasing the overall testing 
time.


> [SPS]: Fix timeout issue in unit tests caused by longger NN down time
> ---------------------------------------------------------------------
>
>                 Key: HDFS-11338
>                 URL: https://issues.apache.org/jira/browse/HDFS-11338
>             Project: Hadoop HDFS
>          Issue Type: Sub-task
>          Components: datanode, namenode
>            Reporter: Wei Zhou
>            Assignee: Wei Zhou
>         Attachments: HDFS-11338-HDFS-10285.00.patch, 
> HDFS-11338-HDFS-10285.01.patch
>
>
> As discussed in HDFS-11186, it takes longer to stop NN:
> {code}
> try {
>   storagePolicySatisfierThread.join(3000);
> } catch (InterruptedException ie) {
> }
> {code}
> So, it takes longer time to finish some tests and this leads to the timeout 
> failures.



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

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

Reply via email to