Re: Improving real world performance by moving files closer to their target workloads

[Gordan Bobic <gordan@xxxxxxxxxx>]

Derek Price wrote:

> If all nodes do attempt to stay up to date with this information, then 
> if the node accepting a write goes incommunicado, the quorum can simply 
> and effectively roll back the transaction by revoking the node's lock 
> and rolling back its idea of the current version number of the affective 
> file or directory.

And with that we're back to the journalling idea. If we have a per file 
journal (write-ahead log, if you will), then if the writing node fails 
during the write, when it's lock is expired, the other nodes can just 
roll back the transaction.

Gordan