[
https://issues.apache.org/jira/browse/RATIS-2590?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18094517#comment-18094517
]
Haonan Hou commented on RATIS-2590:
-----------------------------------
Hi, after a deeper investigation, I found something interesting: these two
macOS-specific Netty native artifacts do not appear to be used by Ratis today.
{{NettyUtils}} only selects Epoll when available and otherwise falls back to
NIO, with no KQueue branch; gRPC name resolution uses {{DnsNameResolver}} with
JDK {{{}InetAddress.getAllByName{}}}, and the non-gRPC Netty path also resolves
addresses through {{NetUtils.createSocketAddr()}} /
{{{}InetAddress.getByName{}}}, so the native macOS DNS resolver is not on the
default runtime path.
> Add Netty macOS aarch64 native dependencies for Apple Silicon support
> ---------------------------------------------------------------------
>
> Key: RATIS-2590
> URL: https://issues.apache.org/jira/browse/RATIS-2590
> Project: Ratis
> Issue Type: Improvement
> Components: thirdparty
> Reporter: Haonan Hou
> Assignee: Haonan Hou
> Priority: Minor
> Fix For: thirdparty-1.1.0, thirdparty-2.0.0
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> ratis-thirdparty/misc/pom.xml currently packages the macOS aarch64 native
> library from {{{}netty-tcnative-boringssl-static{}}}. However,
> {{netty-resolver-dns-native-macos}} and {{netty-transport-native-kqueue}} are
> only configured with the {{osx-x86_64}} classifier and do not include
> {{{}osx-aarch_64{}}}.
> As a result, on Apple Silicon Macs, Netty cannot use the native macOS DNS
> resolver or kqueue transport and may fall back to non-native implementations.
> This has limited impact on Linux deployments, but it affects native transport
> completeness on macOS aarch64, DNS behavior, and potentially I/O performance
> in high-load scenarios.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
