Re: RAC setting for max consistency?

On Sep 11, 2:23 pm, Robert Klemme <shortcut..._at_googlemail.com> wrote:
> On 11.09.2007 20:08, joeNOS..._at_BEA.com wrote:
>
>
>
> > On Sep 11, 8:56 am, "joeNOS..._at_BEA.com" <joe.weinst..._at_gmail.com>
> > wrote:
> >> Hi all,
> >> IIRC, there is a RAC configuration setting that determines the level
> >> of consistency in the view
> >> of the data between multiple RAC nodes. The tradeoff is between
> >> maximum consistency and
> >> coordination versus an acceptance of some latency of view allowing
> >> faster performance. Can
> >> you tell me this configuration parameter and the setting for maximum
> >> consistency?
> >> thanks much,
> >> Joe Weinstein
>
> > I found it: MAX_COMMIT_PROPAGATION_DELAY
>
> > Under some circumstances with rapid writes and reads, the data
> > seen at node B may not include committed changes just made by
> > node A. This setting is for 10.1 and earlier.
> > Joe Weinstein at BEA Systems
>
> For distributed TX there is also tight and loose coupling which also
> influences visibility of changes among TX branches:
>
> http://download.oracle.com/docs/cd/B19306_01/appdev.102/b14251/adfns_...
>
> Kind regards
>
> robert

Thanks! Interesting:

Tight and Loose Coupling

Application threads are tightly coupled if the RM considers them as a single entity for all isolation semantic purposes.

Do you know where it is documented how the RM decides if threads are a single entity for these purposes?
Would it simply be the TX ID associated with the threads? (different branches maybe) Received on Wed Sep 12 2007 - 11:56:32 CDT