HBASE-30382: Update zstd-jni to 1.5.7-15 (branch-2) - #8657
arvindKandpal-ksolves wants to merge 1 commit into
Conversation
|
Hi @arvindKandpal-ksolves, |
|
Verified locally on branch-2 across all 3 failing JDK/Hadoop CI jobs. JDK17/Hadoop3 (large-wave-3): JDK11/Hadoop3 (large-wave-1): JDK8/Hadoop2 (large-wave-1): TestFromClientSide3, TestFromClientSide3WithCoprocessor, TestFlushSnapshotFromClient, TestClientScannerTimeouts — all pass. TestCanaryTool#testWebUI fails with "Could not get Canary status page." Same failure seen on branch-2.6 — confirmed there at the code level: no reference to zstd/compress anywhere in TestCanaryTool.java or CanaryTool.java. It's a pure HTTP fetch/retry against an embedded Jetty status server, and CI itself already classifies this as "Flakes" (intermittent, not deterministic). |
|
Hi @PDavid, I have tested all the failed tests on all branches, and for the tests that failed locally, I reverted my changes and reproduced the same failure without my fix. So I believe these failures are not related to our changes. I have commented my run outputs in each PR , could you please check and verify? |
What changes were proposed in this pull request?
Bumps zstd-jni from 1.5.7-2 to 1.5.7-15 in pom.xml (branch-2).
Why are the changes needed?
zstd-jni versions prior to 1.5.7-14 contain vulnerable code addressed by:
Does this PR introduce any user-facing change?
No.
How was this patch tested?
Ran the full zstd-jni compression test suite before and after the bump:
TestWALCompressionZstd, TestZstdCodec, TestHFileCompressionZstd,
TestZstdDictionary, TestZstdDictionarySplitMerge, TestZstdByteBuffDecompressor.
Baseline (1.5.7-2): 15 tests run, 0 failures, 0 errors
After bump (1.5.7-15): 15 tests run, 0 failures, 0 errors
Verified via
mvn dependency:treethat the resolved artifact iscom.github.luben:zstd-jni:jar:1.5.7-15.
Note: built with
-Dhadoop.profile=3.0(required for JDK11+).