errose28 commented on PR #6226:
URL: https://github.com/apache/ozone/pull/6226#issuecomment-1967976530
I was talking about this with @aswinshakil and there is another problem we
should consider: the size of the Ratis snapshot might be far greater than the
size of the final OM DB. This is because the Ratis snapshot has "inflated" all
the hardlinks, so if there are many filesystem snapshots on dense buckets, the
OM DB device needs an undetermined amount of space greater than the current DB
in order to install the ratis snapshot. If this space is not available and we
remove the configs, there is no good way out of the situation. We already don't
have great handling to make sure there is always room to install a ratis
snapshot, but the hardlink inflation makes the problem worse.
One idea to mitigate the problem:
1. Allow ratis snapshot to be installed wherever is configured, as it is
currently.
2. Copy files one-by-one to the OM DB dir. If the file is in the hardlink
list, create a link instead of a new file.
- This keeps space required on the OM DB device to no more than double
that of the current DB, regardless of the amount of snapshots and hardlinks. It
still does not make sure there is *always* space, but it is not worse than the
current system behavior.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
