Docs 146 clarify which configuration are at group or node l #5549
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
djw-m
added
the
deploy
djw-m
force-pushed
the
DOCS-146-clarify-which-configuration-are-at-group-or-node-l
branch
from
a4b33e3
to
c9af31d
Compare
github-actions
bot
temporarily deployed
to
pr-5549-docs-146-clarify-which-configuration-are-at-group-or-node-l
Signed-off-by: Dj Walker-Morgan <[email protected]>
Signed-off-by: Dj Walker-Morgan <[email protected]>
djw-m
force-pushed
the
DOCS-146-clarify-which-configuration-are-at-group-or-node-l
branch
from
c9af31d
to
92f29b5
Compare
github-actions
bot
temporarily deployed
to
pr-5549-docs-146-clarify-which-configuration-are-at-group-or-node-l
Rahila
reviewed
Apr 30, 2024
product_docs/docs/pgd/5/reference/nodes-management-interfaces.mdx
Outdated
Show resolved
Hide resolved
product_docs/docs/pgd/5/reference/nodes-management-interfaces.mdx
Outdated
Show resolved
Hide resolved
Signed-off-by: Dj Walker-Morgan <[email protected]>
Rahila
reviewed
May 16, 2024
| | `num_writers` | Number of parallel writers for the subscription backing this node group. Valid values are either `-1` or a positive integer. `-1` means the value specified by the GUC `bdr.writers_per_subscription` is used. `-1` is the default. Applies to top-level group only.| | ||
| | `enable_wal_decoder` | Enables/disables the decoding worker process. You can't enable the decoding worker process if `streaming_mode` is already enabled. Valid values are either `on` or `off`. Default is `off`. Applies to top-level group only.| | ||
| | `streaming_mode` | Enables/disables streaming of large transactions. When set to `off`, streaming is disabled. When set to any other value, large transactions are decoded while they're still in progress, and the changes are sent to the downstream. If the value is set to `file`, then the incoming changes of streaming transactions are stored in a file and applied only after the transaction is committed on upstream. If the value is set to `writer`, then the incoming changes are directly sent to one of the writers, if available. If parallel apply is disabled or no writer is free to handle streaming transaction, then the changes are written to a file and applied after the transaction is committed. If the value is set to `auto`, PGD tries to intelligently pick between `file` and `writer`, depending on the transaction property and available resources. You can't enable `streaming_mode` if the WAL decoder is already enabled.<br/><br/>For more details, see [Transaction streaming](../transaction-streaming). Applies to top-level group only.| | ||
| | `default_commit_scope` | The commit scope to use by default, initially the `local` commit scope. This applies only to the top-level node group. You can use individual rules for different origin groups of the same commit scope. See [Origin groups](../durability/commit-scopes/#origin-groups) for more details. | |
There was a problem hiding this comment.
I think we can say that this is supported for subgroups as well. However, the support is not straightforward and would need some more explanation as pointed by Vaijayanti here : https://enterprisedb.atlassian.net/browse/BDR-4947
There was a problem hiding this comment.
The statement "applies to toplevel node-group" needs correction.
Could you create a reference here to the explanation on:
https://enterprisedb.atlassian.net/browse/BDR-4947
that you would put in docs? Is it in this PR?
There was a problem hiding this comment.
No it is not in this PR, but someone is going to have to explain to me why I'm being told conflicting things. I was told that the functions in the older bdr.alter_node_group_config( did not work for subgroups.
Now, back up at line 38 is the same statement which I assume is wrong now.
But someone is going to have to clarify (ie not just say "that is wrong") what the functionality of default_commit_scope is and how it differs between the two calls, assuming that is actually a thing.
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?
Reference fix with tables for alter_node_group_option that detail top or sub-group or all.