-
Notifications
You must be signed in to change notification settings - Fork 189
Enterprise docs for 1.4 #457
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
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)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
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
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
don't forget TODO
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
1.3.0+ ... version 3 isn't that old :)
|
Will +1 when UpgradeV2toV3 formatting is fixed |
|
+1 bravo bro |
No description provided.