storage_service: Drop _update_jobs

This field is write-only.
Leftover from 83ffae1 (storage_service: Drop block_until_update_pending_ranges_finished)

Signed-off-by: Pavel Emelyanov <xemul@scylladb.com>
Message-Id: <20191226091210.20966-1-xemul@scylladb.com>
This commit is contained in:
Pavel Emelyanov
2019-12-26 12:12:10 +03:00
committed by Avi Kivity
parent f2b20e7083
commit 34f8762c4d
2 changed files with 1 additions and 5 deletions

View File

@@ -3165,12 +3165,9 @@ future<> storage_service::do_update_pending_ranges() {
future<> storage_service::update_pending_ranges() {
return get_storage_service().invoke_on(0, [] (auto& ss){
ss._update_jobs++;
return ss._update_pending_ranges_action.trigger_later().then([&ss] {
// calculate_pending_ranges will modify token_metadata, we need to repliate to other cores
return ss.replicate_to_all_cores().finally([&ss, ss0 = ss.shared_from_this()] {
ss._update_jobs--;
});
return ss.replicate_to_all_cores().then([s = ss.shared_from_this()] { });
});
});
}

View File

@@ -151,7 +151,6 @@ private:
gms::gossiper& _gossiper;
sharded<auth::service>& _auth_service;
sharded<cql3::cql_config>& _cql_config;
int _update_jobs{0};
// Note that this is obviously only valid for the current shard. Users of
// this facility should elect a shard to be the coordinator based on any
// given objective criteria