Uploaded image for project: 'Couchbase Kafka Connector'
  1. Couchbase Kafka Connector
  2. KAFKAC-333

ConcurrentModificationException in the Source Kafka Connector

    XMLWordPrintable

Details

    • Bug
    • Resolution: Fixed
    • Major
    • 4.2.1
    • 4.2.0
    • None
    • 0

    Description

      We are seeing the following error in our connector " 

       

      java.util.ConcurrentModificationException at java.base/java.util.HashMap.computeIfAbsent(HashMap.java:1135) at com.couchbase.client.core.cnc.LoggingEventConsumer.accept(LoggingEventConsumer.java:75) at com.couchbase.client.dcp.core.utils.MinimalEventBus.publish(MinimalEventBus.java:41) at com.couchbase.client.core.util.ConnectionStringUtil.seedNodesFromConnectionString(ConnectionStringUtil.java:99) at com.couchbase.client.dcp.Client$Environment.clusterAt(Client.java:1706) at com.couchbase.client.dcp.Client$Environment.<init>(Client.java:1680) at com.couchbase.client.dcp.Client$Environment.<init>(Client.java:1584) at com.couchbase.client.dcp.Client.<init>(Client.java:178) at com.couchbase.client.dcp.Client.<init>(Client.java:135) at com.couchbase.client.dcp.Client$Builder.build(Client.java:1537) at com.couchbase.connect.kafka.CouchbaseReader.<init>(CouchbaseReader.java:144) at com.couchbase.connect.kafka.CouchbaseSourceTask.start(CouchbaseSourceTask.java:156) at org.apache.kafka.connect.runtime.AbstractWorkerSourceTask.initializeAndStart(AbstractWorkerSourceTask.java:273) at org.apache.kafka.connect.runtime.WorkerTask.doRun(WorkerTask.java:199) at org.apache.kafka.connect.runtime.WorkerTask.run(WorkerTask.java:256) at org.apache.kafka.connect.runtime.AbstractWorkerSourceTask.run(AbstractWorkerSourceTask.java:75) at java.base/java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:515) at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264) at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128) at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628) at java.base/java.lang.Thread.run(Thread.java:829)

      I understand that the stacktrace on its own is not that useful but sadly we do not know how to reproduce it. What we do know whoever is that when it happens it kills the task until recovered manually 

       

       

       

      Attachments

        Issue Links

          No reviews matched the request. Check your Options in the drop-down menu of this sections header.

          Activity

            People

              david.nault David Nault
              yeikel Yeikel Santana
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved:

                Gerrit Reviews

                  There are no open Gerrit changes

                  PagerDuty