Krbd exclusive locking » History » Version 1
Josh Durgin, 07/01/2015 12:35 AM
| 1 | 1 | Josh Durgin | h1. krbd exclusive locking |
|---|---|---|---|
| 2 | |||
| 3 | *Summary* |
||
| 4 | Exclusive locking allows rbd to ensure that only one client updates an rbd image at time, to preserve metadata consistency. |
||
| 5 | 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 | |||
| 7 | *Owners* |
||
| 8 | Doug Fuller (Red Hat) |
||
| 9 | |||
| 10 | *Interested Parties* |
||
| 11 | Josh Durgin (Red Hat) |
||
| 12 | |||
| 13 | *Current Status* |
||
| 14 | Patches for watch/notify2 and cls_lock primitives that are used to implement this are posted for review. |
||
| 15 | |||
| 16 | *Detailed Description* |