LMAX Disruptor事件中的类字段是否需要易变？(Do class fields within an LMAX Disruptor event need to be volatile?)

 LMAX Disruptor“入门”的示例代码...... 
 
public class LongEvent
{
    private long value;

    public void set(long value)
    {
        this.value = value;
    }
}
 
 参考： https ： //github.com/LMAX-Exchange/disruptor/wiki/Getting-Started 
 
 为什么不将private long value声明为volatile ？ 
 
 我问，因为隐含于Disruptor模式，数据在线程（生产者 - >消费者）之间共享。 
 
 我的猜测：生产者和消费者线程之间已经存在（至少）一个内存栅栏。 

Sample code from the LMAX Disruptor "Getting Started"...
 
public class LongEvent
{
    private long value;

    public void set(long value)
    {
        this.value = value;
    }
}
 
Ref: https://github.com/LMAX-Exchange/disruptor/wiki/Getting-Started
 
Why isn't private long value declared as volatile?
 
I ask because, implicit to the Disruptor pattern, data is shared between threads (producer -> consumer).
 
My guess: There is already (at least) one memory fence between the producer and consumer threads.

原文：https://stackoverflow.com/questions/34706920