Currently, there is no way to configure what types of errors the client should retry on, so we always fall back to the default behavior of RetryConnectionError. Exposing this configuration as part of TChannelClientOption
coverage: 68.859% (-0.4%) from 69.252% when pulling a8e3a0c844e6aa618c3c6df6a5ab71cf35a8fdb8 on mahipjain:retryon into 8c037deafdb6d78e5569d521be03b83cd6620116 on uber:master.
Currently, there is no way to configure what types of errors the client should retry on, so we always fall back to the default behavior of
RetryConnectionError
. Exposing this configuration as part ofTChannelClientOption