Timeout for Transactions

[GoogleCodeExporter]

Rather a feature request than a issue:

I was thinking about the current implementation of timeouts during a 
transaction. Several timeouts are involved, but it doesn't seem that a 
"transaction-wide" timeout is implemented. E.g. if the transaction contains a 
timer:sleep(30000) the transaction will run >=30 secs.

I tried to include a timeout at least over the read phase (so still no global 
transaction-wide timeout). I'm not complete sure if it works correctly in 
case the current transaction manager node goes down. 
I didn't want to touch the commit phase as interrupting this phase could 
break atomic commit, I assume.

Maybe I have overseen an already existing, better place to introduce the 
timeout or a complete and correct realization is not trivial.

Could you have a look at the code and provide critic?

Original issue reported on code.google.com by Uwe.Daue...@gmail.com on 11 Mar 2010 at 4:12

Attachments:

• tmanager.erl_read_phase_timeout.patch

[GoogleCodeExporter]

With the transaction processing rewrite started in r647 we introduced
an overall transaction validation timeout tx_timeout.

You may access the new tx framework via cs_api_v2, which is compatible with the 
old 
cs_api from a clients point of view. 

Original comment by schin...@gmail.com on 25 Mar 2010 at 6:14

• Changed state: Done