Tomasz Grabiec 22948238b6 row_cache: Fix potential timeout or deadlock due to sstable read concurrency limit ...

database::make_sstable_reader() creates a reader which will need to
obtain a semaphore permit when invoked. Therefore, each read may
create at most one such reader in order to be guaranteed to make
progress. If the reader tries to create another reader, that may
deadlock (or for non-system tables, timeout), if enough number of such
readers tries to do the same thing at the same time.

Avoid the problem by dropping previous reader before creating a new
one.

Refs #2644.

Message-Id: <1501152454-4866-1-git-send-email-tgrabiec@scylladb.com>

2017-07-27 13:58:20 +03:00

9.3 KiB

Raw Blame History

View Raw