Details
-
Bug
-
Resolution: Fixed
-
Minor
-
None
-
None
-
3
-
9223372036854775807
Description
Currently, the lfsck_in_notify() contains too much functionalities, including both the remote LFSCK control and local LFSCK notification. These different LFSCK requirements share the same structure "lfsck_request" to parse kinds of data. It is difficult to enhance the "lfsck_request" with more local LFSCK requirements, because enlarging or adjusting the lfsck_request fields will affect the LFSCK RPC on-wire protocol and caused interoperability issues.
We will split the local LFSCK notifications from the lfsck_in_notify() with new LFSCK API, then even if we have more local LFSCK requirements in future, we can enhance such API freely without affecting LFSCK RPC protocol.