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"]],[["Missing the information I need","missingTheInformationINeed","thumb-down"],["Too complicated / too many steps","tooComplicatedTooManySteps","thumb-down"],["Out of date","outOfDate","thumb-down"],["Samples / code issue","samplesCodeIssue","thumb-down"],["Other","otherDown","thumb-down"]],["Last updated 2025-07-18 UTC."],[[["This document provides details on the `RPCBackoffPolicy` class within the Google Cloud Bigtable C++ client library, with version history from 2.11.0 to the latest release candidate 2.37.0-rc."],["The `RPCBackoffPolicy` class defines the interface for controlling how the Bigtable client handles retries after failed RPC operations, managing aspects such as the number of attempts and the delay between them."],["The application provides an instance of `RPCBackoffPolicy` when creating a `Table` or `TableAdmin` object, which then serves as a prototype for new `RPCBackoffPolicy` objects."],["Key functions within the `RPCBackoffPolicy` include `clone()`, `Setup(grpc::ClientContext &)`, and `OnCompletion(Status const &)`, which handle object creation, context setup, and delay determination after an RPC completion respectively."]]],[]]
