Skip to content

Conversation

@Tim-Brooks
Copy link
Contributor

This is a followup to #27551. That commit introduced a bug where the
incorrect byte buffers would be returned when we attempted a write. This
commit fixes the logic.

This is a followup to elastic#27551. That commit introduced a bug where the
incorrect byte buffers would be returned when we attempted a write. This
commit fixes the logic.
@Tim-Brooks Tim-Brooks added :Distributed Coordination/Network Http and internode communication implementations >bug v6.2.0 v7.0.0 labels Dec 7, 2017
@Tim-Brooks Tim-Brooks merged commit 5b3230c into elastic:master Dec 7, 2017
Tim-Brooks added a commit that referenced this pull request Dec 7, 2017
This is a followup to #27551. That commit introduced a bug where the
incorrect byte buffers would be returned when we attempted a write. This
commit fixes the logic.
Tim-Brooks added a commit to Tim-Brooks/elasticsearch that referenced this pull request Dec 7, 2017
This is a follow up to elastic#27695. This commit adds a test checking that
across multiple writes using multiple buffers, a write operation
properly keeps track of which buffers still need to be written.
Tim-Brooks added a commit that referenced this pull request Dec 7, 2017
This is a follow up to #27695. This commit adds a test checking that
across multiple writes using multiple buffers, a write operation
properly keeps track of which buffers still need to be written.
Tim-Brooks added a commit that referenced this pull request Dec 7, 2017
This is a follow up to #27695. This commit adds a test checking that
across multiple writes using multiple buffers, a write operation
properly keeps track of which buffers still need to be written.
@Tim-Brooks Tim-Brooks deleted the fix_write_issue branch December 10, 2018 16:19
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

>bug :Distributed Coordination/Network Http and internode communication implementations v6.2.0 v7.0.0-beta1

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants