tree 0dac03698680bcd7e9db33cf69179303b5cf8ce5
parent ed4b04680224ce9209bf417247d6c0424c4dfc3d
author Abdullah Alamoudi <bamousaa@gmail.com> 1510536094 -0800
committer abdullah alamoudi <bamousaa@gmail.com> 1510553983 -0800

[NO ISSUE][TX] Fix DatasetLock for Multiple Index Builds

- user model changes: no
- storage format changes: no
- interface changes: no

details:
- The mechanism used for allowing multiple concurrent index
  builds does not work if the first index build finishes
  before other index builds. It relied on a write lock
  obtained by the first index builder and released by
  the last index builder. This is not allowed when using
  ReentrantReadWriteLock and will lead to an
  IllegalMonitorStateException since the last thread to exit
  did not hold the lock.
- Potential Deadlock between modify and exclusive modify can
  happen when an exclusive modify attempts to upgrade the
  lock to write lock while the modify lock waits for the
  exclusive lock to release. This has been fixed too.
- Test cases were added.

Change-Id: I3bea3ff2075d952ab13402b0c445c464b431c0f5
Reviewed-on: https://asterix-gerrit.ics.uci.edu/2144
Integration-Tests: Jenkins <jenkins@fulliautomatix.ics.uci.edu>
Tested-by: Jenkins <jenkins@fulliautomatix.ics.uci.edu>
Contrib: Jenkins <jenkins@fulliautomatix.ics.uci.edu>
Reviewed-by: Michael Blow <mblow@apache.org>