Added a `wait_index` parameter to `proc_replication_demote` to improve
synchronization during demotion operations.

Diana Tikhonova authored 4 months ago and Diana Tikhonova committed 2 months ago

Key updates include:
Adding the term field to relevant RPC requests (ConfigureReplicationRequest, ReplicationSyncRequest, and DemoteRequest).
Utilizing node.status().check_term(req.term) in critical sections of the replication logic.

I found this by compiling tarantool with CMAKE_BUILD_TYPE=Debug

Closes #1130

Add new files:
- storage/snapshot.rs: stuff related to raft snapshot
- storage/schema.rs: stuff related to DDL logic

Code is only moved, no changes to logic

This patch changes when we update current_master_name during consistent
master switchover. Now it is updated as soon as we determine that the
new master has synchronized it's vclock with the old master.

As a result we can now block expel of a non-last replica in cases where
other replicas are offline, which is crucial because instances can
easily become offline due to temporary network issues.

Kurdakov Alexander authored 6 months ago and Alexander Kurdakov committed 5 months ago

New argument `--timeout` for `picodata connect`.

Up to this patch `instance_uuid` and `replicaset_uuid` were generated
using name-based UUID v3. So all instances named `i1` in all clusters
had the same UUID.

With this patch UUIDs become random v4. Particular UUID values are
generated in two locations:

1. `start_boot` (src/lib.rs)
2. `handle_join_request_and_wait` -> `build_instance` (src/rpc/join.rs)

Function `Instance::new()` is removed in favor of explicit struct
construction.

godzie44 authored 7 months ago and Georgy Moshkin committed 6 months ago

Closes #664

Kurdakov Alexander authored 6 months ago and Alexander Kurdakov committed 6 months ago

Tier of replicaset if exists must match with tier from arguments of rpc.

Move vshard related fields from _pico_property to _pico_tier
and adapt it in governor algorithm

This reverts commit d7e93cfc.

Maksim Kaitmazian authored 7 months ago and Georgy Moshkin committed 7 months ago

A global lock for schema changes that solves the following issue:
An expensive index creation can cause RPC timeouts, resulting in re-sending of the
same RPC even though the operation is still in progress on the master. The second RPC
attempts to create the same index, but it realizes that the index already exists
even if the operation has not been completed yet. To handle this scenario, a global
lock was added in `proc_apply_schema_change` to prevent concurrent schema changes.

Closes #875

CAS predicates should always contain the current raft term, because this
is what's explicitly checked in proc_cas.

Note that this will sometimes result in a EntryTermMismatch error
because the latest applied entry may have a different term in case the
election has started but not finished yet.

We could add this check to all the client cas precondition checks, but
it's not a big deal, because we handle the situation correctly anyways.