To fix the problem we need to identify which JAR file contains io.grpc.netty.shaded.io.netty.util.collection.IntObjectHashMap. Can you check which version of which artifact (I suspect io.grpc:grpc-netty) has the class in your runtime?
As far as I know, Beam's vendored (shaded) class files have the package name "org.apache.beam.vendor" prefix. On Thu, Oct 1, 2020 at 3:48 AM Kaymak, Tobias <tobias.kay...@ricardo.ch> wrote: > Hello, > > when deploying a Beam streaming pipeline on Flink and canceling it after > some time, the following can be seen in the logs: > > 2020-10-01 07:36:47,605 WARN > io.grpc.netty.shaded.io.netty.channel.epoll.EpollEventLoop - Unexpected > exception in the selector loop. > flink-taskmanager-7695c66775-xtz4l taskmanager > java.lang.NoClassDefFoundError: > io/grpc/netty/shaded/io/netty/util/collection/IntObjectHashMap$2 > flink-taskmanager-7695c66775-xtz4l taskmanager at > io.grpc.netty.shaded.io.netty.util.collection.IntObjectHashMap.values(IntObjectHashMap.java:221) > flink-taskmanager-7695c66775-xtz4l taskmanager at > io.grpc.netty.shaded.io.netty.channel.epoll.EpollEventLoop.closeAll(EpollEventLoop.java:436) > flink-taskmanager-7695c66775-xtz4l taskmanager at > io.grpc.netty.shaded.io.netty.channel.epoll.EpollEventLoop.run(EpollEventLoop.java:401) > flink-taskmanager-7695c66775-xtz4l taskmanager at > io.grpc.netty.shaded.io.netty.util.concurrent.SingleThreadEventExecutor$6.run(SingleThreadEventExecutor.java:1044) > flink-taskmanager-7695c66775-xtz4l taskmanager at > io.grpc.netty.shaded.io.netty.util.internal.ThreadExecutorMap$2.run(ThreadExecutorMap.java:74) > flink-taskmanager-7695c66775-xtz4l taskmanager at > io.grpc.netty.shaded.io.netty.util.concurrent.FastThreadLocalRunnable.run(FastThreadLocalRunnable.java:30) > flink-taskmanager-7695c66775-xtz4l taskmanager at > java.lang.Thread.run(Thread.java:748) > > A mvn dependency:tree reveals that > > org.apache.beam:beam-sdks-java-io-google-cloud-platform > > and the Flink runner itself defines netty, where Flink uses a shaded one - > if I get this right. > > What is the best way to fix this? > -- Regards, Tomo
