How does Ignite work?


#1

During startup we see this message:

±---------------------------------------------------------------------+
Ignite ver. 2.3.0#20171028-sha1:8add7fd5b501b40658096cdde48af9e948aa8150
±---------------------------------------------------------------------+
OS name: Windows NT (unknown) 10.0 amd64
CPU(s): 2
Heap: 1.6GB
VM name: [email protected]
Ignite instance name: enonic-xp-ignite-instance
Local node [ID=F1CFBD99-8C94-4730-80E4-24E38FF9CE00, order=2, clientMode=false]
Local node addresses: [mycomputer/10.0.0.1]
Local ports: TCP:47100 TCP:47500

We’re running multiple clusters in our network. Will the instance name and/or local port conflict in any way with other clusters or is it used for something else?


#2

The instance name should not pose any problem here.
For the port you would have the same problems as with ElasticSearch already.

Are you running multiple Enonic nodes on the same machine?

  • If not, then you can leave the default port, the same as for ElasticSearch.
  • If you do (because you want to have a cluster locally for example), then you need to change the “discovery.tcp.port.range” in the Ignite config file “com.enonic.xp.ignite.cfg”

Some more information about clustering: https://xp.readthedocs.io/en/stable/operations/clustering.html