Details
-
New Feature
-
Status: Resolved
-
Major
-
Resolution: Fixed
-
0.8.0
-
None
-
None
Description
Currently we have the following synchronization in Log.scala:
1. append, roll, and flush all share a write lock
2. read is non-blocking
Unfortunately this means that flush time latency is added to appends (even if the flush is done by a background thread). To fix this we should investigate a scheme to make append and flush not block each other.