SingleDB configuration with a recovery log will generate spurious 'unable to
update request completion status' messages
-----------------------------------------------------------------------------------------------------------------------
Key: SEQUOIA-833
URL: https://forge.continuent.org/jira/browse/SEQUOIA-833
Project: Sequoia
Type: Bug
Components: Recovery Log, Core
Versions: Sequoia 3.0 beta1, Sequoia 2.10.2
Reporter: Emmanuel Cecchet
Assigned to: Emmanuel Cecchet
Priority: Minor
Fix For: Sequoia 2.10.3, Sequoia 3.0
When using a SingleDB configuration with a recovery log message, the
RequestManager will try to update the request completion status in the recovery
log whereas the SingleDB load balancer does not update the recovery log.
This will result in messages such as the one reported by Peter Courcoux :
> Recovery log was unable to update request completion status:
> UPDATE logtable SET
> exec_status=S,update_count=0,exec_time=1733,completion_log_id=0 WHERE log_id=0
--
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
