Re-edit of PGD - third set of edits #5784
Merged
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
ebgitelman
commented
Jun 19, 2024
| @@ -25,6 +25,8 @@ At the end of the provisioning stage, you will have the required number of insta | |||
| ## Deploy | |||
| The `tpaexec deploy` command installs and configures Postgres and other software on the provisioned servers. TPA can create the servers, but it doesn't matter who created them so long as SSH and sudo access are available. This includes setting up replication, backups, and so on. | |||
There was a problem hiding this comment.
@djw-m I couldn't trace what "This" means in the last sentence. Can you clarify?
ebgitelman
commented
Jun 19, 2024
product_docs/docs/pgd/5/deploy-config/deploy-tpa/deploying/02-deploying.mdx
Outdated
Show resolved
Hide resolved
ebgitelman
commented
Jun 19, 2024
| @@ -79,7 +79,9 @@ This doesn't allow COMMIT status to be retrieved, but it does let you choose ava | |||
|
|
|||
| For a CAMO partner to switch to ready, it needs to be connected, and the estimated catchup interval needs to drop below the `timeout` value of `TO ASYNC`. You can check the current readiness status of a CAMO partner with [`bdr.is_camo_partner_ready()`](/pgd/latest/reference/functions#bdris_camo_partner_ready), while [`bdr.node_replication_rates`](/pgd/latest/reference/catalogs-visible#bdrnode_replication_rates) provides the current estimate of the catchup time. | |||
|
|
|||
| The switch from CAMO protected to asynchronous mode is only ever triggered by an actual CAMO transaction either because the commit exceeds the `timeout` value of `TO ASYNC` or, in case the CAMO partner is already known, disconnected at the time of commit. This switch is independent of the estimated catchup interval. If the CAMO pair is configured to require the current node to be the write lead of a group as configured through `enable_proxy_routing` node group option. See [Commit scopes](commit-scopes) for syntax. This can prevent a split brain situation due to an isolated node from switching to asynchronous mode. If `enable_proxy_routing` isn't set for the CAMO group, the origin node switches to asynchronous mode immediately. | |||
| The switch from CAMO-protected to asynchronous mode is only ever triggered by an actual CAMO transaction. This is true either because the commit exceeds the `timeout` value of `TO ASYNC` or, in case the CAMO partner is already known, disconnected at the time of commit. This switch is independent of the estimated catchup interval. If the CAMO pair is configured to require the current node to be the write lead of a group as configured through the `enable_proxy_routing` node group option. See [Commit scopes](commit-scopes) for syntax. This can prevent a split brain situation due to an isolated node from switching to asynchronous mode. If `enable_proxy_routing` isn't set for the CAMO group, the origin node switches to asynchronous mode immediately. | |||
There was a problem hiding this comment.
@djw-m This is a fragment:
If the CAMO pair is configured to require the current node to be the write lead of a group as configured through the enable_proxy_routing node group option.
Can you figure out what was meant?
Also, I was again not able to trace what "This" meant in the second-to-last sentence.
ebgitelman
commented
Jun 19, 2024
ebgitelman
commented
Jun 19, 2024
ebgitelman
commented
Jun 19, 2024
ebgitelman
commented
Jun 19, 2024
|
@djw-m I have a few queries on this one. Thank you! |
djw-m
reviewed
Jun 26, 2024
djw-m
approved these changes
Jun 26, 2024
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.
What Changed?