You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@druid.apache.org by GitBox <gi...@apache.org> on 2020/03/25 11:44:43 UTC

[GitHub] [druid] rafitadiaz commented on issue #6043: Faulty channel in resource pool

rafitadiaz commented on issue #6043: Faulty channel in resource pool
URL: https://github.com/apache/druid/issues/6043#issuecomment-603794753
 
 
   A quick comment to see if this can be useful for someone having this problem. 
   
   We got the same issue today in our druid cluster. After some research we discover that one of the data nodes was announcing itself with a wrong ip.
   
   We use puppet to populate the conf file when the node is created. We think now that the instance was rebooted and the ip changed but the conf file was not updated.
   
   So the instance now had the `10.132.0.3` but was announcing itself using the old ip `10.132.0.51` and all the queries failed with this:
   
   ```java
   Caused by: org.jboss.netty.channel.ConnectTimeoutException: connection timed out: /10.132.0.51:8083
   ...
   2020-03-25T11:11:58,709 WARN [DruidSchema-Cache-0] org.apache.druid.sql.calcite.schema.DruidSchema - Metadata refresh failed, trying again soon.
   org.apache.druid.query.QueryInterruptedException: org.jboss.netty.channel.ChannelException: Faulty channel in resource pool
   ```
   
   

----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
users@infra.apache.org


With regards,
Apache Git Services

---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@druid.apache.org
For additional commands, e-mail: commits-help@druid.apache.org