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 page provides documentation for the \u003ccode\u003eGrpcCompletionQueueOption\u003c/code\u003e across multiple versions, ranging from 2.10.1 to the latest release candidate 2.37.0-rc.\u003c/p\u003e\n"],["\u003cp\u003e\u003ccode\u003eGrpcCompletionQueueOption\u003c/code\u003e allows users to specify a custom \u003ccode\u003eCompletionQueue\u003c/code\u003e for gRPC background tasks, rather than relying on the library's default queue.\u003c/p\u003e\n"],["\u003cp\u003eWhen a custom \u003ccode\u003eCompletionQueue\u003c/code\u003e is provided, it becomes the user's responsibility to ensure that threads are actively servicing the queue.\u003c/p\u003e\n"],["\u003cp\u003e\u003ccode\u003eGrpcCompletionQueueOption\u003c/code\u003e is mutually exclusive with \u003ccode\u003eGrpcBackgroundThreadPoolSizeOption\u003c/code\u003e and \u003ccode\u003eGrpcBackgroundThreadsFactoryOption\u003c/code\u003e, meaning only one of these can be used.\u003c/p\u003e\n"],["\u003cp\u003eThe page also details the "Alias Of" relationship, stating that the type \u003ccode\u003eCompletionQueue\u003c/code\u003e is aliased to a specific type.\u003c/p\u003e\n"]]],[],null,[]]
