You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This was originally found (and fixed) by @gleb-cloudius , but the patch set with the fix was reverted at some point, and the fix went away. Now the error remains even in new, nice coroutine code.
We check the wrong var in the inner loop of the pre-fill path of allocate_segment_ex, often causing us to generate giant writev:s of more or less the whole file. Not intended.
The text was updated successfully, but these errors were encountered:
elcallio
pushed a commit
to elcallio/scylla
that referenced
this issue
Mar 29, 2021
Fixesscylladb#8369
This was originally found (and fixed) by @gleb-cloudius, but the patch set with the
fix was reverted at some point, and the fix went away. Now the error remains even
in new, nice coroutine code.
We check the wrong var in the inner loop of the pre-fill path of allocate_segment_ex,
often causing us to generate giant writev:s of more or less the whole file.
Not intended.
This was originally found (and fixed) by @gleb-cloudius , but the patch set with the fix was reverted at some point, and the fix went away. Now the error remains even in new, nice coroutine code.
We check the wrong var in the inner loop of the pre-fill path of
allocate_segment_ex
, often causing us to generate giant writev:s of more or less the whole file. Not intended.The text was updated successfully, but these errors were encountered: