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-08-14 UTC."],[[["\u003cp\u003eThis webpage provides documentation for the \u003ccode\u003eGrpcCompletionQueueOption\u003c/code\u003e across multiple versions, from 2.10.1 up to the latest release candidate 2.37.0-rc.\u003c/p\u003e\n"],["\u003cp\u003eThe \u003ccode\u003eGrpcCompletionQueueOption\u003c/code\u003e allows users to specify a custom \u003ccode\u003eCompletionQueue\u003c/code\u003e for gRPC background operations, rather than relying on the library's default queue.\u003c/p\u003e\n"],["\u003cp\u003eIf a custom \u003ccode\u003eCompletionQueue\u003c/code\u003e is provided, users are responsible for ensuring threads service the queue, as the library will not manage these threads.\u003c/p\u003e\n"],["\u003cp\u003e\u003ccode\u003eGrpcCompletionQueueOption\u003c/code\u003e cannot be used with \u003ccode\u003eGrpcBackgroundThreadPoolSizeOption\u003c/code\u003e or \u003ccode\u003eGrpcBackgroundThreadsFactoryOption\u003c/code\u003e because they are mutually exclusive options.\u003c/p\u003e\n"],["\u003cp\u003eThere are also details about type aliases, specifically one for \u003ccode\u003eCompletionQueue\u003c/code\u003e.\u003c/p\u003e\n"]]],[],null,[]]
