Closed archit-rastogi closed 1 month ago
on 2.16 -> 2024.1 upgrade path, the tserver launching the read request (on newer version) sets the wait policy to wait on conflict, but the tserver handling the read (on older version) doesn't handle this well, and errors with the above message. On 2.16
auto conflict_management_policy = wait_queue ? docdb::WAIT_ON_CONFLICT : docdb::FAIL_ON_CONFLICT; // rightly checks
const auto& pairs = write_batch.read_pairs();
if (!pairs.empty() && write_batch.has_wait_policy()) {
switch (write_batch.wait_policy()) {
case WAIT_BLOCK:
conflict_management_policy = docdb::WAIT_ON_CONFLICT; // overwrites without checking if wait queues are enabled
break; // and hence leading to the error.
...
}
}
so upgrades from <= 2.16 to >= 2024.1 might face this issue.
credits: @basavaraj29
This error is expected during upgrade from wait-on-conflict off (< 2024.1 release) to wait-on-conflict on (>=2024.1 release). The test can add this as an expected failure.
Jira Link: DB-12152
Description
Issue Type
kind/bug
Warning: Please confirm that this issue does not contain any sensitive information