Question about cephfs MDS journal

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Hi Team,

I have a question about MDS journal trim policy.
I found the MDS journal would be flushed when the segment number is over the predefined value (default 30) only in tick thread context.
If the journal is not over the predefined value, the segments would not be flushed to the OMAP even eventhrough  the system is not busy. 
My question is what’s the intention for the design? 
I can understand that journal replay is able to restore metadata into memory, there is no negative impact even though the journal is committed to the backend OMAP. 
Is there any more concern?
What if we flush the journal segments in the every tick period as along as journal is not empty?


Thanks
Javen--
To unsubscribe from this list: send the line "unsubscribe ceph-devel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html



[Index of Archives]     [CEPH Users]     [Ceph Large]     [Information on CEPH]     [Linux BTRFS]     [Linux USB Devel]     [Video for Linux]     [Linux Audio Users]     [Yosemite News]     [Linux Kernel]     [Linux SCSI]
  Powered by Linux