dang-stripe opened a new issue, #10900:
URL: https://github.com/apache/pinot/issues/10900

   we've recently dealt with transient errors related to kafka dns resolution. 
this causes realtime segment transitions from OFFLINE -> CONSUMING to go 
immediately into ERROR state. we manually reset the segment to resolve the 
issue. it'd be ideal if we had retries implemented so the segment transition 
eventually succeeds.
   
   ```
   [2023-06-01 15:04:09.010403] WARN [ClientUtils] 
[HelixTaskExecutor-message_handle_thread_8:25] Couldn't resolve server 
kafka-broker:9093 from bootstrap.servers as DNS resolution failed
   [2023-06-01 15:04:09.010792] 
org.apache.pinot.shaded.org.apache.kafka.common.KafkaException: Failed to 
construct kafka consumer
   [2023-06-01 15:04:09.011226] Caused by: 
org.apache.pinot.shaded.org.apache.kafka.common.config.ConfigException: No 
resolvable bootstrap urls given in bootstrap.servers
   ```
   
   
https://github.com/apache/pinot/blob/207036950ad5fc13725ee464a2d0a09f26776638/pinot-plugins/pinot-stream-ingestion/pinot-kafka-2.0/src/main/java/org/apache/pinot/plugin/stream/kafka20/KafkaPartitionLevelConnectionHandler.java#L64
   
   cc @Jackie-Jiang @navina @jadami10


-- 
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.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to