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

DNM : osd: avoid multi set osd_op.outdata in tier pool #5888

Closed
wants to merge 1 commit into from

Conversation

Abhishekvrshny
Copy link

There are two read op on the same object for ec pool. First op read
miss happend, calling do_proxy_read and promote_object, The second op only
do_proxy_read. but before first op process_copy_chunk finish, the second op
finish_proxy_read. first op receive reply from base pool
first and then second received. so the second op set the field "outdata"
in m->ops first. And then first op requeue_ops in process_copy_chunk,
At last in do_osd_ops, it append outdata field.

Fixes: 12540
Signed-off-by: Xinze Chi <xmdxcxz@gmail.com>
(cherry picked from commit 855ae1f)

Conflicts:
	src/osd/ReplicatedPG.cc
@tchaikov tchaikov added this to the hammer milestone Sep 11, 2015
@ghost
Copy link

ghost commented Sep 15, 2015

It may require commit 90e5f41 to be in hammer, as per my understanding.

@ghost ghost self-assigned this Sep 15, 2015
@Abhishekvrshny
Copy link
Author

@XinzeChi this commit does not apply cleanly, would you mind taking a look ?

http://jenkins.ceph.dachary.org/job/ceph/LABELS=centos-7&&x86_64/7703/console

osd/ReplicatedPG.cc:11761:76: error: expected '}' at end of input
 void intrusive_ptr_release(ReplicatedPG::RepGather *repop) { repop->put(); }
                                                                            ^
osd/ReplicatedPG.cc:11761:76: error: expected '}' at end of input

@XinzeChi
Copy link
Contributor

@Abhishekvrshny , it conflicts with proxy write.
So I submit another patch for hammer?

@Abhishekvrshny
Copy link
Author

@dachary : What do we suggest to @XinzeChi ?

@ghost
Copy link

ghost commented Sep 21, 2015

@XinzeChi it would be great if you could adapt your patch to hammer. If the differences are such that it does not make sense to resolve the conflicts, a new patch is also fine.

@Abhishekvrshny thanks for the reminder :-)

@Abhishekvrshny Abhishekvrshny changed the title osd: avoid multi set osd_op.outdata in tier pool DNM : osd: avoid multi set osd_op.outdata in tier pool Sep 21, 2015
@XinzeChi
Copy link
Contributor

@dachary , @Abhishekvrshny , I have fix this conflict at #6060

@tchaikov
Copy link
Contributor

closing this pr, as #6060 supersedes it.

@tchaikov tchaikov closed this Sep 24, 2015
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
4 participants