Skip to content

Conversation

@133tosakarin
Copy link
Contributor

What changes were proposed in this pull request?

For the readIndexRequestProto, we don't need to set message member
In readIndex, we did not use clientRequest.message, so we do not need to serialize the message

What is the link to the Apache JIRA

https://issues.apache.org/jira/browse/RATIS-2165

return toRaftClientRequestProto(request, true);
}

static RaftClientRequestProto toRaftClientRequestProto(RaftClientRequest request, boolean with_msg) {
Copy link
Contributor

Choose a reason for hiding this comment

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

do not use with_msg, at least it should be withMsg

@133tosakarin
Copy link
Contributor Author

@szetszwo

These failed tests seem to meet expectations

Copy link
Contributor

@szetszwo szetszwo left a comment

Choose a reason for hiding this comment

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

+1 the change looks good.

@szetszwo szetszwo changed the title RATIS-2165. Discussion on canceling transmission of RaftClientRequest. Message in RaftServerImpl.sendReadIndexAsync to further optimize transmission efficiency RATIS-2165. Do not include RaftClientRequest Message in ReadIndexRequest Oct 9, 2024
@szetszwo
Copy link
Contributor

szetszwo commented Oct 9, 2024

These failed tests seem to meet expectations

@133tosakarin , you are right that the failures does not seem related; see #1156 . Let's merge this without further retries.

@szetszwo szetszwo merged commit de4e24d into apache:master Oct 9, 2024
szetszwo pushed a commit to szetszwo/ratis that referenced this pull request May 23, 2025
szetszwo pushed a commit to szetszwo/ratis that referenced this pull request May 23, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants