Here is some code that I used. I made the Kafka Ignite Streamer as a service
in Ignite and deploy it as a cluster singleton.
public class IgniteKafkaStreamerService implements Service {
private static final long serialVersionUID = 1L;
@IgniteInstanceResource
Here is more a precise instruction on how to set up both discovery and
communication modules so that the machines are not end up in a single cluster;
https://apacheignite.readme.io/docs/cluster-config#section-isolated-ignite-clusters-on-same-set-of-machines
—
Denis
> On May 14, 2017, at 8:31
Hi!
To start Ignite cluster you need to:
1) copy ignite binary distributive on each machine.
2) configure discovery, see
https://apacheignite.readme.io/docs/cluster-config
On Sun, May 14, 2017 at 8:42 PM, ? ? wrote:
> Dear all,
>
> I notice that /bin/ignite.sh will
Dear all,
I notice that /bin/ignite.sh will start ignite, and ignite will automatically
discover each other.
I have several machines in same subnet, and want to run ignite in each machine,
not in cluster mode.
To achieve this, how to start ignite using command? Many thanks.
Hi, Ilya,
I've tried to reproduce deployment problem in standalone project involving
Ingnite.start() in several WAR files. But this test is still passing.
It is still possible deployment problem can be reprdoced only
when GridDeploymentClassLoader is used for loading class on server, and
several