LEAK: HashedWheelTimer.release() Error seen in Connect Log

[shamanthchandra-yb]

Connector I tried: quay.io/vaibhav_yb/test_repo:1.9.5.y.2.1

2022-11-10 13:17:18,158 ERROR  YugabyteDB|db_cdc|snapshot  LEAK: HashedWheelTimer.release() was not called before it's garbage-collected. See https://netty.io/wiki/reference-counted-objects.html for more information.
Recent access records:
Created at:
        io.netty.util.HashedWheelTimer.<init>(HashedWheelTimer.java:312)
        io.netty.util.HashedWheelTimer.<init>(HashedWheelTimer.java:251)
        io.netty.util.HashedWheelTimer.<init>(HashedWheelTimer.java:224)
        io.netty.util.HashedWheelTimer.<init>(HashedWheelTimer.java:203)
        io.netty.util.HashedWheelTimer.<init>(HashedWheelTimer.java:185)
        io.netty.util.HashedWheelTimer.<init>(HashedWheelTimer.java:142)
        org.yb.client.AsyncYBClient.<init>(AsyncYBClient.java:266)
        org.yb.client.AsyncYBClient.<init>(AsyncYBClient.java:182)
        org.yb.client.AsyncYBClient$AsyncYBClientBuilder.build(AsyncYBClient.java:3369)
        io.debezium.connector.yugabytedb.YugabyteDBStreamingChangeEventSource.<init>(YugabyteDBStreamingChangeEventSource.java:113)
        io.debezium.connector.yugabytedb.YugabyteDBChangeEventSourceFactory.getStreamingChangeEventSource(YugabyteDBChangeEventSourceFactory.java:85)
        io.debezium.pipeline.ChangeEventSourceCoordinator.initStreamEvents(ChangeEventSourceCoordinator.java:179)
        io.debezium.connector.yugabytedb.YugabyteDBChangeEventSourceCoordinator.executeChangeEventSources(YugabyteDBChangeEventSourceCoordinator.java:115)
        io.debezium.pipeline.ChangeEventSourceCoordinator.lambda$start$0(ChangeEventSourceCoordinator.java:109)
        java.base/java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:515)
        java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264)
        java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128)
        java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628)
        java.base/java.lang.Thread.run(Thread.java:829)   [io.netty.util.ResourceLeakDetector]
2022-11-10 13:17:18,160 ERROR  YugabyteDB|db_cdc|snapshot  LEAK: HashedWheelTimer.release() was not called before it's garbage-collected. See https://netty.io/wiki/reference-counted-objects.html for more information.
Recent access records:
Created at:
        io.netty.util.HashedWheelTimer.<init>(HashedWheelTimer.java:312)
        io.netty.util.HashedWheelTimer.<init>(HashedWheelTimer.java:251)
        io.netty.util.HashedWheelTimer.<init>(HashedWheelTimer.java:224)
        io.netty.util.HashedWheelTimer.<init>(HashedWheelTimer.java:203)
        io.netty.util.HashedWheelTimer.<init>(HashedWheelTimer.java:185)
        io.netty.util.HashedWheelTimer.<init>(HashedWheelTimer.java:142)
        org.yb.client.AsyncYBClient.<init>(AsyncYBClient.java:266)
        org.yb.client.AsyncYBClient.<init>(AsyncYBClient.java:182)
        org.yb.client.AsyncYBClient$AsyncYBClientBuilder.build(AsyncYBClient.java:3369)
        io.debezium.connector.yugabytedb.YugabyteDBSnapshotChangeEventSource.<init>(YugabyteDBSnapshotChangeEventSource.java:93)
        io.debezium.connector.yugabytedb.YugabyteDBChangeEventSourceFactory.getSnapshotChangeEventSource(YugabyteDBChangeEventSourceFactory.java:72)
        io.debezium.pipeline.ChangeEventSourceCoordinator.lambda$start$0(ChangeEventSourceCoordinator.java:108)
        java.base/java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:515)
        java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264)
        java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128)
        java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628)
        java.base/java.lang.Thread.run(Thread.java:829)   [io.netty.util.ResourceLeakDetector]

[vaibhav-yb]

This log is just a warning which pops up when we garbage collect the YBClient object in Java created as a part of the whole connector workflow when the object is still active, this happens during a very small window while transitioning from snapshot-mode to streaming-mode or upon connector restarts.