HAProxy背后的Akka Remoting

Question

我试图将远程Akka 系统 （简称为system1 ）放在HAProxy后面，并通过代理由另一个系统（简称为system2 ）使用。 我正在使用具有“ bind-hostname”功能的Akka 2.4（是的，我正在快照存储库中使用Akka，因为在Docker中没有其他Akka选项）。

为system1配置：

akka {
  loglevel = DEBUG
  actor {
    provider = "akka.remote.RemoteActorRefProvider"
  }
  remote {
    netty.tcp {
      bind-hostname = "0.0.0.0"
      bind-port = 9000

      hostname = ${proxyServerIp}
      port = 9000
    }
  }
}

和配置system2 ：

akka {
  loglevel = DEBUG
  actor {
    provider = "akka.remote.RemoteActorRefProvider"
  }
  remote {
    netty.tcp {
      bind-hostname = "0.0.0.0"
      bind-port = 9001

      hostname = ${proxyServerIp}
      port = 9001
    }
  }
}

其中proxyServerIp是具有HAProxy的服务器。 我已经在本地测试了配置，用本地计算机的IP地址替换了proxyServerIp ，并且没有错误。 但是，当我尝试在产品上启动它时，在system1上得到了以下内容：

Feb 20 01:58:37 where12 sh[30586]: [DEBUG] [02/20/2015 01:58:37.113] [System1-akka.remote.default-remote-dispatcher-6] [akka.remote.Remoting] Associated [akka.tcp://System1@10.130.184.248:9000] <- [akka.tcp://System2@10.130.184.248:9001]
Feb 20 01:58:37 where12 sh[30586]: [INFO] [02/20/2015 01:58:37.330] [System1-akka.actor.default-dispatcher-2] [akka://System1/user/EntryExtractingActor] Message [wh.extractor.ExtractedEntry] from Actor[akka://System1/deadLetters] to Actor[akka://System1/user/EntryExtractingActor] 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'.
Feb 20 01:58:37 where12 sh[30586]: [INFO] [02/20/2015 01:58:37.334] [System1-akka.actor.default-dispatcher-2] [akka://System1/user/EntryExtractingActor] Message [wh.extractor.ExtractedEntry] from Actor[akka://System1/deadLetters] to Actor[akka://System1/user/EntryExtractingActor] was not delivered. [2] 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'.
Feb 20 01:58:37 where12 sh[30586]: [INFO] [02/20/2015 01:58:37.337] [System1-akka.actor.default-dispatcher-2] [akka://System1/user/EntryExtractingActor] Message [wh.extractor.ExtractedEntry] from Actor[akka://System1/deadLetters] to Actor[akka://System1/user/EntryExtractingActor] was not delivered. [3] 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'.
Feb 20 01:58:37 where12 sh[30586]: [INFO] [02/20/2015 01:58:37.340] [System1-akka.actor.default-dispatcher-2] [akka://System1/user/EntryExtractingActor] Message [wh.extractor.ExtractedEntry] from Actor[akka://System1/deadLetters] to Actor[akka://System1/user/EntryExtractingActor] was not delivered. [4] 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'.
Feb 20 01:58:39 where12 sh[30586]: [INFO] [02/20/2015 01:58:39.392] [System1-akka.actor.default-dispatcher-2] [akka://System1/user/EntryExtractingActor] Message [wh.extractor.ExtractedEntry] from Actor[akka://System1/deadLetters] to Actor[akka://System1/user/EntryExtractingActor] was not delivered. [5] 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'.
Feb 20 01:58:39 where12 sh[30586]: [INFO] [02/20/2015 01:58:39.395] [System1-akka.actor.default-dispatcher-2] [akka://System1/user/EntryExtractingActor] Message [wh.extractor.ExtractedEntry] from Actor[akka://System1/deadLetters] to Actor[akka://System1/user/EntryExtractingActor] was not delivered. [6] 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'.
Feb 20 01:58:39 where12 sh[30586]: [INFO] [02/20/2015 01:58:39.398] [System1-akka.actor.default-dispatcher-2] [akka://System1/user/EntryExtractingActor] Message [wh.extractor.ExtractedEntry] from Actor[akka://System1/deadLetters] to Actor[akka://System1/user/EntryExtractingActor] was not delivered. [7] 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'.
Feb 20 01:58:39 where12 sh[30586]: [INFO] [02/20/2015 01:58:39.416] [System1-akka.actor.default-dispatcher-2] [akka://System1/user/EntryExtractingActor] Message [wh.extractor.ExtractedEntry] from Actor[akka://System1/deadLetters] to Actor[akka://System1/user/EntryExtractingActor] was not delivered. [8] 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'.
Feb 20 01:58:39 where12 sh[30586]: [INFO] [02/20/2015 01:58:39.431] [System1-akka.actor.default-dispatcher-2] [akka://System1/user/EntryExtractingActor] Message [wh.extractor.ExtractedEntry] from Actor[akka://System1/deadLetters] to Actor[akka://System1/user/EntryExtractingActor] was not delivered. [9] 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'.
Feb 20 01:58:39 where12 sh[30586]: [INFO] [02/20/2015 01:58:39.433] [System1-akka.actor.default-dispatcher-2] [akka://System1/user/EntryExtractingActor] Message [wh.extractor.ExtractedEntry] from Actor[akka://System1/deadLetters] to Actor[akka://System1/user/EntryExtractingActor] was not delivered. [10] dead letters encountered, no more dead letters will be logged. This logging can be turned off or adjusted with configuration settings 'akka.log-dead-letters' and 'akka.log-dead-letters-during-shutdown'.
Feb 20 01:58:40 where12 sh[30586]: [DEBUG] [02/20/2015 01:58:40.604] [System1-akka.remote.default-remote-dispatcher-14] [akka.remote.Remoting] Associated [akka.tcp://System1@10.130.184.248:9000] <- [akka.tcp://System2@10.130.184.248:9001]
Feb 20 01:58:40 where12 sh[30586]: [DEBUG] [02/20/2015 01:58:40.633] [System1-akka.remote.default-remote-dispatcher-14] [akka.tcp://System1@10.130.184.248:9000/system/endpointManager/reliableEndpointWriter-akka.tcp%3A%2F%2FSystem2%4010.130.184.248%3A9001-0/endpointWriter] Disassociated [akka.tcp://System1@10.130.184.248:9000] <- [akka.tcp://System2@10.130.184.248:9001]
Feb 20 01:58:46 where12 sh[30586]: [DEBUG] [02/20/2015 01:58:46.437] [System1-akka.remote.default-remote-dispatcher-6] [akka.remote.Remoting] Associated [akka.tcp://System1@10.130.184.248:9000] <- [akka.tcp://System2@10.130.184.248:9001]
Feb 20 01:58:46 where12 sh[30586]: [DEBUG] [02/20/2015 01:58:46.449] [System1-akka.remote.default-remote-dispatcher-6] [akka.tcp://System1@10.130.184.248:9000/system/endpointManager/reliableEndpointWriter-akka.tcp%3A%2F%2FSystem2%4010.130.184.248%3A9001-1/endpointWriter] Disassociated [akka.tcp://System1@10.130.184.248:9000] <- [akka.tcp://System2@10.130.184.248:9001]
Feb 20 01:58:53 where12 sh[30586]: [DEBUG] [02/20/2015 01:58:53.792] [System1-akka.remote.default-remote-dispatcher-6] [akka.remote.Remoting] Associated [akka.tcp://System1@10.130.184.248:9000] <- [akka.tcp://System2@10.130.184.248:9001]
Feb 20 01:58:53 where12 sh[30586]: [DEBUG] [02/20/2015 01:58:53.807] [System1-akka.remote.default-remote-dispatcher-14] [akka.tcp://System1@10.130.184.248:9000/system/endpointManager/reliableEndpointWriter-akka.tcp%3A%2F%2FSystem2%4010.130.184.248%3A9001-2/endpointWriter] Disassociated [akka.tcp://System1@10.130.184.248:9000] <- [akka.tcp://System2@10.130.184.248:9001]

以及以下system2 ：

Feb 20 02:00:43 where12 sh[30704]: [DEBUG] [02/20/2015 02:00:43.685] [System2-akka.remote.default-remote-dispatcher-14] [akka.tcp://System2@10.130.184.248:9001/system/endpointManager/reliableEndpointWriter-akka.tcp%3A%2F%2FSystem1%4010.130.184.248%3A9000-0/endpointWriter] Associated [akka.tcp://System2@10.130.184.248:9001] -> [akka.tcp://System1@10.130.184.248:9000]
Feb 20 02:00:43 where12 sh[30704]: [DEBUG] [02/20/2015 02:00:43.830] [System2-akka.remote.default-remote-dispatcher-6] [akka.tcp://System2@10.130.184.248:9001/system/endpointManager/reliableEndpointWriter-akka.tcp%3A%2F%2FSystem1%4010.130.184.248%3A9000-0/endpointWriter] Drained buffer with maxWriteCount: 50, fullBackoffCount: 1, smallBackoffCount: 0, noBackoffCount: 5 , adaptiveBackoff: 1000
Feb 20 02:01:01 where12 sh[30704]: [DEBUG] [02/20/2015 02:01:01.448] [System2-akka.remote.default-remote-dispatcher-6] [akka.tcp://System2@10.130.184.248:9001/system/endpointManager/reliableEndpointWriter-akka.tcp%3A%2F%2FSystem1%4010.130.184.248%3A9000-0/endpointWriter] Disassociated [akka.tcp://System2@10.130.184.248:9001] -> [akka.tcp://System1@10.130.184.248:9000]
Feb 20 02:01:01 where12 sh[30704]: [WARN] [02/20/2015 02:01:01.451] [System2-akka.remote.default-remote-dispatcher-14] [akka.tcp://System2@10.130.184.248:9001/system/endpointManager/reliableEndpointWriter-akka.tcp%3A%2F%2FSystem1%4010.130.184.248%3A9000-0] Association with remote system [akka.tcp://System1@10.130.184.248:9000] has failed, address is now gated for [5000] ms. Reason: [Disassociated]
Feb 20 02:01:01 where12 sh[30704]: [DEBUG] [02/20/2015 02:01:01.452] [System2-akka.remote.default-remote-dispatcher-6] [akka.tcp://System2@10.130.184.248:9001/system/endpointManager/reliableEndpointWriter-akka.tcp%3A%2F%2FSystem1%4010.130.184.248%3A9000-0/endpointWriter] Disassociated [akka.tcp://System2@10.130.184.248:9001] ->[akka.tcp://System1@10.130.184.248:9000]
Feb 20 02:01:09 where12 sh[30704]: [DEBUG] [02/20/2015 02:01:08.613] [System2-akka.remote.default-remote-dispatcher-6] [akka.tcp://System2@10.130.184.248:9001/system/endpointManager/reliableEndpointWriter-akka.tcp%3A%2F%2FSystem1%4010.130.184.248%3A9000-0/endpointWriter] Associated [akka.tcp://System2@10.130.184.248:9001] -> [akka.tcp://System1@10.130.184.248:9000]
Feb 20 02:01:09 where12 sh[30704]: [DEBUG] [02/20/2015 02:01:08.950] [System2-akka.remote.default-remote-dispatcher-14] [akka.tcp://System2@10.130.184.248:9001/system/endpointManager/reliableEndpointWriter-akka.tcp%3A%2F%2FSystem1%4010.130.184.248%3A9000-0/endpointWriter] Drained buffer with maxWriteCount: 50, fullBackoffCount: 1, smallBackoffCount: 0, noBackoffCount: 5 , adaptiveBackoff: 1000

看起来消息到达了目标系统，但是由于某种原因没有被分发给参与者。 有什么想法吗？

PS我不想在负载均衡中使用Akka Clustering ，因为我已经为HAProxy实现了通用的（对于每个公开的Docker端口）服务发现，但是Akka Clustering将要求我实现另一个服务发现。

Answer 1

问题非常愚蠢：在迁移到平衡器通信时，我不小心在应用程序中引入了一个错误，因此Actors从未在系统中注册1 。