Release 2.14.0 - #1349
Merged
Merged
Conversation
sssciel
approved these changes
Aug 6, 2026
Mockird31
approved these changes
Aug 6, 2026
bigbes
force-pushed
the
bigbes/release-v2.14.0
branch
4 times, most recently
from
August 6, 2026 10:59
34232db to
542f80c
Compare
`CartridgeApp.set_failover` returned as soon as `tt cartridge failover
setup` reported success, but the clusterwide config patch it makes
drives every instance through ConfiguringRoles once more. A command
issued right after it raced with that reconfiguration and got
failed to edit replicasets: Prepare2pcError: "localhost:8010":
Instance state is ConfiguringRoles, can't apply config in this state
which flaked test_promote_cartridge_failovers on Tarantool 1.10 and 2.x.
The wait `bootstrap` did inline is extracted into
`wait_inst_roles_configured`, which now looks at the last recorded state
transition instead of the presence of any, so it is usable after an
arbitrary reconfiguration and not only right after bootstrap.
`set_failover` waits before returning.
`bootstrap` itself passed no --timeout, leaving `tt replicaset
bootstrap` with its 10s default. That is not enough for a two-phase
commit over the whole cluster on a loaded runner, and
test_vshard_bootstrap_cartridge errored in setup with
failed to edit replicasets: NetboxCallError: "localhost:8010":
Timeout exceeded
so the helper now asks for 60s.
Part of TNTP-9154
Part of TNTP-9154
bigbes
force-pushed
the
bigbes/release-v2.14.0
branch
from
August 6, 2026 11:43
542f80c to
66a94d5
Compare
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.
Overview
This release introduces cluster backup and restore:
tt backupplans a backup, takes it on the nodes, uploads the archives with a cluster manifest to file or S3 storage, and verifies and prunes that storage, whilett restoreplans a recovery point and prepares the instance work directories for it. It also adds cluster topology discovery withtt cluster topologyand the\historycommand in the interactive console, and fixes line loss and hangs intt log -faround log rotation.Only the CHANGELOG is changed here — the code landed in the preceding pull requests. The entries below are shortened to their first sentence; see
CHANGELOG.mdfor the full text.Added
tt backup startandtt backup finalize: add support for creating and finalizing local backup artifacts.tt cluster topology: add cluster topology discovery from a file, etcd, or Tarantool Config Storage with table and JSON output.tt backup last: add support for displaying the latest backup manifest from file or S3 storage.tt backup verify: add a read-only health check of a backup storage: missing and corrupted archives, breaks in the backup chain, and dangling archives.tt backup gc: add retention-based cleanup of a backup storage.tt backup plan: add backup planning command that computes last valid manifest fortt backup start.tt backup upload: add a command that builds a cluster manifest from per-shard fragments and uploads archives and the manifest to file or S3 storage.tt backup plan,upload,verify,gc,lastandtt restore plan:--cluster-nameand--environmentselect the<storage_root>/<cluster_name>/<environment>/subtree of the storage, so one storage can hold several clusters.tt restore plan: add restore planning on the manager host.tt restore apply: add preparation of an instance work directory from a backup chain.tt connect: add\historycommand to display the last executed commands in the interactive console.Changed
tt stop: preliminary interrupts the processes to enable parallel termination.tt create vshard_cluster: the generated rockspec now pinsvshard 0.1.42instead of0.1.25.tt backup: removecreation_durationfrom the cluster manifest — the field was unused and is no longer serialized.Fixed
tt log -f: possible line loss/duplication on rename, hanging after a watched log directory is removed, and lines written just as the file was read to the end not showing up until the next write.Part of TNTP-9154