tree 1ec54a9b4c248d72f083e168db2d7b2fc2a73086
parent aed96f0b524998469e27d1ed40cb97d79b5ed2f8
author luochen <cluo8@uci.edu> 1551329099 -0800
committer Luo Chen <cluo8@uci.edu> 1551577469 -0800

[ASTERIXDB-2522][TX] Skip WAIT record during lock conflicts

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

Details:
- A small optimization to our deadlock-free locking potocol by skipping
the WAIT record. Once the partial frame has been flushed and previous
records are committed, the locks held by the write thread will
eventually be released by the log flusher thread. There is no need to
force the writer thread to wait for the log flusher thread.

Change-Id: I6ef3979d6393d45a6b7b2eb5f09f147299b5cd9f
Reviewed-on: https://asterix-gerrit.ics.uci.edu/3232
Sonar-Qube: Jenkins <jenkins@fulliautomatix.ics.uci.edu>
Tested-by: Jenkins <jenkins@fulliautomatix.ics.uci.edu>
Contrib: Jenkins <jenkins@fulliautomatix.ics.uci.edu>
Integration-Tests: Jenkins <jenkins@fulliautomatix.ics.uci.edu>
Reviewed-by: Murtadha Hubail <mhubail@apache.org>