This should not be a problem. But it is true that backends will be
disabled the same way when doing only a shutdown virtualdatabase.
I just had a quick look to your logs, and it seems that something
strange happens...
2007-01-18 17:01:28,076 INFO controller.virtualdatabase.botdb First
controller in group botdb
This is what I found in first controller logs, after restarting. It
should detect the other controller, and log :
"Group now contains 2 controllers".
Otherwise, recovery logs won't resync, as controller 1 will think that
it is alone.
Is your second controller still up and running when restarting your
first controller?
Regards,
Stephane
Ingo Kampe a écrit :
Guillaume Smet wrote:
On 1/19/07, Ingo Kampe <[EMAIL PROTECTED]> wrote:
disable @VDB_BACKEND1@
Why do you disable the backend? It doesn't seem a good idea to me.
This seems to be the most controlled way to shutdown the whole controller.
foreach DBNAME
admin DBNAME
disable backend *
quit
shutdown virtualdatabase @DB_NAME@ 2
hcaerof
shutdown
I have seen that "shutdown virtualdatabase" also implicit disables all backends
and creates an checkpoint. But I'm searching for a BUG and wanted to be sure.
If this causes any troubles I change it in a minute.
?
Regards,
)ngo
------------------------------------------------------------------------
_______________________________________________
Sequoia mailing list
[email protected]
https://forge.continuent.org/mailman/listinfo/sequoia
_______________________________________________
Sequoia mailing list
[email protected]
https://forge.continuent.org/mailman/listinfo/sequoia
