Hi Jonathan,
If I have a customer that wants to start with a single backend and
then add an additional one later, can they do that without restarting
the controller?
Yes you can.
I know you can clone a backend, but that doesn’t appear to alter the
config. Plus, when I try to enable through the console I get “Trying
to access a non-existing backend” error, even though I can do a “show
backend” on it. Will we have to bring the application down to add and
enable new backends?
You can add the new backend through the JMX API or using the clone
backend command of the console. Note that the new config will only be
present in the memory of the controller, you will have to do a save
config if you want to persist it on disk.
Another option is also to pre-add multiple backends in the config file
(even if they don't exist yet) and activate them on demand.
I’m using the auto-enable feature with the controller.
Auto-enable will not work with a newly added backend since it will have
no state. You will have to go through the standard procedure to restore
a dump on this backend and enable it to resynchonize it. Make sure that
you persist the new config on disk if you want the controller to use
this backend on the next restart.
Hope this helps,
Emmanuel
--
Emmanuel Cecchet
FTO @ Frog Thinker
Open Source Development & Consulting
--
Web: http://www.frogthinker.org
email: [EMAIL PROTECTED]
Skype: emmanuel_cecchet
_______________________________________________
Sequoia mailing list
[email protected]
https://forge.continuent.org/mailman/listinfo/sequoia
