[GitHub] [kafka] yashmayya commented on pull request #13530: KAFKA-14858: Handle exceptions thrown from Connector::taskConfigs in Connect's standalone mode

["yashmayya (via GitHub)" <gi...@apache.org>]

yashmayya commented on PR #13530:
URL: https://github.com/apache/kafka/pull/13530#issuecomment-1576134917

   > mark connectors FAILED in the REST API if we've encountered an error while interacting with them, and will not (automatically) retry that interaction
   
   I'm wondering whether introducing further differences between the standalone and distributed modes makes sense? IMO, the ideal behavior here (when `Connector::taskConfigs` throws) would be for no automatic retries in both standalone and distributed modes and the connector instance transitioning to a failed state (which can then be restarted manually externally). However, based on the discussion in [KAFKA-14746](https://issues.apache.org/jira/browse/KAFKA-14746), it doesn't seem like we can simply go ahead and change the infinite retry behavior in distributed mode. 


-- 
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: jira-unsubscribe@kafka.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org