Home / Companies / Cockroach Labs / Blog / August 2017

August 2017 Summaries

2 posts from Cockroach Labs

Filter
Month: Year:
Post Summaries Back to Blog
A CockroachDB Tech Writer describes the process of documenting new features, emphasizing the importance of understanding business value, thorough testing, and providing clear guidance. The writer highlights a unique feature of CockroachDB: the ability to span a cluster across multiple cloud platforms and migrate data between them with a single command, demonstrated through a video of deploying a 6-node cluster across Digital Ocean and GCE. This process showcases CockroachDB's flexibility, facilitated by the Gossip protocol for self-organization and the Raft consensus algorithm for data replication. The writer further explains how replication zones and node locality settings enable easy data migration and balance across different cloud environments without service interruption, encouraging users to test these capabilities themselves.
Aug 30, 2017 1,309 words in the original blog post.
CockroachDB developed a distributed backup and restore feature in response to user demands for enhanced data security, error recovery, and compliance with legal requirements, despite the database's inherent resilience against data loss. The backup system was designed to be consistent, distributed, and incremental, optimizing resource use and minimizing impact on production traffic. Initially, backups were slow due to centralized data writing, but the introduction of the Export command allowed data to be written directly to cloud storage, leveraging CockroachDB's distributed architecture for scalability. Incremental backups utilize multiversion concurrency control (MVCC) by saving only the data changes since the last backup, although they must occur within a 25-hour window due to data cleanup processes. The result is a fast and efficient backup system, supporting large clusters with minimal downtime, while simpler tools like "cockroach dump" cater to smaller setups. Future enhancements are planned, including point-in-time backups, read-only queries over backups, and more user interface controls, alongside the integration of the RESTORE function to complement the backup process.
Aug 09, 2017 1,291 words in the original blog post.