[LU-10879] FLR: Describe resync event for policy engine Created: 04/Apr/18  Updated: 22/Aug/18

Status: Open
Project: Lustre
Component/s: None
Affects Version/s: None
Fix Version/s: None

Type: Improvement Priority: Minor
Reporter: Jian Yu Assignee: Jian Yu
Resolution: Unresolved Votes: 0
Labels: FLR2

Rank (Obsolete): 9223372036854775807

 Description   

With delayed write implemented in FLR phase 1, while writing to a mirrored file, only one primary or preferred mirror will be updated directly during the write, and other mirrors will be marked as STALE. The state of the mirrored file will be changed from RDONLY to WRITE_PENDING, and this change will be recorded as type "FLRW" in Lustre MDT ChangeLog. The mirrored file can subsequently return to a RDONLY state again by resync operation, which can be done by "lfs mirror resync" command or policy engine.

In this ticket, we'll describe the resync event in detail so that it can be integrated into a policy engine like Robinhood.


Generated at Sat Feb 10 02:38:59 UTC 2024 using Jira 9.4.14#940014-sha1:734e6822bbf0d45eff9af51f82432957f73aa32c.