Define the interface for controlling how the Bigtable client backsoff from failed RPC operations.
The C++ client for Bigtable needs to hide partial and temporary failures from the application. However, we need to give the users enough flexibility to control how many attempts are made to reissue operations, how often these attempts are executed, and how to signal that an error has occurred.
The application provides an instance of this class when the Table (or TableAdmin) object is created. This instance serves as a prototype to create new RPCBackoffPolicy objects of the same (dynamic) type and with the same initial state.
[[["Easy to understand","easyToUnderstand","thumb-up"],["Solved my problem","solvedMyProblem","thumb-up"],["Other","otherUp","thumb-up"]],[["Hard to understand","hardToUnderstand","thumb-down"],["Incorrect information or sample code","incorrectInformationOrSampleCode","thumb-down"],["Missing the information/samples I need","missingTheInformationSamplesINeed","thumb-down"],["Other","otherDown","thumb-down"]],["Last updated 2025-03-14 UTC."],[[["This document provides information on the `RPCBackoffPolicy` class within the Google Cloud Bigtable C++ client library, focusing on how it manages retries and backoff behavior for failed RPC operations."],["The `RPCBackoffPolicy` class allows users to define the strategy for retrying failed RPC calls, including the number of attempts and the time between each attempt."],["The `RPCBackoffPolicy` is initialized when a `Table` or `TableAdmin` object is created, and serves as a template for creating new objects with similar initial configurations."],["The most recent version of the `RPCBackoffPolicy` is 2.37.0-rc, with a range of prior version references, all the way back to version 2.11.0, listed for user reference."],["The `RPCBackoffPolicy` class exposes several methods such as `clone()`, `Setup(grpc::ClientContext &)`, and `OnCompletion()` to control the behavior of RPC retries, update the context, and determine the delay between attempts."]]],[]]
