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.

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

rgw: fix throttle_data size not correct #22638

Closed
wants to merge 1 commit into from

Conversation

tianshan
Copy link
Contributor

If handle_data get not enough for one write, we will put in pending_data_bl,
so the throttle_data will only throttle the last bl. This will affect put
and data sync, big object's throttle will useless.

make RGWPutObjProcessor_Atomic::handle_data return the actual write_size,
throttle_data will get the return size to throttle.

Fixes: http://tracker.ceph.com/issues/24594

Signed-off-by: Tianshan Qu tianshan@xsky.com

If handle_data get not enough for one write, we will put in pending_data_bl,
so the throttle_data will only throttle the last bl. This will affect put
and data sync, big object's throttle will useless.

make RGWPutObjProcessor_Atomic::handle_data return the actual write_size,
throttle_data will get the return size to throttle.

Fixes: http://tracker.ceph.com/issues/24594

Signed-off-by: Tianshan Qu <tianshan@xsky.com>
@stale
Copy link

stale bot commented Oct 17, 2018

This pull request has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs.
If you are a maintainer or core committer, please follow-up on this issue to identify what steps should be taken by the author to move this proposed change forward.
If you are the author of this pull request, thank you for your proposed contribution. If you believe this change is still appropriate, please ensure that any feedback has been addressed and ask for a code review.

@stale stale bot added the stale label Oct 17, 2018
@mattbenjamin
Copy link
Contributor

@tianshan I think the issue this fixes is resolved by the PutObjProcessor refactoring; could you review that and resubmit if there is still an issue?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
3 participants