Enterprise docs for 1.4 #457
Merged
Conversation
This file contains hidden or 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
A fully meshed set up of clusters removes the need to cascade at all.
Removed the term 'double write' and using write request and extraneous write request. Also expanded the example explanation. Added a second way to mitigate extra write requests.
…the titles (and because "New" will someday be "old" while something else takes its place)
| @@ -0,0 +1,71 @@ | |||
| --- | |||
There was a problem hiding this comment.
This file doesn't exist in the navigation
|
I hope my comments aren't too pedantic. Just trying to keep consistency in style. These docs are amazing, thanks for all the hard work. |
…te from naming change
|
|
||
| riak-repl connect boston | ||
|
|
||
| where <sink_cluster_name> is replaced with the name of the sink cluster. |
There was a problem hiding this comment.
These lines are pretty pedantic.
* connect the source cluster to the sink cluster
On any node in the source cluster:
`riak-repl connect <sink_cluster_name>`
For example:
riak-repl connect boston
where <sink_cluster_name> is replaced with the name of the sink cluster.
Could be just as clear with:
* connect the source cluster to the sink cluster. Assuming the sink cluster name *boston*:
`riak-repl connect boston`
You've been using boston as the sink cluster all along, no need to change it now.
| * To start fullsync replication from source to sink: | ||
| `riak-repl fullsync start <sink_cluster_name>` | ||
|
|
||
| Running `riak-repl status` on any node of the source will show which sinks are currently running a fullsync. #TODO mention queue/socket stats |
| --- | ||
| title: "Multi Data Center Replication: Comparison" | ||
| project: riakee | ||
| version: 1.0.0+ |
There was a problem hiding this comment.
1.3.0+ ... version 3 isn't that old :)
|
Will +1 when UpgradeV2toV3 formatting is fixed |
|
+1 bravo bro |
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.
No description provided.