Update to design document overview and trim of appendix #9648
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
LGTM |
petermattis
reviewed
Sep 30, 2016
| ranges. | ||
| CockroachDB is a distributed SQL database. The primary design goals | ||
| are **scalability**, **strong consistency** and **survivability** | ||
| (hence the name). Cockroach aims to tolerate disk, machine, rack, and |
There was a problem hiding this comment.
Should we consistently use CockroachDB in this document?
| additional CockroachDB nodes. Ranges are merged and split to maintain | ||
| a target size, by default `64M`. The relatively small size facilitates | ||
| quick repair and rebalancing to address node failures, new capacity | ||
| and even read/write load. |
There was a problem hiding this comment.
There is also pressure for a larger size to minimize the meta2 index size.
| replication factor), theoretically up to 4 exabytes (4E) of logical | ||
| data; | ||
| - client queries can be sent to any node in the cluster, and queries | ||
| can operate fully independently from each other, meaning that |
There was a problem hiding this comment.
The queries can operate independently when there aren't conflicts. Not sure if that detail is worth calling out here.
| overall throughput is a linear factor of the number of nodes in the | ||
| cluster. | ||
| - queries are distributed (ref: distributed SQL) so that the overall | ||
| throughput of single queries can also be increased by adding more |
There was a problem hiding this comment.
s/can also be/can be/g
| throughput of single queries can also be increased by adding more | ||
| nodes. | ||
|
|
||
| CocroachDB achieves strong consistency: |
There was a problem hiding this comment.
s/CocroachDB/CockroachDB/g
| CockroachDB achieves survivability: | ||
| - range replicas can be co-located within a single datacenter for low | ||
| latency replication and survive disk or machine failures. They can | ||
| be located across racks to survive some network switch failures. |
There was a problem hiding this comment.
s/located/distributed/g
spencerkimball
commented
Sep 30, 2016
| additional CockroachDB nodes. Ranges are merged and split to maintain | ||
| a target size, by default `64M`. The relatively small size facilitates | ||
| quick repair and rebalancing to address node failures, new capacity | ||
| and even read/write load. |
| replication factor), theoretically up to 4 exabytes (4E) of logical | ||
| data; | ||
| - client queries can be sent to any node in the cluster, and queries | ||
| can operate fully independently from each other, meaning that |
| overall throughput is a linear factor of the number of nodes in the | ||
| cluster. | ||
| - queries are distributed (ref: distributed SQL) so that the overall | ||
| throughput of single queries can also be increased by adding more |
| throughput of single queries can also be increased by adding more | ||
| nodes. | ||
|
|
||
| CocroachDB achieves strong consistency: |
| CockroachDB achieves survivability: | ||
| - range replicas can be co-located within a single datacenter for low | ||
| latency replication and survive disk or machine failures. They can | ||
| be located across racks to survive some network switch failures. |
Closed
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This change is