![]() ![]() The number of backfills each DCP client can perform concurrently has been limited to allow fairer allocation of resources. OSO backfill in Magma now sets the correct resume point after a pause.ĭata Service rebalance duration was significantly impacted if other DCP clients created a large number of Streams, if those streams needed to be read from disk, due to the lack of prioritizing between rebalance and other DCP clients. This happened where the stream was paused and resumed when the resume point was wrongly set to a key already processed in the stream. Metadata items are now cleaned when the expiry pager runs.ĭCP clients streamed in out-of-sequence-order backfill snapshots under Magma observed duplicate documents received in the disk snapshot. GET_META requests for deleted items fetched metadata in memory which was not evicted in value-eviction buckets. NET SDK on Windows 10 client and client certs were enabled on CB Server, the Data-Service did not establish a connection and client bootstrap failed with a OpenSSL “session id context uninitialized" error.ĭata-Service has been updated to disable TLS session resume. This was due to a specific unanticipated state in memory which increased CPU usage, and connection became unusable for further operations.ĭeleteWithMeta is now resilient to temporary non-existent values with xattr datatype. XDCR or restore from backup entered an endless loop if attempting to overwrite a document which was deleted or expired some time ago with a deleteWithMeta operation. Memory pressure recovery logic (Item expelling) is now skipped when replica rollback is in progress. In rare cases, after a failover or memcached restart, a replica rollback while under memory pressure might have caused a crash in the Data Service. The lastReadSeqno is now Incremented when the client is not collection-aware. ![]() ItemExpel has been enhanced to release all the items in a checkpoint when memory conditions allow.Ī rollback loop affected legacy clients when collections were used and a tombstone newer than the last mutation in the default collection was purged. In scenarios such as large average item size, high numbers of replicas or low Bucket quota could result in a data-node entering an unrecoverable Out-of-Memory state. The last item in a replica checkpoint was not expelled. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |