From 9118db63d1ab493a2e44a3b4973fde810a835c49 Mon Sep 17 00:00:00 2001
From: Google APIs <noreply@google.com>
Date: Mon, 13 Jan 2020 15:26:31 -0800
Subject: [PATCH] firestore: don't retry reads that fail with Aborted

For transaction reads that fail with ABORTED, we need to rollback and start a new transaction. Our current configuration makes it so that GAPIC retries ABORTED reads multiple times without making any progress. Instead, we should retry at the transaction level.

PiperOrigin-RevId: 289532382
---
 google/firestore/v1/firestore_grpc_service_config.json | 3 ---
 1 file changed, 3 deletions(-)

diff --git a/google/firestore/v1/firestore_grpc_service_config.json b/google/firestore/v1/firestore_grpc_service_config.json
index d12fb697..0c6f86d9 100755
--- a/google/firestore/v1/firestore_grpc_service_config.json
+++ b/google/firestore/v1/firestore_grpc_service_config.json
@@ -35,7 +35,6 @@
         "maxBackoff": "60s",
         "backoffMultiplier": 1.3,
         "retryableStatusCodes": [
-          "ABORTED",
           "UNAVAILABLE",
           "INTERNAL",
           "DEADLINE_EXCEEDED"
@@ -56,7 +55,6 @@
         "maxBackoff": "60s",
         "backoffMultiplier": 1.3,
         "retryableStatusCodes": [
-          "ABORTED",
           "UNAVAILABLE",
           "INTERNAL",
           "DEADLINE_EXCEEDED"
@@ -106,7 +104,6 @@
         "maxBackoff": "60s",
         "backoffMultiplier": 1.3,
         "retryableStatusCodes": [
-          "ABORTED",
           "UNAVAILABLE",
           "INTERNAL",
           "DEADLINE_EXCEEDED"