Hi, Environment: debian etch, java 1.5, 1 backend postgresql 8.1.4, EmbeddedRecoveryLog, sequoia 3.0 beta02, appia 3.2.4, hedera 1.5.6-cvs03.01.2007
state direct after initialize and enable. botdb(admin) > show checkpoints +----+----------------------------+ | id | name | +----+----------------------------+ | 0 | Initial_empty_recovery_log | +----+----------------------------+ localhost:21090 > shutdown virtualdatabase botdb 2 Shutting down database botdb from controller Database botdb was successfully shutdown now i try to reenable the vdb and the backend: localhost:21090 > load virtualdatabase configuration /etc/tbone/backbone/certservice/sequoia/virtual_db.xml XML file /etc/tbone/backbone/certservice/sequoia/virtual_db.xml successfully sent to Sequoia controller. localhost:21090 > admin botdb Virtual database Administrator Login > admin Virtual database Administrator Password > Ready to administrate virtual database botdb botdb(admin) > expert on Expert mode on botdb(admin) > show checkpoints +----+--------------------------------------------------------------+ | id | name | +----+--------------------------------------------------------------+ | 0 | Initial_empty_recovery_log | | 12 | disable all backends-node00304884C6C0-20070104140434602+0100 | | 12 | shutdownnode00304884C6C0 | +----+--------------------------------------------------------------+ botdb(admin) > enable botdb1_00304884C6C0 Enabling backend botdb1_00304884C6C0 from its last known checkpoint !Cannot enable backend botdb1_00304884C6C0 from a known state. Resynchronize this backend by restoring a dump.! Why? In my understanding of sequoia it should use the automatically created checkpoint to enable the backend and replay the recovery log. I get the same error with: >disable botdb1_00304884C6C0 >shutdown virtualdatabase botdb 2 >load virtualdatabase configuration >enable botdb1_00304884C6C0 2nd Problem: after >botdb(admin) > restore backend botdb1_00304884C6C0 init_dump >enable * I see in the full_cluster.log thousends of lines with 2007-01-04 14:33:01,319 DEBUG sequoia.controller.recoverylog recovering read request 1. Why recovering of read requests? 2. It seems to be an endless loop, waiting for some minutes yet and there were only 20 read requests before disabling the backends. Thanx for help, )ngo
smime.p7s
Description: S/MIME cryptographic signature
_______________________________________________ Sequoia mailing list [email protected] https://forge.continuent.org/mailman/listinfo/sequoia
