storage_proxy: use counter-specific timeout for writes

This commit is contained in:
Paweł Dziepak
2017-02-24 11:38:32 +00:00
parent d177160f90
commit cf193f4b41
2 changed files with 2 additions and 2 deletions

View File

@@ -489,7 +489,7 @@ public:
val(read_request_timeout_in_ms, uint32_t, 5000, Used, \
"The time that the coordinator waits for read operations to complete" \
) \
val(counter_write_request_timeout_in_ms, uint32_t, 5000, Unused, \
val(counter_write_request_timeout_in_ms, uint32_t, 5000, Used, \
"The time that the coordinator waits for counter writes to complete." \
) \
val(cas_contention_timeout_in_ms, uint32_t, 5000, Unused, \

View File

@@ -1208,7 +1208,7 @@ future<> storage_proxy::mutate_counters(Range&& mutations, db::consistency_level
}
// Forward mutations to the leaders chosen for them
auto timeout = clock_type::now() + std::chrono::milliseconds(_db.local().get_config().write_request_timeout_in_ms());
auto timeout = clock_type::now() + std::chrono::milliseconds(_db.local().get_config().counter_write_request_timeout_in_ms());
auto my_address = utils::fb_utilities::get_broadcast_address();
return parallel_for_each(leaders, [this, cl, timeout, tr_state = std::move(tr_state), my_address] (auto& endpoint_and_mutations) {
auto endpoint = endpoint_and_mutations.first;