You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@ignite.apache.org by franck102 <fr...@yahoo.com> on 2017/08/14 11:36:10 UTC
Centralized configuration management
Hi all,
I am trying to design a controller that will be responsible for managing the
cache configuration of all nodes in a cluster. Having read this in the docs:
"All caches defined in Ignite Spring XML configuration on any cluster member
will also be automatically created and deployed on all the cluster servers
(no need to specify the same configuration on each cluster member)."...
I am thinking of having that controller start a client node and join the
cluster. This raises a few questions though:
- If I update the configuration on the controller, can I manually trigger a
re-deployment to all nodes?
- on configuration changes I can re-create the client node and have it
re-join the cluster: will that trigger a re-deployment of the controller's
cache configuration? Or will that trigger an error because two different
cnofigurations exist for the same cache?
- If that is what it takes, is there any node-2-node or REST API I can use
to restart each node in the cluster?
Any other suggestion to design a configuration manager that can control the
cache configuration for an entire cluster is welcome... thanks!
Franck
--
View this message in context: http://apache-ignite-users.70518.x6.nabble.com/Centralized-configuration-management-tp16159.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.
Re: Centralized configuration management
Posted by franck102 <fr...@yahoo.com>.
Thanks Alex!
--
View this message in context: http://apache-ignite-users.70518.x6.nabble.com/Centralized-configuration-management-tp16159p16168.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.
Re: Centralized configuration management
Posted by afedotov <al...@gmail.com>.
Hi,
Yes, GetOrCreateCache should do the thing in this case.
Kind regards,
Alex.
On Mon, Aug 14, 2017 at 3:53 PM, franck102 [via Apache Ignite Users] <
ml+s70518n16165h49@n6.nabble.com> wrote:
> Hi Alex,
>
> Regarding this statement:
> "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."
>
> I assume that after destroying the cache, simply calling GetOrCreateCache
> locally on the client node will be enough for remote server nodes to pick
> up the new cache and its configuration - without having to restart them?
>
> ------------------------------
> 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-tp16159p16165.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=>
> .
> NAML
> <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-tp16159p16167.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.
Re: Centralized configuration management
Posted by franck102 <fr...@yahoo.com>.
Hi Alex,
Regarding this statement:
"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."
I assume that after destroying the cache, simply calling GetOrCreateCache
locally on the client node will be enough for remote server nodes to pick up
the new cache and its configuration - without having to restart them?
--
View this message in context: http://apache-ignite-users.70518.x6.nabble.com/Centralized-configuration-management-tp16159p16165.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.
Re: Centralized configuration management
Posted by afedotov <al...@gmail.com>.
Hi,
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
configurations.
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,
Alex.
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=>
> .
> NAML
> <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.
Re: Centralized configuration management
Posted by franck102 <fr...@yahoo.com>.
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
--
View this message in context: http://apache-ignite-users.70518.x6.nabble.com/Centralized-configuration-management-tp16159p16161.html
Sent from the Apache Ignite Users mailing list archive at Nabble.com.