"Manuel Fomitescu" <[EMAIL PROTECTED]> writes: > Hy, my name is Manuel and I am a Java software developer...I > installed Sequoia for my application but I'm a little bit > confused.Why when a backend is down sequoia don't make a checkpoint > for this backend and don't disable it automaticaly (if I stop the > postgres server on a backend machine sequoia controller disable the > backend but don't make a check point, if I remove the network cable > from the backend machine then sequoia controller don't realize that > this backend must be disable, it remains in enable state and a > checkpoint it is not added also). Only when I disable the backend > from the sequoia administration console the checkpoint is correctly > created and the backend it's putted in the correct state.Also when I > restore and dump to a backend some errors appear and the backend is > not enabled. I use a configuration with 1 controller, 2 backends and > postrgreSQL database server, and the configuration files are taken > from the examples directory in the installation.In other way it's > work fine but when something happens it a little bit difficult to > get the system in a correct state. Thank you for your understanding > and hope hearing soon news from you.Best regards, Manuel!
Hi Manuel, Checkpoints cannot be set automatically because their purpose is to mark in time a well known backend state. When a backend suddenly disappear, possibly in the middle of some running transactions, the controller has absolutely no idea what it has become. You'll find more details about this in the documentation or in the mailing list archive. When you unplug the network cable, a backend is not immediately disabled because if you replug the cable quickly enough, everything will run fine. This is the usual behaviour of most network applications. Cheers, Marc. _______________________________________________ Sequoia mailing list [email protected] https://forge.continuent.org/mailman/listinfo/sequoia
