You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Dec 19, 2017. It is now read-only.
The current implementation of Copycat's log does not handle concurrency well. This prevents leaders from replicating to followers in parallel and prevents log compaction processes from occurring in parallel with other reads. This limitation is mitigated to some extent by buffering entries in the log and biased locking for synchronized methods, but the lack of true support for concurrent access of the log still represents a significant flaw in the architecture that needs to be resolved.
The log needs to be re-architected with a per-segment read-write lock that allows leaders to replicate to followers in parallel and reduces the overhead of locating entries within the log.
The text was updated successfully, but these errors were encountered:
The current implementation of Copycat's log does not handle concurrency well. This prevents leaders from replicating to followers in parallel and prevents log compaction processes from occurring in parallel with other reads. This limitation is mitigated to some extent by buffering entries in the log and biased locking for synchronized methods, but the lack of true support for concurrent access of the log still represents a significant flaw in the architecture that needs to be resolved.
The log needs to be re-architected with a per-segment read-write lock that allows leaders to replicate to followers in parallel and reduces the overhead of locating entries within the log.
The text was updated successfully, but these errors were encountered: