hazelcast / hazelcast-remote-controller

Hazelcast Remote Controller

Hazelcast Cluster lifecycle manager for native client tests. Server container and language clients provide easy management of server side from clients

Cluster methods running with server jars

• Create a cluster with a provided xml config
• Start a Member in the configured cluster
• Shutdown a member
• Terminate a member
• Remote script execution on the container

Cloud API usage

The documentation of the Cloud API is here; https://cloud.hazelcast.com/v1/api/explorer

Prerequisites for usage of Cloud API

Cloud credentials should be added as an env variable; baseUrl, apiKey, apiSecret; e.g. baseUrl=https://uat.hazelcast.cloud

API for native clients

• Create Standard and SSL enabled/disabled hazelcast cloud cluster
• Stop/Resume/Delete/Get cloud cluster
• Scale up/down cloud cluster

Project uses Apache Thrift to provide multi language support.

Mail Group

Please join the mail group if you are interested in using or developing Hazelcast.

http://groups.google.com/group/hazelcast

License

Hazelcast Remote Controller is available under the Apache 2 License.

Copyright

Copyright (c) 2008-2016, Hazelcast, Inc. All Rights Reserved.

Visit www.hazelcast.com for more info.

hazelcast-remote-controller's Issues

Add operations for split brain emulation

In order to emulate split brain we should add new operations to execute the following methods: HazelcastTestSupport#closeConnectionBetween,
SplitBrainTestSupport#blockCommunicationBetween, SplitBrainTestSupport#unblockCommunicationBetween

Examples of bugs where we need this functionality for bugfix tests:
hazelcast/hazelcast-python-client#272
hazelcast/hazelcast-nodejs-client#733

Update Main class to RemoteController to make the nameon on ps list definitive.

Initially connected member termination causes an inconsistent state

Scenario:
There are running members in the same cluster at ports 5701, 5702 and 5703 then default smart-client connected to those members. It first receives the member information from the first member that it is connected which is 5701 in this case. Then, connect all the remaining members via those information by listening certain event. After the client is ready, If we just terminate first member which is exploited for the discovery purpose through remote-controller, we just receive MembershipStateRemoved event as it is suppose to be. But when we attempt to add a new member through rc again, client does not receive MembershipStateAdded event. Rather, if we first remove the member which is discovered after the first member connection and add a new member again, rc works fine and throws MembershipStateAdded event. I tested both cases manually without the remote-controller in localhost, everything works fine as it is expected.

Gist: https://gist.github.com/nevzatseferoglu/37199fd3e2bcd7aa1cbdadc5843a2f5d
Slack discussion: https://hazelcast.slack.com/archives/C016TGXPWPJ/p1656085097529409