Hi David,
On the source connector there is an error which requires a restart of the connector in order to consume the messages again.
This error can be seen on the versions (3.4.7 and 3.4.8)
Error message:
An exceptionCaught() event was fired, and it reached at the tail of the pipeline. It usually means the last handler in the pipeline did not handle the exception. (com.couchbase.client.deps.io.netty.channel.DefaultChannelPipeline:151).
Thanks,
Samir
Hi Samir,
Thanks for letting us know there’s an issue. Can you please provide more information in order to help us diagnose the problem?
It would be helpful to know if the problem happens consistently, and if so, how you reproduce it.
It would also be helpful to see the connector config (with passwords or other sensitive info removed) so we can understand which connector features you’re using.
It might be useful to see a Couchbase Server diagnostic dump captured with the cbcollect_info tool.
Most importantly, it would be very useful to see the full connector log of a session where this error occurs. If you can activate debug logging, that would be even better. (Logging is usually configured in a file called connect-log4j.properties somewhere in your Kafka installation.)
If you are an enterprise customer, please engage with our support team; that will make it easier to track the process and the diagnostic artifacts. Otherwise, feel free to post the requested info here in the forum, and we’ll take a look as time allows.
Thanks,
David