1:01 p.m.
Should write skews be allowed by default? This would be less correct,
but less likely for exceptions being thrown due to concurrent read-
then-write patterns.
What do you guys think?
- Manik
--
Manik Surtani
Lead, JBoss Cache
manik(a)jboss.org
2:15 p.m.
How about no default and force people to configure it / throw
ConfigurationException if they don't? Make people understand what they
are doing, since this will be new to most users. This could probably be
explained really clearly on one wiki page, so it's not a huge imposition
on people.
Manik Surtani wrote:
Should write skews be allowed by default? This would be less
correct,
but less likely for exceptions being thrown due to concurrent
read-then-write patterns.
What do you guys think?
- Manik
--
Manik Surtani
Lead, JBoss Cache
manik(a)jboss.org
_______________________________________________
jbosscache-dev mailing list
jbosscache-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jbosscache-dev
--
Brian Stansberry
Lead, AS Clustering
JBoss, a division of Red Hat
brian.stansberry(a)redhat.com
5:14 p.m.
IMO we should default it to off, since enabling it is a step closer to
SERIALIZABLE. Having it off still offers greater isolation than most
dbs, which are all read committed essentially.
Manik Surtani wrote:
Should write skews be allowed by default? This would be less
correct,
but less likely for exceptions being thrown due to concurrent
read-then-write patterns.
What do you guys think?
- Manik
--
Manik Surtani
Lead, JBoss Cache
manik(a)jboss.org
_______________________________________________
jbosscache-dev mailing list
jbosscache-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jbosscache-dev
8:15 p.m.
I'm guessing you mean allow write skews by default, rather than throw
an exception when they are detected?
On 15 Jul 2008, at 23:14, Jason T. Greene wrote:
IMO we should default it to off, since enabling it is a step closer
to SERIALIZABLE. Having it off still offers greater isolation than
most dbs, which are all read committed essentially.
Manik Surtani wrote:
> Should write skews be allowed by default? This would be less
> correct, but less likely for exceptions being thrown due to
> concurrent read-then-write patterns.
> What do you guys think?
> - Manik
> --
> Manik Surtani
> Lead, JBoss Cache
> manik(a)jboss.org
> _______________________________________________
> jbosscache-dev mailing list
> jbosscache-dev(a)lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/jbosscache-dev
--
Manik Surtani
Lead, JBoss Cache
manik(a)jboss.org
8:31 p.m.
Right, what I meant was:
# Prevents writes to a node that changed after it was read
write-skew-checking = false
Manik Surtani wrote:
I'm guessing you mean allow write skews by default, rather than
throw an
exception when they are detected?
On 15 Jul 2008, at 23:14, Jason T. Greene wrote:
> IMO we should default it to off, since enabling it is a step closer to
> SERIALIZABLE. Having it off still offers greater isolation than most
> dbs, which are all read committed essentially.
>
> Manik Surtani wrote:
>> Should write skews be allowed by default? This would be less
>> correct, but less likely for exceptions being thrown due to
>> concurrent read-then-write patterns.
>> What do you guys think?
>> - Manik
>> --
>> Manik Surtani
>> Lead, JBoss Cache
>> manik(a)jboss.org
>> _______________________________________________
>> jbosscache-dev mailing list
>> jbosscache-dev(a)lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/jbosscache-dev
>
--
Manik Surtani
Lead, JBoss Cache
manik(a)jboss.org
3:19 a.m.
Ah, there's the disconnect - I've called the cfg option:
# if true, allows any write skews detected to proceed without
throwing an exception
allowWriteSkew = true
But I think that can be confusing - writeSkewCheck is better.
On 16 Jul 2008, at 02:31, Jason T. Greene wrote:
Right, what I meant was:
# Prevents writes to a node that changed after it was read
write-skew-checking = false
Manik Surtani wrote:
> I'm guessing you mean allow write skews by default, rather than
> throw an exception when they are detected?
> On 15 Jul 2008, at 23:14, Jason T. Greene wrote:
>> IMO we should default it to off, since enabling it is a step
>> closer to SERIALIZABLE. Having it off still offers greater
>> isolation than most dbs, which are all read committed essentially.
>>
>> Manik Surtani wrote:
>>> Should write skews be allowed by default? This would be less
>>> correct, but less likely for exceptions being thrown due to
>>> concurrent read-then-write patterns.
>>> What do you guys think?
>>> - Manik
>>> --
>>> Manik Surtani
>>> Lead, JBoss Cache
>>> manik(a)jboss.org
>>> _______________________________________________
>>> jbosscache-dev mailing list
>>> jbosscache-dev(a)lists.jboss.org
>>> https://lists.jboss.org/mailman/listinfo/jbosscache-dev
>>
> --
> Manik Surtani
> Lead, JBoss Cache
> manik(a)jboss.org
--
Manik Surtani
Lead, JBoss Cache
manik(a)jboss.org
6471
days inactive
6472
days old
jbosscache-dev@lists.jboss.org
5 comments
3 participants
participants (3)
-
Brian Stansberry -
Jason T. Greene -
Manik Surtani