[Bugs] [Bug 1583462] Sharding sends all application sent fsyncs to the main shard file

[bugzilla at redhat.com]

https://bugzilla.redhat.com/show_bug.cgi?id=1583462

Krutika Dhananjay <kdhananj at redhat.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
           Doc Type|If docs needed, set a value |Bug Fix


--- Doc Text *updated* ---
Cause: 
Previously when an application sent fsync on a sharded file, shard translator was not sending fsync on the modified shards.
Consequence: 
We were able to live under this limitation because replicate translator would regularly send fsyncs on shards written to. But now, since we will be supporting single-brick distributed sharded volumes (and that means no replicate translator on stack), we need to make sure shard translator sends fsync on modified shards to prevent data loss.

Fix: 
Now the shard translator keeps track of all shards associated with every file that were modified and when the application sends fsync on the main file, fsync is also sent on these changed shards.
Result: 
This fix allows us to support sharding in non-replicated volumes too.


-- 
You are receiving this mail because:
You are on the CC list for the bug.
Unsubscribe from this bug https://bugzilla.redhat.com/token.cgi?t=QYFL6E4gWL&a=cc_unsubscribe