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
It ensures correctness during procedures and reduces the lock's scope, making the procedure execution faster.
What does the feature do?
Considers introducing a fine-grained lock service(memory-based) in the meta server's leader. And procedure acquires locks on demand.
The incorrect locking
If we didn't acquire the lock before operating the shared resource, it might incur data inconsistency.
coarse-grained locking
The procedure acquires the coarse-grained lock during the whole procedure. However, if the scope of locks overlaps, procedures are executed serially.
fine-grained locking
Implementation challenges
However, if the old leader loses the leadership(e.g., network partition), its running procedure can still write data into etcd, which also incurs data inconsistency.
The text was updated successfully, but these errors were encountered:
What problem does the new feature solve?
It ensures correctness during procedures and reduces the lock's scope, making the procedure execution faster.
What does the feature do?
Considers introducing a fine-grained lock service(memory-based) in the meta server's leader. And procedure acquires locks on demand.
The incorrect locking
If we didn't acquire the lock before operating the shared resource, it might incur data inconsistency.
coarse-grained locking
The procedure acquires the coarse-grained lock during the whole procedure. However, if the scope of locks overlaps, procedures are executed serially.
fine-grained locking
Implementation challenges
However, if the old leader loses the leadership(e.g., network partition), its running procedure can still write data into etcd, which also incurs data inconsistency.
The text was updated successfully, but these errors were encountered: