[
https://forge.continuent.org/jira/browse/SEQUOIA-1050?page=comments#action_14326
]
Stefan Lischke commented on SEQUOIA-1050:
-----------------------------------------
Thanks for filing this bug, i have observed this for a long time, but i thought
it was not critical, cause the checkpoint was not created.
You think it might cause something serious?
here is my exception i always get:
-----
checkpoint with name shutdown192.168.0.114:25322 already exists!
2007-09-18 15:54:19,134 WARN controller.virtualdatabase.messenger Error while
setting shutdown checkpoint
java.sql.SQLException: A checkpoint with name shutdown192.168.0.114:25322
already exists!
at
org.continuent.sequoia.controller.recoverylog.RecoveryLog.storeCheckpoint(RecoveryLog.java:2573)
> Duplicate shutdown checkpoint names with non-distributed virtual databases
> --------------------------------------------------------------------------
>
> Key: SEQUOIA-1050
> URL: https://forge.continuent.org/jira/browse/SEQUOIA-1050
> Project: Sequoia
> Type: Bug
> Components: Recovery Log, Core
> Environment: Any non-distributed virtual database with recovery log
> Reporter: Emmanuel Cecchet
> Assignee: Emmanuel Cecchet
> Priority: Critical
>
>
> The code in VirtualDatabase.setShutdownCheckpoint does not generate unique
> checkpoint names. Shutting down the controller for the second time on the
> same controller will generate a duplicate entry exception in the recovery log.
> The method should use buildCheckpointName("shutdown") instead like in the
> DistributedVirtualDatabase implementation.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://forge.continuent.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
_______________________________________________
Sequoia mailing list
[email protected]
https://forge.continuent.org/mailman/listinfo/sequoia
