You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@couchdb.apache.org by GitBox <gi...@apache.org> on 2020/11/26 17:42:45 UTC
[GitHub] [couchdb-documentation] thigg opened a new pull request #608: Description of Standalone vs Cluster
thigg opened a new pull request #608:
URL: https://github.com/apache/couchdb-documentation/pull/608
## Overview
Added a short description of Standalone and Clustermode which should make clearer what the purposes of the modes are. I tried to sketch it to make the process easier.
## Testing recommendations
Give the text to someone who has no in-depth knowledge of couchdb.
## Checklist
- [ ] Update [rebar.config.script](https://github.com/apache/couchdb/blob/master/rebar.config.script) with the commit hash once this PR is rebased and merged
<!-- Before opening the PR, consider running `make check` locally for a faster turnaround time -->
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [couchdb-documentation] wohali merged pull request #608: Description of Standalone vs Cluster
Posted by GitBox <gi...@apache.org>.
wohali merged pull request #608:
URL: https://github.com/apache/couchdb-documentation/pull/608
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [couchdb-documentation] wohali commented on a change in pull request #608: Description of Standalone vs Cluster
Posted by GitBox <gi...@apache.org>.
wohali commented on a change in pull request #608:
URL: https://github.com/apache/couchdb-documentation/pull/608#discussion_r531240765
##########
File path: src/cluster/index.rst
##########
@@ -17,8 +17,8 @@ Cluster Management
==================
As of CouchDB 2.0.0, CouchDB can be run in two different modes of operation:
- * Standalone
- * Cluster
+ * Standalone: The default mode of operation. Each instance is a single logical entity. Typically replication is setup to other standalone CouchDB instances.
Review comment:
The second sentence is also inaccurate here. Something like this is more accurate:
"In this mode, CouchDB's clustering is unavailable. CouchDB's HTML-based replication with other CouchDB installations remains available."
##########
File path: src/cluster/index.rst
##########
@@ -17,8 +17,8 @@ Cluster Management
==================
As of CouchDB 2.0.0, CouchDB can be run in two different modes of operation:
- * Standalone
- * Cluster
+ * Standalone: The default mode of operation. Each instance is a single logical entity. Typically replication is setup to other standalone CouchDB instances.
Review comment:
Standalone isn't the "default" mode of operation. It may be your preference, but it's not the global expectation, nor is it our recommendation (that would be a cluster of 3 nodes for production use).
##########
File path: src/cluster/index.rst
##########
@@ -17,8 +17,8 @@ Cluster Management
==================
As of CouchDB 2.0.0, CouchDB can be run in two different modes of operation:
- * Standalone
- * Cluster
+ * Standalone: The default mode of operation. Each instance is a single logical entity. Typically replication is setup to other standalone CouchDB instances.
+ * Cluster: Multiple CouchDBs build a single entity where each CouchDB is a node in the cluster. The cluster itsself is a single logical database which is hosted on multiple servers/VMs. Operations like writing need to reach a quorum in the cluster to guarantee that the change is agreed on by all nodes eventually.
Review comment:
This is not a great way of describing a cluster, though it's better than the standalone description. How about:
"A cluster of CouchDB installations internally replicate with each other via optimized network connections. This is intended to be used with servers that are in the same data center. This allows for database sharding to improve performance. The theory behind clustering, as well as the required additional configuration steps, are described below."
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [couchdb-documentation] thigg commented on a change in pull request #608: Description of Standalone vs Cluster
Posted by GitBox <gi...@apache.org>.
thigg commented on a change in pull request #608:
URL: https://github.com/apache/couchdb-documentation/pull/608#discussion_r531563180
##########
File path: src/cluster/index.rst
##########
@@ -17,8 +17,8 @@ Cluster Management
==================
As of CouchDB 2.0.0, CouchDB can be run in two different modes of operation:
- * Standalone
- * Cluster
+ * Standalone: The default mode of operation. Each instance is a single logical entity. Typically replication is setup to other standalone CouchDB instances.
+ * Cluster: Multiple CouchDBs build a single entity where each CouchDB is a node in the cluster. The cluster itsself is a single logical database which is hosted on multiple servers/VMs. Operations like writing need to reach a quorum in the cluster to guarantee that the change is agreed on by all nodes eventually.
Review comment:
I removed the last sentence because the same is stated the sentence afterwards
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [couchdb-documentation] thigg commented on pull request #608: Description of Standalone vs Cluster
Posted by GitBox <gi...@apache.org>.
thigg commented on pull request #608:
URL: https://github.com/apache/couchdb-documentation/pull/608#issuecomment-735954051
done
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [couchdb-documentation] thigg commented on pull request #608: Description of Standalone vs Cluster
Posted by GitBox <gi...@apache.org>.
thigg commented on pull request #608:
URL: https://github.com/apache/couchdb-documentation/pull/608#issuecomment-734801968
Thanks for your quick response. I happily put your suggestions into the file (with some small changes).
Feel free to edit the branch directly, should be possible for maintainers.
My intention with creating a pull request was mostly to get things started at the point where I felt information is lacking. As you could see from my original texts, I've been missing important information. Thanks for clearing this up ;)
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [couchdb-documentation] thigg commented on a change in pull request #608: Description of Standalone vs Cluster
Posted by GitBox <gi...@apache.org>.
thigg commented on a change in pull request #608:
URL: https://github.com/apache/couchdb-documentation/pull/608#discussion_r531558834
##########
File path: src/cluster/index.rst
##########
@@ -17,8 +17,8 @@ Cluster Management
==================
As of CouchDB 2.0.0, CouchDB can be run in two different modes of operation:
- * Standalone
- * Cluster
+ * Standalone: The default mode of operation. Each instance is a single logical entity. Typically replication is setup to other standalone CouchDB instances.
Review comment:
I swapped HTML for HTTP, I guess that was your intention
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
[GitHub] [couchdb-documentation] wohali commented on a change in pull request #608: Description of Standalone vs Cluster
Posted by GitBox <gi...@apache.org>.
wohali commented on a change in pull request #608:
URL: https://github.com/apache/couchdb-documentation/pull/608#discussion_r532795316
##########
File path: src/cluster/index.rst
##########
@@ -17,8 +17,12 @@ Cluster Management
==================
As of CouchDB 2.0.0, CouchDB can be run in two different modes of operation:
- * Standalone
- * Cluster
+ * Standalone: In this mode, CouchDB's clustering is unavailable.
+ CouchDB's HTTP-based replication with other CouchDB installations remains available.
+ * Cluster: A cluster of CouchDB installations internally replicate
+ with each other via optimized network connections.
+ This is intended to be used with servers that are in the same data center.
+ This allow for database sharding to improve performance.
Review comment:
`allows` then we can merge this!
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
users@infra.apache.org