[ https://forge.continuent.org/jira/browse/SEQUOIA-928?page=all ]
     
Emmanuel Cecchet resolved SEQUOIA-928:
--------------------------------------

    Resolution: Not an issue

Actually you should run the single controller configuration with a Distribution 
element in the first place. This way you can add a second controller seamlessly.
Removing the Distribution element is just an optimization that will use a 
different code path (incompatible with distributed controller code) to avoid 
distributed failover code. It is not possible to dynamically promote a 
non-distributed controller to distributed, this is a completely different code 
path and behavior.
You should always use the Distribution element even in a single controller 
scenario unless you really want to stick with a single controller as a simple 
load balancer.

Let me know if the documentation is unclear on that topic.

> Runtime Switch for distribution config
> --------------------------------------
>
>          Key: SEQUOIA-928
>          URL: https://forge.continuent.org/jira/browse/SEQUOIA-928
>      Project: Sequoia
>         Type: New Feature
>   Components: Core
>     Reporter: )ngo Kampe
>     Assignee: Emmanuel Cecchet

>
>
> I like to request a feature for changing the <Distribution> config during 
> runtime. I suggest a JMX method with
> access to config and automatic config reloading.
> The UseCase:
> A standalone sequoia controller is running in production environment. This 
> feature gives the possibility to extend this controller with a second 
> controller without downtime. The new controller (and probably new machine) 
> will be connected and than on the first controller distribution is to 
> activate.
> Today:
> We have to stop the production controller and add the
>         <Distribution hederaPropertiesFile="/hedera_appia.properties" 
> clientFailoverTimeout="60000">
>             <MessageTimeouts/>
>         </Distribution>
> element to our vdb.xml and start the controller again.
> For heartbeat experts:
> This could be compared to the cibadmin heartbeat tool, which allows to write, 
> update, delete cluster configuration.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   https://forge.continuent.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira


_______________________________________________
Sequoia mailing list
[email protected]
https://forge.continuent.org/mailman/listinfo/sequoia

Reply via email to