Hi Stuart,
We experienced the below after an attempted automated backup operation,
the pg_dump command did not actually begin till 3:30. Why is there a
timeout on 0 pending transactions?
Actually, begin handling is very complex in Sequoia depending on the
nature of the transaction. There is an optimization that starts
transactions lazily to prevent starting read-only transactions on
multiple nodes.
So a couple of questions about your configuration since each case has a
different code path:
- are you using multiple controllers?
- was the client starting the transaction connected to the controller
where the timeout occurred?
- was the query following the begin a SELECT or an update (INSERT,
UPDATE, DELETE...)?
- are you using persistent connections?
2008-05-20 01:51:23,631 WARN sequoia.controller.scheduler Timeout in
begin, still waiting for 0 pending transactions to complete
2008-05-20 01:51:23,631 WARN controller.virtualdatabase.seccard Begin
failed (Timeout in begin, still waiting for 0 pending transactions to
complete)
Would you have a complete log to see when the backup operation was
triggered and what were the subsequent errors if any?
Thanks for your feedback,
Emmanuel
--
Emmanuel Cecchet
FTO @ Frog Thinker
Open Source Development & Consulting
--
Web: http://www.frogthinker.org
email: [EMAIL PROTECTED]
Skype: emmanuel_cecchet
_______________________________________________
Sequoia mailing list
[email protected]
https://forge.continuent.org/mailman/listinfo/sequoia
