Yes, I typically see it on large cluster states when cluster state update tasks in front of a delete repo task take too long to finish (because of a large number of nodes, indices, types, aliases etc.). We have improved the situation in later versions of elasticsearch by switching to shipping cluster state diffs instead of a complete cluster state and implementing cluster state task batching in more places.