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-21 UTC."],[[["This document details the `RPCBackoffPolicy` class within the Google Cloud Bigtable C++ client, focusing on how it manages retries for failed RPC operations."],["The `RPCBackoffPolicy` allows users to control the number of retry attempts, the timing between attempts, and the signaling of errors during RPC operations, offering customization for handling failures."],["When creating `Table` or `TableAdmin` objects, users must provide an instance of this `RPCBackoffPolicy` class, which acts as a prototype for generating new `RPCBackoffPolicy` objects with the same settings."],["The class provides methods such as `clone()`, `Setup()`, and `OnCompletion()` to facilitate creating copies, updating the `ClientContext`, and determining delays after RPC operations, respectively."],["This page provides documentation for multiple versions of the RPCBackoffPolicy class, from version 2.11.0 up to the latest release candidate version 2.37.0-rc."]]],[]]
