Scala Akka |如何将多个群集节点作为来自不同JVM的一个群集连接

如何解决Scala Akka |如何将多个群集节点作为来自不同JVM的一个群集连接

经过2天的尝试和错误,也许有人可以指出我正确的方向。

我希望不同机器上的2个群集节点(在本例中为2个EC2实例)作为1个群集与公共IP(第一个EC2实例中的公共IP)协作。加入节点不应仅局限于EC2。

登录启动器EC2:

[INFO] [08/18/2020 18:02:02.741] [run-main-0] [ArteryTcpTransport(akka://RTJVMCluster)] Remoting started with transport [Artery tcp]; listening on address [akka://RTJVMCluster@18.185.238.129:2550] and bound to [akka://RTJVMCluster@172.31.28.140:2550] with UID [235194870536733302]
[INFO] [08/18/2020 18:02:02.779] [run-main-0] [Cluster(akka://RTJVMCluster)] Cluster Node [akka://RTJVMCluster@18.185.238.129:2550] - Starting up,Akka version [2.6.8] ...
[INFO] [08/18/2020 18:02:03.042] [run-main-0] [Cluster(akka://RTJVMCluster)] Cluster Node [akka://RTJVMCluster@18.185.238.129:2550] - Registered cluster JMX MBean [akka:type=Cluster]
[INFO] [08/18/2020 18:02:03.042] [run-main-0] [Cluster(akka://RTJVMCluster)] Cluster Node [akka://RTJVMCluster@18.185.238.129:2550] - Started up successfully
[INFO] [08/18/2020 18:02:03.164] [RTJVMCluster-akka.actor.default-dispatcher-10] [akka://RTJVMCluster/system/cluster/core/daemon/downingProvider] SBR started. Config: stableAfter: 20000 ms,strategy: KeepMajority,selfUniqueAddress: UniqueAddress(akka://RTJVMCluster@18.185.238.129:2550,235194870536733302),selfDc: default
[INFO] [akkaMemberChanged][08/18/2020 18:02:03.209] [RTJVMCluster-akka.actor.internal-dispatcher-4] [Cluster(akka://RTJVMCluster)] Cluster Node [akka://RTJVMCluster@18.185.238.129:2550] - Node [akka://RTJVMCluster@18.185.238.129:2550] is JOINING itself (with roles [dc-default]) and forming new cluster
[INFO] [08/18/2020 18:02:03.211] [RTJVMCluster-akka.actor.internal-dispatcher-4] [Cluster(akka://RTJVMCluster)] Cluster Node [akka://RTJVMCluster@18.185.238.129:2550] - is the new leader among reachable nodes (more leaders may exist)
[INFO] [akkaMemberChanged][08/18/2020 18:02:03.234] [RTJVMCluster-akka.actor.internal-dispatcher-4] [Cluster(akka://RTJVMCluster)] Cluster Node [akka://RTJVMCluster@18.185.238.129:2550] - Leader is moving node [akka://RTJVMCluster@18.185.238.129:2550] to [Up]
[INFO] [08/18/2020 18:02:03.291] [RTJVMCluster-akka.actor.default-dispatcher-10] [akka://RTJVMCluster/system/cluster/core/daemon/downingProvider] This node is now the leader responsible for taking SBR decisions among the reachable nodes (more leaders may exist).
[WARN] [08/18/2020 18:03:10.744] [RTJVMCluster-akka.remote.default-remote-dispatcher-7] [akka.stream.Log(akka://RTJVMCluster/system/Materializers/StreamSupervisor-1)] [outbound connection to [akka://RTJVMCluster@18.185.238.129:2551],message stream] Upstream failed,cause: StreamTcpException: Tcp command [Connect(18.185.238.129:2551,None,List(),Some(5000 milliseconds),true)] failed because of java.net.ConnectException: Connection refused

登录第二个EC2:

[INFO] [08/18/2020 18:03:09.628] [run-main-0] [ArteryTcpTransport(akka://RTJVMCluster)] Remoting started with transport [Artery tcp]; listening on address [akka://RTJVMCluster@18.185.238.129:2551] and bound to [akka://RTJVMCluster@172.31.23.84:2550] with UID [969183754535976376]
[INFO] [08/18/2020 18:03:09.665] [run-main-0] [Cluster(akka://RTJVMCluster)] Cluster Node [akka://RTJVMCluster@18.185.238.129:2551] - Starting up,Akka version [2.6.8] ...
[INFO] [08/18/2020 18:03:09.772] [run-main-0] [Cluster(akka://RTJVMCluster)] Cluster Node [akka://RTJVMCluster@18.185.238.129:2551] - Registered cluster JMX MBean [akka:type=Cluster]
[INFO] [08/18/2020 18:03:09.775] [run-main-0] [Cluster(akka://RTJVMCluster)] Cluster Node [akka://RTJVMCluster@18.185.238.129:2551] - Started up successfully
[INFO] [08/18/2020 18:03:09.917] [RTJVMCluster-akka.actor.default-dispatcher-10] [akka://RTJVMCluster/system/cluster/core/daemon/downingProvider] SBR started. Config: stableAfter: 20000 ms,selfUniqueAddress: UniqueAddress(akka://RTJVMCluster@18.185.238.129:2551,969183754535976376),selfDc: default
[WARN] [akkaJoinFailed][08/18/2020 18:03:20.156] [RTJVMCluster-akka.actor.internal-dispatcher-2] [Cluster(akka://RTJVMCluster)] Cluster Node [akka://RTJVMCluster@18.185.238.129:2551] - Couldn't join seed nodes after [2] attempts,will try again. seed-nodes=[akka://RTJVMCluster@18.185.238.129:2550]

到目前为止,我相信第二个EC2实例可以连接到我启动第一个ActorSystem的第一个EC2实例,但是我不明白为什么连接被拒绝。

Scala应用代码(EC2 1和EC2 2):

package example

import akka.actor.ActorSystem
import com.typesafe.config.ConfigFactory

object Test extends App {
  val config = ConfigFactory.load("configuration.conf")
  ActorSystem("RTJVMCluster",config)
}

configuration.conf | EC2 1 :(此EC2首先启动)

akka {
    actor {
        provider = "cluster"
    }

    remote {
        artery {
            enabled = on
            transport = tcp
            canonical.hostname = "18.185.238.129"      # external (logical) hostname
            canonical.port = 2550

            # EC2 1
            bind.hostname = "172.31.28.140"            # internal (bind) hostname
            bind.port = 2550                           # internal (bind) port
        }
    }

  cluster {
    seed-nodes = ["akka://RTJVMCluster@18.185.238.129:2550"]
    downing-provider-class = "akka.cluster.sbr.SplitBrainResolverProvider"
  }
}

configuration.conf | EC2 2:

akka {
    actor {
        provider = "cluster"
    }

    remote {
        artery {
            enabled = on
            transport = tcp
            canonical.hostname = "18.185.238.129"      # external (logical) hostname
            canonical.port = 2551

            # EC2 2
            bind.hostname = "172.31.23.84"             # internal (bind) hostname
            bind.port = 2550                           # internal (bind) port
        }
    }

  cluster {
    seed-nodes = ["akka://RTJVMCluster@18.185.238.129:2550"]
    downing-provider-class = "akka.cluster.sbr.SplitBrainResolverProvider"
  }
}

.jvmopts

-Djava.net.preferIPv4Stack=true
-Dcom.sun.management.jmxremote
-Dcom.sun.management.jmxremote.ssl=false
-Dcom.sun.management.jmxremote.authenticate=false
-Xms256m
-Xmx512m

还尝试了其他选项,例如:-Dakka.remote.port = 2550和2551 | -Dcom.sun.management.jmxremote.port = 2550和2551 | -Dcom.sun.management.jmxremote.rmi.port = 2550和2551 | -Djava.rmi.server.hostname = ec2-18-185-238-129.eu-central-1.compute.amazonaws.com

build.sbt

name := "test"
version := "1.0"
scalaVersion := "2.13.3" 

lazy val akkaVersion = "2.6.8"

libraryDependencies ++= Seq(
  "com.typesafe.akka" %% "akka-actor" % akkaVersion,"com.typesafe.akka" %% "akka-stream" % akkaVersion,"com.typesafe.akka" %% "akka-http"   % "10.2.0","com.typesafe.akka" %% "akka-cluster" % akkaVersion,"com.typesafe.akka" %% "akka-remote" % akkaVersion,)

在EC2实例上,所有入站和出站端口都是开放的。

任何有关如何使用公共ip从不同机器连接多个节点的帮助都将受到高度赞赏!

版权声明:本文内容由互联网用户自发贡献,该文观点与技术仅代表作者本人。本站仅提供信息存储空间服务,不拥有所有权,不承担相关法律责任。如发现本站有涉嫌侵权/违法违规的内容, 请发送邮件至 dio@foxmail.com 举报,一经查实,本站将立刻删除。

相关推荐


依赖报错 idea导入项目后依赖报错,解决方案:https://blog.csdn.net/weixin_42420249/article/details/81191861 依赖版本报错:更换其他版本 无法下载依赖可参考:https://blog.csdn.net/weixin_42628809/a
错误1:代码生成器依赖和mybatis依赖冲突 启动项目时报错如下 2021-12-03 13:33:33.927 ERROR 7228 [ main] o.s.b.d.LoggingFailureAnalysisReporter : *************************** APPL
错误1:gradle项目控制台输出为乱码 # 解决方案:https://blog.csdn.net/weixin_43501566/article/details/112482302 # 在gradle-wrapper.properties 添加以下内容 org.gradle.jvmargs=-Df
错误还原:在查询的过程中,传入的workType为0时,该条件不起作用 <select id="xxx"> SELECT di.id, di.name, di.work_type, di.updated... <where> <if test=&qu
报错如下,gcc版本太低 ^ server.c:5346:31: 错误:‘struct redisServer’没有名为‘server_cpulist’的成员 redisSetCpuAffinity(server.server_cpulist); ^ server.c: 在函数‘hasActiveC
解决方案1 1、改项目中.idea/workspace.xml配置文件,增加dynamic.classpath参数 2、搜索PropertiesComponent,添加如下 <property name="dynamic.classpath" value="tru
删除根组件app.vue中的默认代码后报错:Module Error (from ./node_modules/eslint-loader/index.js): 解决方案:关闭ESlint代码检测,在项目根目录创建vue.config.js,在文件中添加 module.exports = { lin
查看spark默认的python版本 [root@master day27]# pyspark /home/software/spark-2.3.4-bin-hadoop2.7/conf/spark-env.sh: line 2: /usr/local/hadoop/bin/hadoop: No s
使用本地python环境可以成功执行 import pandas as pd import matplotlib.pyplot as plt # 设置字体 plt.rcParams['font.sans-serif'] = ['SimHei'] # 能正确显示负号 p
错误1:Request method ‘DELETE‘ not supported 错误还原:controller层有一个接口,访问该接口时报错:Request method ‘DELETE‘ not supported 错误原因:没有接收到前端传入的参数,修改为如下 参考 错误2:cannot r
错误1:启动docker镜像时报错:Error response from daemon: driver failed programming external connectivity on endpoint quirky_allen 解决方法:重启docker -> systemctl r
错误1:private field ‘xxx‘ is never assigned 按Altʾnter快捷键,选择第2项 参考:https://blog.csdn.net/shi_hong_fei_hei/article/details/88814070 错误2:启动时报错,不能找到主启动类 #
报错如下,通过源不能下载,最后警告pip需升级版本 Requirement already satisfied: pip in c:\users\ychen\appdata\local\programs\python\python310\lib\site-packages (22.0.4) Coll
错误1:maven打包报错 错误还原:使用maven打包项目时报错如下 [ERROR] Failed to execute goal org.apache.maven.plugins:maven-resources-plugin:3.2.0:resources (default-resources)
错误1:服务调用时报错 服务消费者模块assess通过openFeign调用服务提供者模块hires 如下为服务提供者模块hires的控制层接口 @RestController @RequestMapping("/hires") public class FeignControl
错误1:运行项目后报如下错误 解决方案 报错2:Failed to execute goal org.apache.maven.plugins:maven-compiler-plugin:3.8.1:compile (default-compile) on project sb 解决方案:在pom.
参考 错误原因 过滤器或拦截器在生效时,redisTemplate还没有注入 解决方案:在注入容器时就生效 @Component //项目运行时就注入Spring容器 public class RedisBean { @Resource private RedisTemplate<String
使用vite构建项目报错 C:\Users\ychen\work>npm init @vitejs/app @vitejs/create-app is deprecated, use npm init vite instead C:\Users\ychen\AppData\Local\npm-