HybridBoy
Active member
I have this error, out of sudden I got this errors
and my host support says this is the issue below:
What's the solution to this fix this issue, so I can tell my host? seems this is over their knowledge
and my host support says this is the issue below:
[2024-06-06T06:35:31,880][WARN ][o.e.p.PersistentTasksClusterService] [ my server ] failed to reassign persistent tasks
org.elasticsearch.cluster.coordination.FailedToCommitClusterStateException: node closed
at org.elasticsearch.cluster.service.MasterService.forkQueueProcessor(MasterService.java:1292) ~[elasticsearch-8.14.0.jar:?]
at org.elasticsearch.cluster.service.MasterService$5.onCompletion(MasterService.java:1256) ~[elasticsearch-8.14.0.jar:?]
at org.elasticsearch.cluster.service.MasterService$5$1.onResponse(MasterService.java:1219) ~[elasticsearch-8.14.0.jar:?]
at org.elasticsearch.cluster.service.MasterService$5$1.onResponse(MasterService.java:1216) ~[elasticsearch-8.14.0.jar:?]
at org.elasticsearch.action.ActionListenerImplementations$RunBeforeActionListener.onResponse(ActionListenerImplementations.java:307) ~[elasticsearch-8.14.0.jar:?]
at org.elasticsearch.action.ActionListenerImplementations$RunAfterActionListener.onResponse(ActionListenerImplementations.java:269) ~[elasticsearch-8.14.0.jar:?]
at org.elasticsearch.action.ActionListenerImplementations$DelegatingResponseActionListener.onResponse(ActionListenerImplementations.java:182) ~[elasticsearch-8.14.0.jar:?]
at org.elasticsearch.cluster.service.MasterService$2.onResponse(MasterService.java:284) ~[elasticsearch-8.14.0.jar:?]
at org.elasticsearch.cluster.service.MasterService$2.onResponse(MasterService.java:281) ~[elasticsearch-8.14.0.jar:?]
at org.elasticsearch.cluster.service.MasterService$3.run(MasterService.java:451) ~[elasticsearch-8.14.0.jar:?]
=====================
From the above logs, it can be concluded that if a persistent task cannot be immediately reassigned and has caused periodic rechecks to be scheduled (on the master node at that time), then those rechecks continue to be rescheduled regardless of whether the node is still the master.
What's the solution to this fix this issue, so I can tell my host? seems this is over their knowledge