You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As mentioned in #3363 we don't decrement the CountDownLatch and never return a response if there's an uncaught exception in some of the TransportMasterNodeOperationActions that modify the cluster state. Some actions do catch Throwable and don't suffer from this issue, while some others don't.
We need to go over those and fix this issue so that we always decrement the CountDownLatch and give back the error that was thrown instead of hanging waiting for the thread to finish its execution.
The text was updated successfully, but these errors were encountered:
As mentioned in #3363 we don't decrement the CountDownLatch and never return a response if there's an uncaught exception in some of the TransportMasterNodeOperationActions that modify the cluster state. Some actions do catch Throwable and don't suffer from this issue, while some others don't.
We need to go over those and fix this issue so that we always decrement the CountDownLatch and give back the error that was thrown instead of hanging waiting for the thread to finish its execution.
The text was updated successfully, but these errors were encountered: