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

hammer: rgw: subset of uploaded objects via radosgw are unretrievable when using EC pool #9407

Merged
merged 1 commit into from Jul 7, 2016

Conversation

smithfarm
Copy link
Contributor

@smithfarm smithfarm self-assigned this May 31, 2016
@smithfarm smithfarm added this to the hammer milestone May 31, 2016
Fixes: http://tracker.ceph.com/issues/15745

When complete_writing_data() is called, if pending_data_bl is not empty
we still need to handle stripe transition correctly. If pending_data_bl
has more data that we can allow in current stripe, move to the next one.

Signed-off-by: Yehuda Sadeh <yehuda@redhat.com>
(cherry picked from commit b7a7d41)

Conflicts:
	src/rgw/rgw_rados.cc (hammer write_data() takes rgw_obj reference as
	4th argument, hammer throttle_data() takes rgw_obj as 2nd argument)
smithfarm added a commit that referenced this pull request Jun 1, 2016
…ia radosgw are unretrievable when using erasure coded pool

Reviewed-by: Nathan Cutler <ncutler@suse.com>
smithfarm added a commit that referenced this pull request Jun 27, 2016
…ia radosgw are unretrievable when using erasure coded pool

Reviewed-by: Nathan Cutler <ncutler@suse.com>
@yehudasa yehudasa merged commit 387d5c1 into ceph:hammer Jul 7, 2016
@smithfarm smithfarm deleted the wip-15833-hammer branch July 7, 2016 17:20
@smithfarm smithfarm changed the title hammer: RGW :: Subset of uploaded objects via radosgw are unretrievable when using erasure coded pool hammer: rgw: subset of uploaded objects via radosgw are unretrievable when using EC pool Aug 15, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
2 participants