Skip to content
Browse files
fix: Make EOS Matching more robust (#1128)
fix: Make EOS Matching more robust

Clients are seeing a different variant now: Received unexpected EOS on empty DATA frame from server

Thank you for opening a Pull Request! Before submitting your PR, there are a few things you can do to make sure it goes smoothly:
- [x] Make sure to open an issue as a [bug/issue]( before writing your code!  That way we can discuss the change, evaluate designs, and agree on the general idea
- [x] Ensure the tests and linter pass
- [x] Code coverage does not decrease (if any source code was changed)
- [x] Appropriate docs were updated (if necessary)

Fixes #<issue_number_goes_here> ☕️
  • Loading branch information
emkornfield committed Jun 11, 2021
1 parent aea80e9 commit 3b5cdbe769fcebeebc571922c84c129066e76aaf
Showing with 1 addition and 1 deletion.
  1. +1 −1 google-cloud-bigquerystorage/src/main/java/com/google/cloud/bigquery/storage/util/
@@ -31,7 +31,7 @@ public static boolean isRetryableInternalStatus(Status status) {
String description = status.getDescription();
return status.getCode() == Status.Code.INTERNAL
&& description != null
&& (description.contains("Received unexpected EOS on DATA frame from server")
&& (description.contains("Received unexpected EOS ")
|| description.contains(" Rst ")
|| description.contains("RST_STREAM")
|| description.contains("Connection closed with unknown cause")

0 comments on commit 3b5cdbe

Please sign in to comment.