Move OperationLimiter.acquire() warnings to callers 01/68401/4
authorRobert Varga <robert.varga@pantheon.tech>
Tue, 23 Jan 2018 16:42:44 +0000 (17:42 +0100)
committerRobert Varga <robert.varga@pantheon.tech>
Wed, 28 Feb 2018 17:37:17 +0000 (18:37 +0100)
We have two distinct call sites from where we are acquiring permits,
where failure to acquire has different root cause:
RemoteTransactionContext's failure to acquire indicates a slow leader,
while TransactionContextWrapper indicates a failure to discover a leader
in time.

Modify acquire() to report success and log failures to acquire from
the two call sites, with different messages so it is immediately clear
what is going on.

Change-Id: Ie828984c6a984690224494af1a9fdd0e4f257fab
Signed-off-by: Robert Varga <robert.varga@pantheon.tech>

No differences found