Skip to content

[Config] Document configuration options related to replication #3851

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.

Sign up for GitHub

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

Jump to bottom
Closed
Tracked by #3544
andreyaksenov opened this issue Nov 14, 2023 · 1 comment · Fixed by #3834
Closed
Tracked by #3544

[Config] Document configuration options related to replication #3851

andreyaksenov opened this issue Nov 14, 2023 · 1 comment · Fixed by #3834
Assignees
@andreyaksenov
Labels
3.0 config

Comments

@andreyaksenov
Copy link
Contributor

andreyaksenov commented Nov 14, 2023 •
edited
Loading

Next step: #3654

Product: Tarantool
Since: 3.0
Root document:

SME: @ Totktonada

Details

Schema: https://github.com/tarantool/tarantool/blob/941a85c39735b789914da04acad3faabd63b5dd6/src/box/lua/config/instance_config.lua#L1068

Related YAML sections:

  • replicasets (<replicaset_name>, leader)
  • groups (<group_name>.replicasets)
  • replication
  • iproto (listen, advertise.peer)
  • instances
  • credentials (replicator user)
  • database (mode: ro, rw; replica set UUID)

See notes here: #3654.
@andreyaksenov andreyaksenov self-assigned this Nov 14, 2023
@andreyaksenov andreyaksenov linked a pull request Nov 14, 2023 that will close this issue
3.0 config: replication reference #3834
Merged
This was referenced Nov 14, 2023
Closed
Closed
@andreyaksenov
Copy link
Contributor Author

https://docs.d.tarantool.io/en/doc/3.0/reference/configuration/configuration_reference/

Totktonada added a commit to Totktonada/tarantool that referenced this issue Dec 5, 2023
@Totktonada
config: don't try to persist anon replica name
05784df 
The commit effectively enables support of anonymous replicas in the
declarative configuration. It has several caveats (see the changelog
entry), which will be resolved in the following commits of the patchset.

An attempt to persist an instance name of an anonymous replica can't be
successful, because it has no entry in `_cluster` system space. Such an
attempt leads to ER_INSTANCE_NAME_MISMATCH error.

This commit patches the configuration applying logic to skip attempt to
set `box.cfg({instance_name = <...>})` if the instance is configured as
an anonymous replica using `replication.anon: true` option.

Part of tarantool#9432

NO_DOC=replication.anon option is already documented in the scope of
       tarantool/doc#3851. The bugfix
       shouldn't affect the documentation pages much, however related
       constraints are summarized in a documentation request in the last
       commit of the series.
Totktonada added a commit to Totktonada/tarantool that referenced this issue Dec 5, 2023
@Totktonada
config: don't try to persist anon replica name
965e5a0 
The commit effectively enables support of anonymous replicas in the
declarative configuration. It has several caveats (see the changelog
entry), which will be resolved in the following commits of the patchset.

An attempt to persist an instance name of an anonymous replica can't be
successful, because it has no entry in `_cluster` system space. Such an
attempt leads to ER_INSTANCE_NAME_MISMATCH error.

This commit patches the configuration applying logic to skip attempt to
set `box.cfg({instance_name = <...>})` if the instance is configured as
an anonymous replica using `replication.anon: true` option.

Part of tarantool#9432

NO_DOC=replication.anon option is already documented in the scope of
       tarantool/doc#3851. The bugfix
       shouldn't affect the documentation pages much, however related
       constraints are summarized in a documentation request in the last
       commit of the series.
Totktonada added a commit to Totktonada/tarantool that referenced this issue Dec 6, 2023
@Totktonada
config: don't try to persist anon replica name
dbdb80f 
The commit effectively enables support of anonymous replicas in the
declarative configuration. It has several caveats (see the changelog
entry), which will be resolved in the following commits of the patchset.

An attempt to persist an instance name of an anonymous replica can't be
successful, because it has no entry in `_cluster` system space. Such an
attempt leads to ER_INSTANCE_NAME_MISMATCH error.

This commit patches the configuration applying logic to skip attempt to
set `box.cfg({instance_name = <...>})` if the instance is configured as
an anonymous replica using `replication.anon: true` option.

Part of tarantool#9432

NO_DOC=replication.anon option is already documented in the scope of
       tarantool/doc#3851. The bugfix
       shouldn't affect the documentation pages much, however related
       constraints are summarized in a documentation request in the last
       commit of the series.
Totktonada added a commit to Totktonada/tarantool that referenced this issue Dec 6, 2023
@Totktonada
config: don't try to persist anon replica name
2b0f33a 
The commit effectively enables support of anonymous replicas in the
declarative configuration. It has several caveats (see the changelog
entry), which will be resolved in the following commits of the patchset.

An attempt to persist an instance name of an anonymous replica can't be
successful, because it has no entry in `_cluster` system space. Such an
attempt leads to ER_INSTANCE_NAME_MISMATCH error.

This commit patches the configuration applying logic to skip attempt to
set `box.cfg({instance_name = <...>})` if the instance is configured as
an anonymous replica using `replication.anon: true` option.

Part of tarantool#9432

NO_DOC=replication.anon option is already documented in the scope of
       tarantool/doc#3851. The bugfix
       shouldn't affect the documentation pages much, however related
       constraints are summarized in a documentation request in the last
       commit of the series.
Totktonada added a commit to tarantool/tarantool that referenced this issue Dec 6, 2023
@Totktonada
config: don't try to persist anon replica name
1f533fc 
The commit effectively enables support of anonymous replicas in the
declarative configuration. It has several caveats (see the changelog
entry), which will be resolved in the following commits of the patchset.

An attempt to persist an instance name of an anonymous replica can't be
successful, because it has no entry in `_cluster` system space. Such an
attempt leads to ER_INSTANCE_NAME_MISMATCH error.

This commit patches the configuration applying logic to skip attempt to
set `box.cfg({instance_name = <...>})` if the instance is configured as
an anonymous replica using `replication.anon: true` option.

Part of #9432

NO_DOC=replication.anon option is already documented in the scope of
       tarantool/doc#3851. The bugfix
       shouldn't affect the documentation pages much, however related
       constraints are summarized in a documentation request in the last
       commit of the series.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@andreyaksenov andreyaksenov

Labels
3.0 config
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

3.0 config: replication reference tarantool/doc
1 participant
@andreyaksenov