You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@ignite.apache.org by Вячеслав Коптилин <sl...@gmail.com> on 2018/02/23 09:47:42 UTC

Re: how to dismiss a ignite server node.

Hello,

If you don't have configured 3rd party cache store or backups,
then there is only one possible way, I think.
You need to
 - store all the data from the node you want to shut down,
 - shut down the node
 - upload stored data back to the cluster.

It can be done via an external database, for example.
If the data set is not huge, you can try to use a new partitioned cache
(with node filter/backups) or replicated cache.

Thanks.

2018-02-23 10:00 GMT+03:00 shawn.du <sh...@neulion.com.cn>:

> Hi,
> Suppose I have several ignite server nodes which compose a cluster.
> all data in PARTITIONED mode, and with no backups.
> It is possible to dismiss a node without restarting and data lose?
> if possible, what are the steps?
>
> Thanks
> Shawn
>
>

Re: how to dismiss a ignite server node.

Posted by "slava.koptilin" <sl...@gmail.com>.
Hi Shawn,

Perhaps, it will be a good idea to propose this feature on dev-list to see
what dev community thinks.

Best regards,
Slava.



--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/

Re: how to dismiss a ignite server node.

Posted by David Harvey <dh...@jobcase.com>.
ElasticSearch has this feature (where you exclude a node) and we use it all
the time in production.

For example, if AWS has planned maintenance on instance with local SSDs, we
want to add a new node, and remove the old node, without a temporary
decrease in the number  of backups.   If you are running with one backup,
your choices are to add another backup for all partitions, or stop a node
and run with no backups for some period of time.   Neither is attractive.
 I want to add a new node, and to remove all data from the old node,
without loosing protection.

-DH

Disclaimer

The information contained in this communication from the sender is confidential. It is intended solely for use by the recipient and others authorized to receive it. If you are not the recipient, you are hereby notified that any disclosure, copying, distribution or taking action in relation of the contents of this information is strictly prohibited and may be unlawful.

This email has been scanned for viruses and malware, and may have been automatically archived by Mimecast Ltd, an innovator in Software as a Service (SaaS) for business. Providing a safer and more useful place for your human generated data. Specializing in; Security, archiving and compliance. To find out more visit the Mimecast website.

Re: how to dismiss a ignite server node.

Posted by vkulichenko <va...@gmail.com>.
Shawn,

I doubt this feature makes much sense as it doesn't really add value. If you
need to avoid data loss, using backups (and sometimes persistence) is a
must, and with backups you can easily achieve functionality you're
describing.

-Val



--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/