Vulncheck / Vulncheck (pull_request) Successful in 6m1sDetails
Build / Build Components (1.21) (pull_request) Successful in 7m37sDetails
Build / Build Components (1.20) (pull_request) Successful in 7m52sDetails
Tests and linters / Staticcheck (pull_request) Successful in 8m56sDetails
Tests and linters / Lint (pull_request) Successful in 9m26sDetails
Tests and linters / Tests (1.21) (pull_request) Successful in 15m5sDetails
Tests and linters / Tests with -race (pull_request) Successful in 15m7sDetails
DCO action / DCO (pull_request) Successful in 1m1sDetails
Tests and linters / Tests (1.20) (pull_request) Successful in 4m1sDetails
Badger implementation isn't tested and works not well,
but requires human resources to maintain.
Signed-off-by: Dmitrii Stepanov <d.stepanov@yadro.com>
DCO action / DCO (pull_request) Successful in 1m59sDetails
Vulncheck / Vulncheck (pull_request) Successful in 3m31sDetails
Build / Build Components (1.20) (pull_request) Successful in 4m37sDetails
Build / Build Components (1.21) (pull_request) Successful in 4m33sDetails
Tests and linters / Tests (1.20) (pull_request) Successful in 4m54sDetails
Tests and linters / Staticcheck (pull_request) Successful in 4m49sDetails
Tests and linters / Tests with -race (pull_request) Successful in 5m9sDetails
Tests and linters / Lint (pull_request) Successful in 6m4sDetails
Tests and linters / Tests (1.21) (pull_request) Successful in 6m9sDetails
Now it is possible to enable compressability estimation.
If data is likely uncompressable, it should reduce CPU time and memory.
Signed-off-by: Dmitrii Stepanov <d.stepanov@yadro.com>
Concurrent initialization in case of the metabase resync leads to
high memory consumption and potential OOM.
Signed-off-by: Dmitrii Stepanov <d.stepanov@yadro.com>
Include settings for block and mutex profilers.
They are disabled by default, as in Go runtime itself.
Signed-off-by: Pavel Karpy <p.karpy@yadro.com>
Signed-off-by: Evgenii Stratonikov <e.stratonikov@yadro.com>
Currently, DELETE service sets tombstone expiration epoch to
`current epoch + 5`. This works less than ideal in private networks
where an epoch can be e.g. 10 minutes. In this case, after a node is
unavailable for more than 1 hour, already deleted objects have a chance
to reappear.
After this commit tombstone lifetime can be configured.
Signed-off-by: Evgenii Stratonikov <e.stratonikov@yadro.com>