-
Notifications
You must be signed in to change notification settings - Fork 55
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.
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
Revert allocation transaction committed #3491
Revert allocation transaction committed #3491
Conversation
/packit test |
052e31d
to
2939c32
Compare
/packit test |
1 similar comment
/packit test |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This all looks good. One minor docs request.
2939c32
to
b62424e
Compare
I also made one PR revision that appeared to be required to avoid a panic in cases where we incorrectly calculate the amount of space to allocate from the backstore to the thinpool. I bumped into this due to a bug in #3274 that I intend to fix but it seems better to handle that case with an error in case we introduce another bug like that in the future. |
Putting back in progress to look into one additional piece brought up by #3274. |
47df312
to
63a5aef
Compare
/packit test |
I think this is ready for final review. |
63a5aef
to
2a7a542
Compare
/packit test |
2a7a542
to
c4a7e9f
Compare
@jbaublitz Plz rebase when you get the chance. |
c4a7e9f
to
b7b8a73
Compare
/packit test |
@jbaublitz Plz rebase when you get the chance and we can merge this. |
This code has two notable drawbacks that make it better to remove. 1. The code is never used as intended. All requests are immediately followed by a commit. This does not justify the complexity required to maintain the feature. 2. There is an assumption that will likely be broken in future commits related to changes in stacking and metadata. The assumption is that allocations are always driven by the backstore. If this assumption is broken and allocations to reserve space for metadata are performed at layers lower than the backstore, these layers don't have protections against reserving the same space for two separate allocations and then commiting them both.
b7b8a73
to
1c0cd0d
Compare
Related to #3274