Closed polyrabbit closed 2 weeks ago
It's slow to test, which will slow down the mount.
The AK/SK is verified in format/config, which should be enough.
format
only verifies the AK/SK but cannot check user's environment. A typical scenario is when a node cannot connect to OSS for various reasons, such as DNS issues or VPC network isolation problems. In such cases, users may encounter EIO
errors in the middle of his task.
If we can perform some cheap self-checks at startup to expose errors early, we can avoid expensive user-side errors.
It could be useful in some cases, should be enabled by a flag.
Do you have a suggestion for this flag's name?
--check-storage
?
Updated. Please review, thanks!
Attention: Patch coverage is 29.41176%
with 12 lines
in your changes missing coverage. Please review.
Project coverage is 53.87%. Comparing base (
c2b21f4
) to head (c20ebe7
). Report is 70 commits behind head on main.
Files with missing lines | Patch % | Lines |
---|---|---|
cmd/mount.go | 0.00% | 10 Missing :warning: |
cmd/format.go | 0.00% | 2 Missing :warning: |
:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.
Test object storage at startup to fail fast instead of throwing
EIO
in the middle of user's workload.