From 308d5e0ae36c5fed6ccd00fe2056f2cd056626eb Mon Sep 17 00:00:00 2001
From: Yannick Welsch <yannick@welsch.lu>
Date: Sat, 29 Apr 2017 10:49:12 +0200
Subject: [PATCH] Don't call ClusterService.state() in a ClusterStateUpdateTask

The current state is readily available as a parameter

Original commit: elastic/x-pack-elasticsearch@a09929aa82db653881a7d1e68e993b365c46451b
---
 .../xpack/persistent/PersistentTasksClusterService.java         | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/plugin/src/main/java/org/elasticsearch/xpack/persistent/PersistentTasksClusterService.java b/plugin/src/main/java/org/elasticsearch/xpack/persistent/PersistentTasksClusterService.java
index 2ab4dc857e3..a9b99ed21d5 100644
--- a/plugin/src/main/java/org/elasticsearch/xpack/persistent/PersistentTasksClusterService.java
+++ b/plugin/src/main/java/org/elasticsearch/xpack/persistent/PersistentTasksClusterService.java
@@ -57,7 +57,7 @@ public class PersistentTasksClusterService extends AbstractComponent implements
                 if (builder.hasTask(taskId)) {
                     throw new ResourceAlreadyExistsException("task with id {" + taskId + "} already exist");
                 }
-                validate(action, clusterService.state(), params);
+                validate(action, currentState, params);
                 final Assignment assignment;
                 assignment = getAssignement(action, currentState, params);
                 return update(currentState, builder.addTask(taskId, action, params, assignment));