This is quite a headache in the context of using the alluxio-shaded-client with other libraries which pull netty-tcnative-boringssl-static (e.g. : azure-core).
Now as you may know, in the shading process for alluxio-shaded-client, the library libnetty_tcnative_linux_x86_64.so remains untouched. This can cause peculiar JVM crashes at runtime when azure-core is trying to load this native library because it can grab the library belonging to alluxio-shaded-client.
I'm very happy also with a workaround proposal if possible.
This issue has been automatically marked as stale because it has not had recent activity. It will be closed in two weeks if no further activity occurs. Thank you for your contributions.
Summary
Looking at the https://github.com/Alluxio/alluxio/blob/release-2.7.4/core/common/pom.xml#L115-L119 can be seen that the version for
netty-tcnative-boringssl-static
is from 2019.Urgency
This is quite a headache in the context of using the
alluxio-shaded-client
with other libraries which pullnetty-tcnative-boringssl-static
(e.g. :azure-core
).Now as you may know, in the shading process for
alluxio-shaded-client
, the librarylibnetty_tcnative_linux_x86_64.so
remains untouched. This can cause peculiar JVM crashes at runtime whenazure-core
is trying to load this native library because it can grab the library belonging toalluxio-shaded-client
.I'm very happy also with a workaround proposal if possible.