- Sep 06, 2024
-
-
Georgy Moshkin authored
-
Georgy Moshkin authored
-
Georgy Moshkin authored
-
Georgy Moshkin authored
-
Georgy Moshkin authored
-
Georgy Moshkin authored
We only use Eq ranges
-
Georgy Moshkin authored
-
Georgy Moshkin authored
-
Дмитрий Афанасьев authored
-
Дмитрий Афанасьев authored
-
Дмитрий Афанасьев authored
-
Дмитрий Афанасьев authored
-
Дмитрий Афанасьев authored
-
Yaroslav Dynnikov authored
-
-
-
-
-
-
-
-
- Sep 04, 2024
-
-
Виталий Шунков authored
-
- Sep 03, 2024
-
-
-
Егор Ивков authored
-
Егор Ивков authored
-
Егор Ивков authored
-
Егор Ивков authored
-
-
- Sep 02, 2024
-
-
Вартан Бабаян authored
-
Maksim Kaitmazian authored
-
- Aug 30, 2024
-
-
Maksim Kaitmazian authored
-
roman.kuzmin authored
-
-
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.
-
Georgy Moshkin authored
-
Georgy Moshkin authored
Closes #875
-
Georgy Moshkin authored
-
Georgy Moshkin authored
-
Georgy Moshkin authored
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.
-