Currently we are using native Couchbase-elastic connector application version 4.3.6 to sync data between Couchbase cluster and elastic search.We are not overriding anything and only providing the Couchbase and elastic search connection informations in .toml file.
Recently we saw an issue where there is some connectivity issue between Couchbase instance and this connector application when we restart the pods , the application is neither generating any error logs nor are our pods changing stage from green to red.
Looked at the couchbase-elasticsearch-connector jar, when there is some exception in the main method, the finally block is suppressing the exceptions and we are not able to get any exception out.
Can you please help us what is the issue here and also are there any configs available which we can make use of to get the logs incase of connection failure.
Recently we saw an issue where there is some connectivity issue between Couchbase instance and this connector application when we restart the pods , the application is neither generating any error logs nor are our pods changing stage from green to red.
Is the connector generating any log output? If so, can you share it?
If there’s not enough information in the logs to understand what’s happening, you could try enabling debug logging for the Elasticsearch connector. If you want to do that, edit config/log4j2.xml and replace
Which pods are you starting? All of them? Just Couchbase? Just the connector?
Out of curiosity, how are you deploying the connector? (for example, are you using the native Kubernetes integration, or coordinating with Consul, or just running each connector worker as an independent process/pod?)
I would also try upgrading to the latest version of the connector to see if that helps.