[
https://issues.apache.org/jira/browse/RATIS-2265?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17941070#comment-17941070
]
Tsz-wo Sze commented on RATIS-2265:
-----------------------------------
{quote}Asking them about the ETA:
[https://github.com/grpc/grpc-java/pull/11912#issuecomment-2749019292]
{quote}
Unfortunately, we have not got any responses from the gRPC community.
[~tanxinyu], [~adoroszlai], Before getting a good gRPC release, I suggest
having a new Ratis-thirdparty release (say 1.0.9) to have grpc 1.71.0 and netty
4.1.110.Final. Then, the projects using Ratis could choose which thirdparty
version they want by maven dependency inclusion-exclusion. For examples,
- Ozone dependency: Ratis 3.1.3 with exclusion Ratis-thirdparty 1.0.8, and
Ratis-thirdparty 1.0.9
- IoTDB dependency: Ratis 3.1.3
What do you think?
> Thirdparty should use the netty version recommended by gRPC
> -----------------------------------------------------------
>
> Key: RATIS-2265
> URL: https://issues.apache.org/jira/browse/RATIS-2265
> Project: Ratis
> Issue Type: Improvement
> Components: thirdparty
> Reporter: Tsz-wo Sze
> Assignee: Tsz-wo Sze
> Priority: Major
> Time Spent: 20m
> Remaining Estimate: 0h
>
> The mysterious problem reported by HDDS-12103 could be caused by the
> underlying libraries. In this JIRA, we try changing the grpc, netty, protobuf
> versions.
> We should use the netty version recommended by gRPC
> - https://github.com/grpc/grpc-java/blob/master/SECURITY.md#netty
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
