[
https://issues.apache.org/jira/browse/HDFS-4656?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13619818#comment-13619818
]
Hudson commented on HDFS-4656:
------------------------------
Integrated in Hadoop-Mapreduce-trunk #1389 (See
[https://builds.apache.org/job/Hadoop-Mapreduce-trunk/1389/])
HDFS-4656. DN heartbeat loop can be briefly tight. Contributed by Aaron T.
Myers. (Revision 1463357)
Result = SUCCESS
atm : http://svn.apache.org/viewcvs.cgi/?root=Apache-SVN&view=rev&rev=1463357
Files :
* /hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs/CHANGES.txt
*
/hadoop/common/trunk/hadoop-hdfs-project/hadoop-hdfs/src/main/java/org/apache/hadoop/hdfs/server/datanode/BPServiceActor.java
> DN heartbeat loop can be briefly tight
> --------------------------------------
>
> Key: HDFS-4656
> URL: https://issues.apache.org/jira/browse/HDFS-4656
> Project: Hadoop HDFS
> Issue Type: Bug
> Components: datanode
> Affects Versions: 2.0.4-alpha
> Reporter: Aaron T. Myers
> Assignee: Aaron T. Myers
> Priority: Minor
> Attachments: HDFS-4656.patch
>
>
> The DN hearbeat loop looks roughly like this:
> {code}
> if (now - timeOfLastHeartbeat > configuredHeartbeatInterval) {
> // do heartbeat
> }
> timeToWait = configuredHeartbeatInterval - (now - timeOfLastHeartbeat)
> sleep(timeToWait)
> {code}
> The trouble is that since we sleep for exactly the heartbeat interval, and
> then check to see if we have waited _more_ than that heartbeat interval, we
> will very often have waited exactly the heartbeat interval (in millis), and
> not more than it. In this case we will skip actually performing the heartbeat
> and will calculcate timeToWait as being 0ms. The DN heartbeat loop will then
> loop tightly for 1ms. The solution is just to change the "{{>}}" in the code
> above to "{{>=}}".
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
