August 2016 Summaries

CockroachDB, a scalable and consistent SQL database, initially prioritized correctness and performance but has faced challenges with stability, particularly in maintaining a stable 10-node cluster under continuous load. The complexity of intertwined components, under or over-designed stability fixes, and constant code changes have contributed to this instability. To address this, the team has initiated a "code yellow" focusing on stability, designating a dedicated team to manage stability fixes separately from new feature development. This strategic shift has impacted contributors, who now work on a separate branch to minimize instability, and users, who have experienced a slowdown in beta releases as stability is prioritized over new features. The team anticipates resuming regular releases focused on stability fixes, with new features available only from the source.

CockroachDB encountered a significant, long-standing bug in its SQL handling due to a combination of design flaws and language constraints, specifically in the way it managed table and column references using Go. The bug, a classic "schrödinbug," was exposed through fuzz testing, which revealed that improperly handled SQL syntax could cause the database server to crash. The root issue stemmed from using a single, complex Go data type, `QualifiedName`, for multiple SQL objects, which led to errors in normalization and checking. To resolve this, the team implemented a more robust solution by introducing distinct types for different SQL objects, ensuring more precise handling and reducing the risk of similar issues in the future. This change required extensive modifications to the SQL codebase but ultimately strengthened the system's reliability by leveraging strong typing practices.

CockroachDB has expanded its communication channels over the past 30 months, initially using GitHub and later adding various platforms like Google Groups and Gitter to connect users and developers. Despite this growth, efforts to centralize community interactions have been limited until now, as the company introduces the CockroachDB Community Forum. This new platform aims to facilitate discussions on how-tos, best practices, and development updates, such as the recent upgrade to Go 1.7. With the launch of the forum, CockroachDB will deprecate its Google Groups by August 12, 2016, while other channels like Gitter remain operational, though users may be encouraged to engage more through the forum. The forum has been initially populated with frequently asked questions and is expected to become increasingly beneficial as community participation grows, inviting users and developers to contribute to a vibrant exchange of knowledge.