org.elasticsearch.transport.ReceiveTimeoutTransportException

[][inet[/192.168.1.2:9200]][cluster:monitor/nodes/info] request_id [2] timed out after [ 5001ms]

Samebug tips0

There are no available Samebug tips for this exception. If you know how to solve this issue, help other users by writing a short tip.

Don't give up yet. Paste your full stack trace to get a solution.

Solutions on the web247

  • via Google Groups by Unknown author, 6 months ago
    [][inet[/192.168.1.2:9200]][cluster:monitor/nodes/info] request_id [2] timed out after [ 5001ms]
  • via GitHub by mufukuri
    , 1 year ago
    [][inet[localhost/127.0.0.1:9200]][cluster:monitor/nodes/info] request_id [0] timed out after [5001ms]
  • [][inet[/172.17.0.2:9200]][cluster/nodes/info] request_id [2] timed out after [5001ms]
  • Stack trace

    • org.elasticsearch.transport.ReceiveTimeoutTransportException: [][inet[/192.168.1.2:9200]][cluster:monitor
    • odes/info] request_id [2] timed out after [ 5001ms] at org.elasticsearch.transport.TransportService$TimeoutHandler.run(TransportService.java:366) at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615) at java.lang.Thread.run(Thread.java:745)

    Write tip

    You have a different solution? A short tip here would help you and many other users who saw this issue last week.

    Users with the same issue

    Once, 11 months ago
    3 times, 1 day ago
    31 times, 1 week ago
    25 times, 1 week ago
    3 times, 1 month ago
    8 more bugmates