Skip to content

[CCR] Fix request serialization bug #34917

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

Merged
merged 1 commit into from
Oct 29, 2018

Conversation

martijnvg
Copy link
Member

and some parameters that were not set in tests.

and some parameters that were not set in tests.
@martijnvg martijnvg added >non-issue :Distributed Indexing/CCR Issues around the Cross Cluster State Replication features labels Oct 26, 2018
@martijnvg martijnvg requested a review from dnhatn October 26, 2018 16:11
@elasticmachine
Copy link
Collaborator

Pinging @elastic/es-distributed

@@ -137,9 +137,6 @@ public void testAutoFollowParameterAreDelegated() throws Exception {
if (randomBoolean()) {
request.setMaxReadRequestOperationCount(randomIntBetween(0, Integer.MAX_VALUE));
}
if (randomBoolean()) {
Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

removed, because is a duplicate if statement

Copy link
Member

@dnhatn dnhatn left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM. Thanks @martijnvg for fixing this.

@@ -266,6 +266,8 @@ public void readFrom(final StreamInput in) throws IOException {
maxReadRequestOperationCount = in.readOptionalVInt();
maxOutstandingReadRequests = in.readOptionalVInt();
maxReadRequestSize = in.readOptionalWriteable(ByteSizeValue::new);
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Would you mind moving maxReadRequestSize above maxOutstandingReadRequests so that we have the same order for both read and write.

@martijnvg martijnvg merged commit bad5972 into elastic:master Oct 29, 2018
martijnvg added a commit that referenced this pull request Oct 29, 2018
and some parameters that were not set in tests.
martijnvg added a commit that referenced this pull request Oct 29, 2018
and some parameters that were not set in tests.
kcm pushed a commit that referenced this pull request Oct 30, 2018
and some parameters that were not set in tests.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
:Distributed Indexing/CCR Issues around the Cross Cluster State Replication features >non-issue
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants