Hi Rami,

Which version of Sequoia are you using?
Are the 2 controllers running on different machines?
What group communication implementation are you using?
What is your recovery log configuration?

That should be easy to fix if this is not a configuration problem.
Keep us posted,
Emmanuel


We have the next scenario

2 Controllers with 1 DB each, both shared virtual DB using sequoia[RAIDb1].

when we start the first controller everything goes well, but when we start the second one we have the below log error:

14:35:26,774 ERROR sequoia.controller.recoverylog Logger thread was
unable to log Storing checkpoint Member(address=/192.168.0.6:33029,
uid=opensequoia) joined group
opensequoia-192.168.0.7:25323-20070105143526441+0100 with id 0 because
of java.sql.SQLException: Unable to store checkpoint
Member(address=/192.168.0.6:33029, uid=opensequoia) joined group
opensequoia-192.168.0.7:25323-20070105143526441+0100 in recovery log
database (Duplicate entry 'Member(address=/192.168.0.6:3302' for key 1)
java.sql.SQLException: Unable to store checkpoint
Member(address=/192.168.0.6:33029, uid=opensequoia) joined group
opensequoia-192.168.0.7:25323-20070105143526441+0100 in recovery log
database (Duplicate entry 'Member(address=/192.168.0.6:3302' for key 1)
        at
org.continuent.sequoia.controller.recoverylog.LoggerThread.storeCheckpointWithLogId(LoggerThread.java:398)
        at
org.continuent.sequoia.controller.recoverylog.events.StoreCheckpointWithLogIdEvent.execute(StoreCheckpointWithLogIdEvent.java:69)
        at
org.continuent.sequoia.controller.recoverylog.LoggerThread.run(LoggerThread.java:732)



are there any suggestion?

thanks on advanced,
Regards,


--
Emmanuel Cecchet
Chief Scientific Officer, Continuent

Blog: http://emanux.blogspot.com/
Open source: http://www.continuent.org
Corporate: http://www.continuent.com
Skype: emmanuel_cecchet
Cell: +33 687 342 685


_______________________________________________
Sequoia mailing list
[email protected]
https://forge.continuent.org/mailman/listinfo/sequoia

Reply via email to