[ https://forge.continuent.org/jira/browse/SEQUOIA-997?page=comments#action_14118 ]
Emmanuel Cecchet commented on SEQUOIA-997: ------------------------------------------ Do your transactions complete with an explicit commit in the recovery log? Could you give an example of a complete transaction in your recovery log that is not replayed? Did you check the query status to see if it was successful or failed? Failed queries are usually not replayed if they do not have side effect. The same applies to rollback transactions. > Recovery replay only applies transactions where auto_conn_tran is A > (autocommit) does not replay where auto_conn_tran T > ----------------------------------------------------------------------------------------------------------------------- > > Key: SEQUOIA-997 > URL: https://forge.continuent.org/jira/browse/SEQUOIA-997 > Project: Sequoia > Type: Bug > Components: Recovery Log > Versions: Sequoia 2.10.9 > Environment: Linux with postgresql 8.2.5 > Reporter: Dominic Vieira > > > Extension to Jira SEQUIOA-996. > When a backend is disabled I inserted transaction through sql client, I > noticed auto_conn_tran was set to A. Through my application the same sql > inserted in the the recovery log with auto_conn_tran set to T. When the > backend was enabled only the auto_conn_tran transactions in the recovery log > were applied to the enabled backend. > If I manually change the auto_conn_tran field to A and transaction_id to 0 > for the transaction that was created through the app, the transaction is > replayed to the enabled backend on recovery. > Please help, this is becoming an urgent matter for me... -- 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
