hbase-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Paul Cowan <co...@aconex.com>
Subject Re: Re: volatile considered harmful
Date Fri, 16 Apr 2010 00:05:13 GMT
On -9/01/37 05:59, Ryan Rawson wrote:
> So the previous use of volatile for a boolean seems like a textbook
> case, but the situation i discovered was pretty clear cut. I have no
> other explanation than a highly delayed volatile read (which are
> allowed).

I don't see that they are allowed, actually.

Section 17.4.5 of the JLS says that:

> * An unlock on a monitor happens-before every subsequent lock on that monitor.
> * A write to a volatile field (§ happens-before every subsequent read of that

IOW, the situations (unlock-then-lock) and (volatile-write then 
volatile-read) have the same visibility guarantees.

Section says:

> A field may be declared volatile, in which case the Java memory model (§17)  ensures
that all threads see a consistent value for the variable.

In your case, the thread calling done() is not seeing the same value as 
the thread calling run(), which is not consistent.

And for good measure Java Concurrency in Practice makes it much more 
explicit (emphasis mine):

> Volatile variables are not cached in registers or in caches where they are hidden from
other processors, so *a read of a volatile variable always returns the most recent write by
any thread*.

And finally, on changing to an AtomicBoolean fixing the problem, JCIP says:

> Atomic variables offer the same memory semantics as volatile variables

So this doesn't really make sense either.

All that's a long way of saying that the only ways I can see your 
situation happening are:

* pre-Java-1.5 (and hence pre-JSR-133) JVM
* JVM with a bug
* ordering is not as you expect, i.e. the actual chronological order is not:

     THREAD 1                 THREAD 2
     spawn new thread

but rather:

     THREAD 1                 THREAD 2
     spawn new thread

in which case the set of run to false at the start of run() overwrites 
the set of it to true at the start of done(), and you're in for infinite 
loop fun.



View raw message