Details
-
Bug
-
Resolution: Fixed
-
Minor
-
None
-
None
-
3
-
9223372036854775807
Description
Otherwise, soft limit will be very close to hard limit, and on sluggish network, extended soft limit can reach hard limit easily, and the whole recovery will be aborted easier. Actually, IR is used to shorten the client reconnect time during recovery, so shrink soft limit is good enough. It doesn't make sense to shrink the hard limit.
Attachments
Activity
Link | New: This issue is duplicated by SEA-186 [ SEA-186 ] |
Link | New: This issue is related to SEA-287 [ SEA-287 ] |
Link | New: This issue is related to JFC-17 [ JFC-17 ] |
Link | New: This issue is related to LDEV-301 [ LDEV-301 ] |
Fix Version/s | New: Lustre 2.10.0 [ 12204 ] | |
Resolution | New: Fixed [ 1 ] | |
Status | Original: Open [ 1 ] | New: Resolved [ 5 ] |
Description | Original: Otherwise, hard time is reached as soon as recovery time expires, and no chance for VBR. | New: Otherwise, soft limit will be very close to hard limit, and on sluggish network, extended soft limit can reach hard limit easily, and the whole recovery will be aborted easier. Actually, IR is used to shorten the client reconnect time during recovery, so shrink soft limit is good enough. It doesn't make sense to shrink the hard limit. |
Summary | Original: recovery hard time should be extended when extending recovery time | New: recovery hard time should not be shrunk for IR |
Description | Original: client data deletion should be done synchronously, otherwise, the data client could be left on disk when server is shutdown. | New: Otherwise, hard time is reached as soon as recovery time expires, and no chance for VBR. |
Landed for 2.10