Gérard BUNEL [17/10/07 12:01]:
Hello,
Héllo Gérard,
We have 2 controllers with each 2 backends. VDB is in autoload config
We stop one controller, then restart it. Using the console we can see
that the VDB is not mounted and the log is as here-under.
As the controller as just been shutdonw then restarted, it was
effectively the last man down. So why is sequoia complaining about not
beeing the last man down.
If I understand you correctly, you keep the other controller up, thus doing
down-up on one controller does not make it the last man down: there remains one
man up ! May be the term "last man down" is miss-leading. It is meant to
identify the last vdb part that went down in a full (all parts) vdb shutdown.
The logs states that there's an error while trying to
join the group. So maybe an appia problem ?
First, a side note: the error shows at group-join time, but this is really a by
product: actually, it is vdb.xml load time: when we check for last-man-down
condition, IF we are the first vdb part in the group.
Now for your case: according to your logs, the vdb part you are attempting to
load is actually the first member in the group:
2007-10-17 11:56:06,201 INFO controller.virtualdatabase.MATISSEDB First
controller in group MATISSEDB
So either the other controller is down - and we are not in the case you describe
- or the controller you are restarting can not see the other one - and you have
a connectivity issue.
Hope this helps.
A+O.
_______________________________________________
Sequoia mailing list
[email protected]
https://forge.continuent.org/mailman/listinfo/sequoia
