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

ASF GitHub Bot commented on HDFS-16684:
---------------------------------------

saintstack commented on PR #4786:
URL: https://github.com/apache/hadoop/pull/4786#issuecomment-1229257567

   Looking at failed tests.....
   
   Run 1
   
   hadoop.hdfs.server.datanode.TestDataNodeRollingUpgrade
   --
     | hadoop.hdfs.server.namenode.ha.TestRetryCacheWithHA
     | hadoop.hdfs.server.datanode.TestBPOfferService
   
   
   Run 2
   
   hadoop.hdfs.server.datanode.TestDataNodeRollingUpgrade
   --
     | hadoop.hdfs.server.namenode.TestNameNodeMXBean
     | hadoop.hdfs.TestDecommissionWithStriped
     | hadoop.hdfs.server.namenode.TestFsck
     | hadoop.hdfs.server.balancer.TestBalancerWithHANameNodes
   
   
   Run 3
   
   hadoop.hdfs.server.datanode.TestDataNodeRollingUpgrade
   --
     | hadoop.hdfs.server.datanode.TestBPOfferService
     | hadoop.hdfs.server.balancer.TestBalancer
     | hadoop.hdfs.TestDecommission
     | hadoop.hdfs.server.namenode.TestFsck
   
   .... the one common failure is 
hadoop.hdfs.server.datanode.TestDataNodeRollingUpgrade. Let me try another 
run...
   
   
   




> Exclude self from JournalNodeSyncer when using a bind host
> ----------------------------------------------------------
>
>                 Key: HDFS-16684
>                 URL: https://issues.apache.org/jira/browse/HDFS-16684
>             Project: Hadoop HDFS
>          Issue Type: Improvement
>          Components: journal-node
>    Affects Versions: 3.4.0, 3.3.9
>         Environment: Running with Java 11 and bind addresses set to 0.0.0.0.
>            Reporter: Steve Vaughan
>            Assignee: Steve Vaughan
>            Priority: Major
>              Labels: pull-request-available
>             Fix For: 3.4.0, 3.3.9
>
>
> The JournalNodeSyncer will include the local instance in syncing when using a 
> bind host (e.g. 0.0.0.0).  There is a mechanism that is supposed to exclude 
> the local instance, but it doesn't recognize the meta-address as a local 
> address.
> Running with bind addresses set to 0.0.0.0, the JournalNodeSyncer will log 
> attempts to sync with itself as part of the normal syncing rotation.  For an 
> HA configuration running 3 JournalNodes, the "other" list used by the 
> JournalNodeSyncer will include 3 proxies.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

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

Reply via email to