Make AllocatedPersistentTask members volatile (#2297)

These members are default initialized on contruction and then set by the
init() method.  It's possible that another thread accessing the object
after init() is called could still see the null/0 values, depending on how
the compiler optimizes the code.
This commit is contained in:
David Roberts 2017-08-17 14:54:31 +01:00 committed by Martijn van Groningen
parent b0de3c38d6
commit 7313ad5b29
No known key found for this signature in database
GPG Key ID: AB236F4FCF2AF12A
1 changed files with 6 additions and 6 deletions

View File

@ -36,16 +36,16 @@ import java.util.concurrent.atomic.AtomicReference;
* Represents a executor node operation that corresponds to a persistent task * Represents a executor node operation that corresponds to a persistent task
*/ */
public class AllocatedPersistentTask extends CancellableTask { public class AllocatedPersistentTask extends CancellableTask {
private String persistentTaskId; private volatile String persistentTaskId;
private long allocationId; private volatile long allocationId;
private final AtomicReference<State> state; private final AtomicReference<State> state;
@Nullable @Nullable
private Exception failure; private volatile Exception failure;
private PersistentTasksService persistentTasksService; private volatile PersistentTasksService persistentTasksService;
private Logger logger; private volatile Logger logger;
private TaskManager taskManager; private volatile TaskManager taskManager;
public AllocatedPersistentTask(long id, String type, String action, String description, TaskId parentTask) { public AllocatedPersistentTask(long id, String type, String action, String description, TaskId parentTask) {