Upgrade Netty to 4.1.119, tcnative to 2.0.70 and io_uring to 0.0.26

[lhotari]

Motivation

• Keeping Netty version up-to-date.
• Address CVE-2025-24970

Changes

• Upgrade Netty to 4.1.119.Final
  • Comes with tcnative 2.0.70.Final
• Upgrade netty-transport-native-io_uring to 0.0.26.Final

[nodece]

BookKeeper CI / Replication Tests (pull_request) CI always fails, because the DNS resolve time is too long, which leads to the test timeout.

[lhotari]

BookKeeper CI / Replication Tests (pull_request) CI always fails, because the DNS resolve time is too long, which leads to the test timeout.

@nodece interesting. In a different context, a reporter in this Pulsar GH discussion was saying that something changed in Netty DNS resolution in the upgrade.

[nodece]

@lhotari The bk did not use the netty dns resolver, I will use the netty dns resolver instead of the java built-in dns resolver, please see #4585

[lhotari]

@lhotari The bk did not use the netty dns resolver, I will use the netty dns resolver instead of the java built-in dns resolver, please see #4585

@nodece Although there are benefits in using Netty's DNS resolver, I wonder if this test flakiness is simply due to default DNS caching settings in Java.

[nodece]

In the local network environment, the DNS resolution process takes as long as 15 seconds, it seems that the Java did not cache the DNS info.

[lhotari]

commented at #4585 (comment)

[lhotari]

In the local network environment, the DNS resolution process takes as long as 15 seconds.

That's possibly due to the default negative DNS cache setting of 10 seconds. Have you tested with these changes: #4585 (comment) .

[nodece]

I will test that with your suggestion tomorrow.

[lhotari]

@nodece I created #4586 to tune the DNS TTL settings for tests and for CI

[StevenLuMT]

Great jobs