0
我试图在Hazelcast 3.6 EA中使用基于jClouds的新发现机制。但是,无法使用与原生AWS发现完全相同的凭据进行工作。这里有两个CONFIGS:jClouds发现不适用于Hazelcast 3.6 EA
本地AWS(作品):
<network>
<join>
<multicast enabled="false" />
<tcp-ip enabled="false" />
<aws enabled="true">
<access-key>AKIAXXXXXXXXXXXXX</access-key>
<secret-key>YYYYYYYYYYYYYYYYY</secret-key>
<region>eu-west-1</region>
<host-header>ec2.amazonaws.com</host-header>
</aws>
</join>
</network>
jClouds(不工作):
<properties>
<property name="hazelcast.discovery.enabled">true</property>
</properties>
<network>
<join>
<multicast enabled="false" />
<tcp-ip enabled="false" />
<aws enabled="false" />
<discovery-strategies>
<discovery-strategy class="com.hazelcast.jclouds.JCloudsDiscoveryStrategy" enabled="true">
<properties>
<property name="provider">aws-ec2</property>
<property name="identity">AKIAXXXXXXXXXXXXX</property>
<property name="credential">YYYYYYYYYYYYYYYYY</property>
<property name="regions">eu-west-1</property>
</properties>
</discovery-strategy>
</discovery-strategies>
</join>
</network>
更多设置:2种情况下它们是相同的弹性部分Beanstalk应用程序。端口5701公开(用于测试)。为Hazelcast启用DEBUG日志级别。 AWS用户必须执行ec2:describe*
启用jClouds发现的权限,每个节点只看到自己:
DEBUG: Log4jFactory.java:93 [172.31.5.117]:5701 [dev] [3.6-EA] This node will assume master role since no possible member where connected to.
DEBUG: Log4jFactory.java:93 [172.31.5.117]:5701 [dev] [3.6-EA] This node is being set as the master
DEBUG: Log4jFactory.java:93 [172.31.5.117]:5701 [dev] [3.6-EA] PostJoin master: Address[172.31.5.117]:5701, isMaster: true
INFO : Log4jFactory.java:99 [172.31.5.117]:5701 [dev] [3.6-EA]
Members [1] {
Member [172.31.5.117]:5701 this
}
你可以试试3.6-EA2吗?如果您仍然遇到问题,我们很乐意为您提供帮助。 http://hazelcast.org/download/ – Mesut
@Mesut刚刚尝试过3.6-EA3,完美适用于jclouds和IAM角色。谢谢! – Rustam