We don't expect users to be changing those too often.

Kurdakov Alexander authored 1 year ago and Yaroslav Dynnikov committed 1 year ago

New tarantool options 'memtx_memory' and 'log' can be configured via
picodata cli

1. Add a new option picodata run --shredding to enable shredding upon xlog_remove_file_impl.
2. For test purposes additionally use the inject_errors feature to keep files after shred operation
and allow the test code to look inside and make sure that content was really shredded.

Note: this changes return values from all .proc_* stored procedures,
making them more usable, but completely breaking the compatibility with
older versions.

Closes #500

Dmitry Rodionov authored 1 year ago and Yaroslav Dynnikov committed 1 year ago

Since https://github.com/tarantool/tarantool/pull/8626 memtx_memory is
now rounded up to 64MB in case lower value is specified.

Also prefix stored procedures names `raft_join` and `raft_interact`

Georgy Moshkin authored 2 years ago and Yaroslav Dynnikov committed 2 years ago

Tarantool synchronous replication is broken in such a way, that local
& asynchronous transactions get rolled back upon synchronous
transaction rollback. This is critical for us, because we use local
spaces for the raft log, which should be orthogonal to synchronous
business spaces, but is not due to this behavior. Until it is fixed, we
will not use synchronous replication.

See https://github.com/tarantool/tarantool/issues/7903

Yaroslav Dynnikov authored 2 years ago and Georgy Moshkin committed 2 years ago

32MiB is the minimum allowed memtx_memory size.

Yaroslav Dynnikov authored 2 years ago and Georgy Moshkin committed 2 years ago

Join requests should be made without timeout restrictions. Otherways
it's impossible to tell retried request from instance_id collision.
Retried requests never succeed and return the "already joined" error.

Georgy Moshkin authored 2 years ago and Georgy Moshkin committed 2 years ago

deactivation means that instance
- is demoted to learner (if it wasn't one already)
- is marked "inactive" so that it's ignored when determining
    the number of voters required for the cluster