Krbd exclusive locking » History » Version 1
Josh Durgin, 07/01/2015 12:35 AM
1 | 1 | Josh Durgin | h1. krbd exclusive locking |
---|---|---|---|
2 | 1 | Josh Durgin | |
3 | 1 | Josh Durgin | *Summary* |
4 | 1 | Josh Durgin | Exclusive locking allows rbd to ensure that only one client updates an rbd image at time, to preserve metadata consistency. |
5 | 1 | Josh Durgin | This is a building block for other rbd features like object map and journalling, and provides a bit of extra safety in case a supposedly dead client reconnects. |
6 | 1 | Josh Durgin | |
7 | 1 | Josh Durgin | *Owners* |
8 | 1 | Josh Durgin | Doug Fuller (Red Hat) |
9 | 1 | Josh Durgin | |
10 | 1 | Josh Durgin | *Interested Parties* |
11 | 1 | Josh Durgin | Josh Durgin (Red Hat) |
12 | 1 | Josh Durgin | |
13 | 1 | Josh Durgin | *Current Status* |
14 | 1 | Josh Durgin | Patches for watch/notify2 and cls_lock primitives that are used to implement this are posted for review. |
15 | 1 | Josh Durgin | |
16 | 1 | Josh Durgin | *Detailed Description* |