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

Avoid releasing sent buffer to early in BookieClient mock #1651

Conversation

eolivelli
Copy link
Contributor

Cherry pick tp branch-4.8 commit 6b9cbf2 from Ivan Kelly

If the buffer was sent to more than one bookie with the mock, it would
be released after being sent to the first one. Each write should
retain a refCount themselves, and then release when done.

Author: Ivan Kelly ivank@apache.org

Relates to #1598, closes #1643

If the buffer was sent to more than one bookie with the mock, it would
be released after being sent to the first one. Each write should
retain a refCount themselves, and then release when done.

Author: Ivan Kelly <ivank@apache.org>

Reviewers: Sijie Guo <sijie@apache.org>

This closes apache#1598 from ivankelly/double-rel-mock
@eolivelli
Copy link
Contributor Author

@sijie thank you for taking a look so quickly.

do you know why only Travis-CI started to validate this patch, and not ASF Jenkins ?

@sijie
Copy link
Member

sijie commented Sep 5, 2018

@eolivelli not sure. jenkins jobs should start as well.

@eolivelli
Copy link
Contributor Author

@sijie as soon as Travis will turn green I will merge this patch, the fix is trivial, it is already on master.
I think we do not need additional validations

@sijie
Copy link
Member

sijie commented Sep 5, 2018

@eolivelli sure works for me

@eolivelli
Copy link
Contributor Author

rerun integration tests

@eolivelli eolivelli self-assigned this Sep 5, 2018
eolivelli pushed a commit that referenced this pull request Sep 5, 2018
Cherry pick tp branch-4.8 commit 6b9cbf2 from Ivan Kelly

If the buffer was sent to more than one bookie with the mock, it would
be released after being sent to the first one. Each write should
retain a refCount themselves, and then release when done.

Author: Ivan Kelly <ivankapache.org>

Relates to #1598, closes #1643

Author: Ivan Kelly <ivank@apache.org>

Reviewers: Sijie Guo <sijie@apache.org>

This closes #1651 from eolivelli/fix/cherry-pick-mock-client-tests-errors
@eolivelli
Copy link
Contributor Author

closed with b5065b9

@eolivelli eolivelli closed this Sep 5, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants