y1chi commented on PR #17537: URL: https://github.com/apache/beam/pull/17537#issuecomment-1118034282
> Thanks! I think this workaround is preferable to retrying the entire test. A couple of questions/concerns: > > * Are we sure it's safe to retry these UNAVAILABLE responses? The [gRPC [docs](https://grpc.github.io/grpc/core/md_doc_statuscodes.html) note "it is not always safe to retry non-idempotent operations." > * I think this is a better workaround, but it's still a little concerning that we don't understand the root cause - any thoughts on how we could dig deeper? I believe UNAVAILABLE in this cases means that the underneath tcp connection was broken (not sure why and unclear how to debug that) before the request is handled so that means it should be retriable(had more than 250 runs and didn't see any side effect like getting wrong results after adding retry). I enabled the GRPC debug log but didn't find anything interesting also. -- 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]
