Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

[DOC] Update data integrity check performance that do not use a -dev version #8574

Open
derekbit opened this issue May 15, 2024 · 0 comments
Open

[DOC] Update data integrity check performance that do not use a -dev version #8574

derekbit opened this issue May 15, 2024 · 0 comments
Assignees
@mantissahz
Labels
area/performance System, volume performance area/volume-data-integrity Volume Data integrity related kind/doc Doc request priority/1 Highly recommended to fix in this release (managed by PO)
Milestone
v1.7.0

Comments

@derekbit
Copy link
Member

derekbit commented May 15, 2024 •
edited

What's the document you plan to update? Why? Please describe

Update data integrity check performance that do not use a -dev version

https://longhorn.io/docs/1.6.1/advanced-resources/data-integrity/snapshot-data-integrity-check/#performance-impact

Additional context

https://suse.slack.com/archives/C02CLV7D2KH/p1715762144009509
@derekbit derekbit added the kind/doc Doc request label May 15, 2024
@derekbit derekbit added this to the v1.7.0 milestone May 15, 2024
@derekbit derekbit added area/performance System, volume performance area/volume-data-integrity Volume Data integrity related priority/1 Highly recommended to fix in this release (managed by PO) labels May 15, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@mantissahz mantissahz

Labels
area/performance System, volume performance area/volume-data-integrity Volume Data integrity related kind/doc Doc request priority/1 Highly recommended to fix in this release (managed by PO)
Projects
None yet
Milestone
v1.7.0
Development

No branches or pull requests
2 participants
@derekbit @mantissahz