[[["易于理解","easyToUnderstand","thumb-up"],["解决了我的问题","solvedMyProblem","thumb-up"],["其他","otherUp","thumb-up"]],[["很难理解","hardToUnderstand","thumb-down"],["信息或示例代码不正确","incorrectInformationOrSampleCode","thumb-down"],["没有我需要的信息/示例","missingTheInformationSamplesINeed","thumb-down"],["翻译问题","translationIssue","thumb-down"],["其他","otherDown","thumb-down"]],["最后更新时间 (UTC):2025-04-21。"],[[["Asynchronous read pool instances can be created to increase database cluster read throughput and availability by providing read-only clones."],["Each read pool instance requires its own unique manifest file, configured within the database instance's manifest, and up to 20 read pool instances can be created."],["Read pool instances occupy the same amount of storage as the database instance they replicate, and the size of the pool is determined by the number of nodes set during creation."],["The availability and streaming status of a read pool instance can be verified using specific `kubectl` commands, indicating whether it can serve queries and is actively replicating data."],["Even if the main database instance is unreachable, read pool instances will continue serving queries, maintaining availability although data replication may be interrupted."]]],[]]