1
72%
master: 72%

Ran 15 Aug 2018 02:51PM UTC

Files 434

Run time 1min

Badge

Embed ▾

Committed 15 Aug 2018 02:51PM UTC coverage: 72.199% (-0.1%) from 72.321%

Job # 180.1

Build Type

push

jenkins

Committed by Sijie Guo

Commit Message

Provide consistent locking mechanism in EntryLogManagerForEntryLogPerLedger

Descriptions of the changes in this PR:

Assumption: The lock stored alongside the EntryLog in this map is meant
to be used to ensure that no two threads can be writing to the same
ledger at the same time.

The above invariant can be violated if the EntryLogAndLockTuple
object is evicted from the cache while in a critical section nominally
protected by the contained lock.

The conditions required for this to happen would be pretty odd --
there needs to be a huge amount of cache churn during one of
the protected operations.

The fix for this issue is to allocate in the constructor a fixed array of locks and select
for each EntryLogAndLockTuple a lock from that array
deterministically by ledgerId such that the same ledgerId
will always get the same lock.

Author: cguttapalem <cguttapalem@salesforce.com>

Reviewers: Sijie Guo <sijie@apache.org>

This closes #1600 from reddycharan/elmlock

Run Details

24786 of 34330 relevant lines covered (72.2%)

0.72 hits per line

apache / bookkeeper / 180 / 1
72%
master: 72%

README BADGES
x

Markdown

Textile

RDoc

HTML

Rst

Source Files on job 180.1

apache / bookkeeper / 180 / 1 72% master: 72%

README BADGES x

Markdown

Textile

RDoc

HTML

Rst

Source Files on job 180.1

apache / bookkeeper / 180 / 1
72%
master: 72%

README BADGES
x