Let me explain usecase in details:
- Start ES cluster with several nodes
- Start loading ES using client App
- Drop (kill) one of ES nodes.
- Continue loading
- Start dropped ES node an let it become a part of cluster -> during this process I experience mentioned exception.
That basicaly means for me, that ES node is available to handle requests from client perspective, but it is not ready.