You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I saw a dial failing recently because the OS was very overloaded and
then slow -- dial timeouts are fine. Every other dial failure indicates
a bigger problem.
if!kerr.IsRetriable(load.err) &&!isRetryableBrokerErr(load.err) &&!isDialErr(load.err) &&!isContextErr(load.err) { // non-retryable response error; signal such in a response
1783
+
if!kerr.IsRetriable(load.err) &&!isRetryableBrokerErr(load.err) &&!isDialNonTimeoutErr(load.err) &&!isContextErr(load.err) { // non-retryable response error; signal such in a response
1784
1784
s.c.addFakeReadyForDraining(load.topic, load.partition, load.err, fmt.Sprintf("notification of non-retryable error from %s request", loaded.loadType))
s.cl.cfg.logger.Log(LogLevelWarn, "unable to AddPartitionsToTxn due to retryable broker err, bumping client's buffered record load errors by 1 and retrying", "err", err)
332
332
s.cl.triggerUpdateMetadata(false, "attempting to refresh broker list due to failed AddPartitionsToTxn requests")
0 commit comments