If this option is set, the library will use the supplied CompletionQueue instead of its own. The caller is responsible for making sure there are thread(s) servicing this CompletionQueue. The client library will not create any background threads or attempt to call CompletionQueue::Run().
[[["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-02 UTC."],[[["This webpage provides documentation for the `GrpcCompletionQueueOption` across multiple versions, ranging from 2.10.1 to the latest release candidate 2.37.0-rc."],["The `GrpcCompletionQueueOption` allows users to specify a custom `CompletionQueue` for gRPC background operations, rather than relying on the library's default queue."],["If a custom `CompletionQueue` is provided, the user is responsible for ensuring threads are actively servicing that queue, as the library will not manage threads for it."],["`GrpcBackgroundThreadPoolSizeOption`, `GrpcCompletionQueueOption`, and `GrpcBackgroundThreadsFactoryOption` are mutually exclusive."],["This page contains a list of the alias type, being `CompletionQueue`."]]],[]]
