About extra data node?

[yucigou <yu...@gmail.com>]

Hi,

Currently we have four web app servers, which are session-clustered via
Ignite. 

I've also added a fifth server as a data note, which is of the same capacity
of the other four servers, CPU/memory wise. This node is not a web app
server, but just part of the cluster as an extra server node. It is expected
that this extra node would help protect/keep the clustered data in the event
of all web app servers being down for any reason.

Just wonder if you could have any comment on this setup. Is it a good
practice, or not really necessary? Or there are other better options please?

Many thanks,
Yuci



--
View this message in context: http://apache-ignite-users.70518.x6.nabble.com/About-extra-data-node-tp8290.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.

Re: About extra data node?

[vkulichenko <va...@gmail.com>]

Yuci,

If you intend to scale dynamically, I would recommend to start standalone
server nodes and run nodes embedded in the app as clients [1]. This will
allow you to separate the load and scale two parts of this architecture
separately. For faster access on the client you can utilize near cache [2].

Also keep in mind that if you lose all nodes except one at a time, you will
most likely lose some data, unless you're using replicated cache. If there
is a big risk that such thing will happen and you want to avoid data loss in
this scenario, replicated cache in a must for you.

[1] https://apacheignite.readme.io/docs/clients-vs-servers
[2] https://apacheignite.readme.io/docs/near-caches

-Val



--
View this message in context: http://apache-ignite-users.70518.x6.nabble.com/About-extra-data-node-tp8290p8307.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.