I have a cluster of 15 nodes/boxes. I start the nodes roughly at the same 
time. One of the nodes is behaving oddly and continually logging "Ignoring 
received gossip intended for someone else". However, the node does seem to 
work for a while before being being dropped from the cluster. Basically 
this one node seems to think it is someone else, whilst also behaviouring 
as itself. The code and config is exactly the same on all 15 nodes so I 
don't understand why I'm getting this issue on only one node. Maybe this is 
a hardware issue?

Some logging:

11:27:45.412 INFO  [main] Remoting - Starting remoting
11:27:45.638 INFO  [main] Remoting - Remoting started; listening on 
addresses :[akka.tcp://streaming@172.17.102.128:7000]
11:27:45.660 INFO  [main] Cluster(akka://streaming) - Cluster Node 
[akka.tcp://streaming@172.17.102.128:7000] - Starting up...
11:27:45.714 INFO  [main] Cluster(akka://streaming) - Cluster Node 
[akka.tcp://streaming@172.17.102.128:7000] - Registered cluster JMX MBean 
[akka:type=Cluster]
11:27:45.715 INFO  [main] Cluster(akka://streaming) - Cluster Node 
[akka.tcp://streaming@172.17.102.128:7000] - Started up successfully
11:27:45.830 INFO  [streaming-akka.actor.default-dispatcher-3] 
a.a.LocalActorRef - Message 
[akka.cluster.InternalClusterAction$InitJoinAck] from 
Actor[akka.tcp://streaming@172.17.100.98:7000/system/cluster/core/daemon#1997515880]
 
to 
Actor[akka://streaming/system/cluster/core/daemon/joinSeedNodeProcess-1#1132911]
 
was not delivered. [1] dead letters encountered. This logging can be turned 
off or adjusted with configuration settings 'akka.log-dead-letters' and 
'akka.log-dead-letters-during-shutdown'.
11:27:45.872 INFO  [streaming-akka.actor.default-dispatcher-5] 
Cluster(akka://streaming) - Cluster Node 
[akka.tcp://streaming@172.17.102.128:7000] - Welcome from 
[akka.tcp://streaming@172.17.102.125:7000]
11:27:45.911 INFO  [streaming-akka.actor.default-dispatcher-2] 
Cluster(akka://streaming) - Cluster Node 
[akka.tcp://streaming@172.17.102.128:7000] - Ignoring received gossip 
intended for someone else, from [akka.tcp://streaming@172.17.102.68:7000] 
to [UniqueAddress(akka.tcp://streaming@172.17.102.128:7000,-1482656725)]
11:27:45.943 INFO  [streaming-akka.actor.default-dispatcher-16] 
Cluster(akka://streaming) - Cluster Node 
[akka.tcp://streaming@172.17.102.128:7000] - Ignoring received gossip 
intended for someone else, from [akka.tcp://streaming@172.17.102.70:7000] 
to [UniqueAddress(akka.tcp://streaming@172.17.102.128:7000,-1482656725)]
11:27:46.122 INFO  [streaming-akka.actor.default-dispatcher-16] 
Cluster(akka://streaming) - Cluster Node 
[akka.tcp://streaming@172.17.102.128:7000] - Ignoring received gossip 
intended for someone else, from [akka.tcp://streaming@172.17.102.69:7000] 
to [UniqueAddress(akka.tcp://streaming@172.17.102.128:7000,-1482656725)]

Config:

akka {
  cluster {
    seed-nodes = [
      "akka.tcp://streaming@172.17.102.125:7000"
      "akka.tcp://streaming@172.17.100.98:7000"
    ]
  }
  remote.netty.tcp.hostname = 172.17.102.128
}

I thought it was weird that the unique address in the gossip messages 
referred to a negative number. I added log.info(s"my unique ID: 
${AddressUidExtension(actorSystem).addressUid}") to the confused node (I 
hope this is the correct code) and it gave me the answer "1549799231", 
whilst continuing to give "-1482656725" in the gossip messages. I'm 
guessing the problem is that the gossip messages have a corrupted address, 
which is why the confused node believes these messages are not for itself. 
I'm using Akka 2.3.2.


-- 
>>>>>>>>>>      Read the docs: http://akka.io/docs/
>>>>>>>>>>      Check the FAQ: 
>>>>>>>>>> http://doc.akka.io/docs/akka/current/additional/faq.html
>>>>>>>>>>      Search the archives: https://groups.google.com/group/akka-user
--- 
You received this message because you are subscribed to the Google Groups "Akka 
User List" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to akka-user+unsubscr...@googlegroups.com.
To post to this group, send email to akka-user@googlegroups.com.
Visit this group at http://groups.google.com/group/akka-user.
For more options, visit https://groups.google.com/d/optout.

Reply via email to