Re: [Firebird-devel] Max transaction duration

[David J. <dav...@di...>]

On 2002.12.12 15:51:27 -0500 Pavel Cisar wrote:
> David,
> 
> On 12 Dec 2002 at 9:35, David Jencks wrote:
> 
> > Umm, then they should share their wisdom on reliable distributed system
> > design with the  rest of the world, which AFAIK universally uses
> timeouts
> > to model node failure in distributed systems.  This can be explicit as
> in
> > the XA transaction model with transaction timeouts (a fairly old
> example)
> > and JINI leases (a much newer example) or implicit as in systems with
> > heartbeats.
> 
> I didn't think that transaction timeout itself is not useful or needed in
> 
> some cases, but there is no need to implement it at database engine level
> 
> as flat transaction behaviour. Your distributed transaction manager can 
> easily implement this without any change in database engine.


I don't see how.  Unless the resource manager can discard timed out work
automatically, someone has to do it manually.  If the tm crashes, it will
have no record of transactions that have been started but not prepared, and
will not be able to instruct the resource manager to forget them: there
could be other tms that are responsible for them and are still actively
using them.

Please explain how the abandoned work on the resource manager will get
cleaned up automatically in this case unless the rm can unilaterally
discard it based only on information it knows.

thanks
david jencks
>  
> Best regards
> Pavel Cisar
> http://www.ibphoenix.com
> For all your upto date Firebird and
> InterBase information
> 
> 
> 
> -------------------------------------------------------
> This sf.net email is sponsored by:
> With Great Power, Comes Great Responsibility 
> Learn to use your power at OSDN's High Performance Computing Channel
> http://hpc.devchannel.org/
> _______________________________________________
> Firebird-devel mailing list
> Fir...@li...
> https://lists.sourceforge.net/lists/listinfo/firebird-devel
> 
>