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"]],[["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-05 UTC."],[[["This page provides documentation for the `GrpcCompletionQueueOption` across multiple versions, from 2.10.1 up to the latest release candidate 2.37.0-rc."],["`GrpcCompletionQueueOption` allows users to specify a custom `CompletionQueue` for gRPC background tasks, rather than relying on the library's default queue."],["When a custom `CompletionQueue` is provided, it becomes the caller's responsibility to ensure that threads are actively servicing the queue."],["`GrpcCompletionQueueOption` cannot be used concurrently with `GrpcBackgroundThreadPoolSizeOption` or `GrpcBackgroundThreadsFactoryOption`, as they are mutually exclusive."]]],[]]
