Core 1829- Docs Migration: Added New Clustering Docs #8
Merged
Conversation
terraHDB
changed the title
* doc migration epic branch * 3/4 progress of security * finished configuration.md, began users and roles * users and roles migrated; still needs updates * updated user and roles operations * corrections to security docs * CORE-1825 Add/Update "install harpedb" subtopics (#1) * added mac, added/updated windows, added/updated node version requirements, and added offline docs * go requirements * docs adjustments * testing variable usage * testing variable usage * Update other.md Update installation for other operating systems. * added link to download * node version * exact replica download button * functional download link * deleted old link * node version Co-authored-by: Kris Zyp <kriszyp@gmail.com> * Core 1826 add/update harperdb studio topic and subtopics (#2) * added mac, added/updated windows, added/updated node version requirements, and added offline docs * 1/3 through studio subtopics * 2/3 through studio subtopics * 3/3 through studio subtopics * corrected harperdb operations api * removed icon descriptions and fixed typos * removed icon descriptions * primary key vs hash_attribute change * primary key vs hash attribute qualifier * minor change to example function Co-authored-by: Kris Zyp <kriszyp@gmail.com>
# Conflicts: # docs/harperdb-cloud/index.md # docs/harperdb-studio/index.md
| @@ -1 +1,3 @@ | |||
| # Clustering | |||
|
|
|||
Member
There was a problem hiding this comment.
Clustering introduction needs more than this. How much of the existing into do you think we could incorporate here?
| @@ -0,0 +1,64 @@ | |||
| # Authentication | |||
|
|
|||
Member
There was a problem hiding this comment.
How come all this security/studio stuff is in the clustering PR?
Contributor
Author
There was a problem hiding this comment.
the security/studio pr was mistakenly merged to main, rather than the epic CORE-1824
|
|
||
| To create a cluster you must have two or more nodes* (aka instances) of HarperDB running. | ||
|
|
||
| **A node is a single instance/installation of HarperDB constitutes a node. A node of HarperDB can operate independently with clustering on or off.* |
Member
There was a problem hiding this comment.
This sentence sounds off.
|
|
||
| Subscriptions can be added, updated, or removed through the API. | ||
|
|
||
| _Note: The schema and tables in the subscription must exist on the local node (the node that is receiving the API request), but do not need to exist on the remote node. Any schema and tables that do not exist on the remote node will be automatically created._ |
Member
There was a problem hiding this comment.
This has changed. Now the schema and table must exist in at least one location - local or remote. If it doesnt exist on the"other" location it will be created
…havior description
kriszyp
approved these changes
Nov 28, 2022
DavidCockerill
approved these changes
Nov 29, 2022
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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 PR includes a reworking of our cluster docs. Old clustering docs can be found here