[ 
https://issues.apache.org/jira/browse/HDFS-16623?focusedWorklogId=780412&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-780412
 ]

ASF GitHub Bot logged work on HDFS-16623:
-----------------------------------------

                Author: ASF GitHub Bot
            Created on: 10/Jun/22 19:01
            Start Date: 10/Jun/22 19:01
    Worklog Time Spent: 10m 
      Work Description: cnauroth merged PR #4409:
URL: https://github.com/apache/hadoop/pull/4409




Issue Time Tracking
-------------------

    Worklog Id:     (was: 780412)
    Time Spent: 1h 10m  (was: 1h)

> IllegalArgumentException in LifelineSender
> ------------------------------------------
>
>                 Key: HDFS-16623
>                 URL: https://issues.apache.org/jira/browse/HDFS-16623
>             Project: Hadoop HDFS
>          Issue Type: Bug
>            Reporter: ZanderXu
>            Assignee: ZanderXu
>            Priority: Major
>              Labels: pull-request-available
>             Fix For: 3.4.0, 3.2.4, 3.3.4
>
>          Time Spent: 1h 10m
>  Remaining Estimate: 0h
>
> In our production environment, an IllegalArgumentException occurred in the 
> LifelineSender at one DataNode which was undergoing GC at that time. 
> And the bug code is at line 1060 in BPServiceActor.java, because the sleep 
> time is negative.
> {code:java}
> while (shouldRun()) {
>      try {
>         if (lifelineNamenode == null) {
>           lifelineNamenode = dn.connectToLifelineNN(lifelineNnAddr);
>         }
>         sendLifelineIfDue();
>         Thread.sleep(scheduler.getLifelineWaitTime());
>       } catch (InterruptedException e) {
>         Thread.currentThread().interrupt();
>       } catch (IOException e) {
>         LOG.warn("IOException in LifelineSender for " + BPServiceActor.this, 
> e);
>      }
> }
> {code}



--
This message was sent by Atlassian Jira
(v8.20.7#820007)

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

Reply via email to