ignite-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From afedotov <alexander.fedot...@gmail.com>
Subject Re: Centralized configuration management
Date Mon, 14 Aug 2017 12:42:05 GMT

There is no option to update the configuration of an existing cache. As
well, you cannot create two caches with the same name but different
So, as you've correctly suggested, to achieve this, you need first to
destroy a cache and then start a new one with the updated configuration.
When you destroy or create a cache from a client node, there generally no
need to have/propagate the configuration manually to remote nodes.
On join/restart, a node will find out the caches configured in the cluster
and all the required routines will take place.

Kind regards,

On Mon, Aug 14, 2017 at 2:53 PM, franck102 [via Apache Ignite Users] <
ml+s70518n16161h25@n6.nabble.com> wrote:

> I need to be a bit more specific I guess.
> I need the ability to create new caches, or to update the configuration of
> existing caches.
> When updating the configuration of a cache other caches should not be
> affected - so a node restart is not a great option.
> Would this plan work:
> - The controller contains a client node; and also serves XML configuration
> for all cluster nodes through a REST endpoint
> - When an existing cache configuration is updated, the controller
>   1. updates the persistent configuration that it returns through the REST
> endpoint
>   2. destroys the cache
>   3. Recreates it use GetOrCreateCache
> I assume that 2. and 3. above will propagate the changes to the entire
> cluster? And 1. should take care of any late joiners or future restarts?
> Franck
> ------------------------------
> If you reply to this email, your message will be added to the discussion
> below:
> http://apache-ignite-users.70518.x6.nabble.com/Centralized-configuration-
> management-tp16159p16161.html
> To start a new topic under Apache Ignite Users, email
> ml+s70518n1h65@n6.nabble.com
> To unsubscribe from Apache Ignite Users, click here
> <http://apache-ignite-users.70518.x6.nabble.com/template/NamlServlet.jtp?macro=unsubscribe_by_code&node=1&code=YWxleGFuZGVyLmZlZG90b2ZmQGdtYWlsLmNvbXwxfC0xMzYxNTU0NTg=>
> .
> <http://apache-ignite-users.70518.x6.nabble.com/template/NamlServlet.jtp?macro=macro_viewer&id=instant_html%21nabble%3Aemail.naml&base=nabble.naml.namespaces.BasicNamespace-nabble.view.web.template.NabbleNamespace-nabble.view.web.template.NodeNamespace&breadcrumbs=notify_subscribers%21nabble%3Aemail.naml-instant_emails%21nabble%3Aemail.naml-send_instant_email%21nabble%3Aemail.naml>

View this message in context: http://apache-ignite-users.70518.x6.nabble.com/Centralized-configuration-management-tp16159p16163.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.
View raw message