You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
both nodes crash just before the first node saves an IP of the second node in the system.peers table (error injection "crash-before-bootstrapping-node-added"). Bootstrap tokens of the second node are already saved in topology_coordinator::handle_topology_transition.
restart the first node and query it with inserts and selects
the node gets this error after entering commit cdc generation transition state
CDC generation publisher fiber repeats this operation until it succeeds. It succeeds when the first node enters the left token ring transition state. This doesn't break the node but should be investigated.
@margdoc please investigate at least which read exactly is failing with this error -- if it's a local read (from system table), then it's suspicious that it's failing.
(BTW I was hoping you'd introduce this info when opening the issue, as we agreed...)
The failing write is from system_distributed_keyspace -> system_keyspace::create_cdc_desc
co_awaitmax_concurrent_for_each(ms, 20, [&] (mutation& m) -> future<> {
// We use the storage_proxy::mutate API since CQL is not the best for handling large batches.co_await _sp.mutate(
{ std::move(m) },
quorum_if_many(ctx.num_token_owners),
db::timeout_clock::now() + 30s,
nullptr, // trace_stateempty_service_permit(),
db::allow_per_partition_rate_limit::no,
false// raw_counters
);
});
When running
on margdoc@e4b4a62, the first node gets an error:
The scenario of this test is as follows:
system.peers
table (error injection "crash-before-bootstrapping-node-added"). Bootstrap tokens of the second node are already saved intopology_coordinator::handle_topology_transition
.commit cdc generation
transition stateCDC generation publisher fiber repeats this operation until it succeeds. It succeeds when the first node enters the
left token ring
transition state. This doesn't break the node but should be investigated.topology_experimental_raft.test_ip_mappings.1.log
scylla-1.log
scylla-2.log
The text was updated successfully, but these errors were encountered: