Hi Karthik,
- Is it required to run connector in same network which elastic search runs?
No, as long as Elasticsearch is publicly accessible. The challenge is in talking to Couchbase from a different network.
- What does the provided error message infer?
Couchbase needs special configuration if you want to access it from another network. See About Alternate Addresses and Configuring Alternate Addresses using the REST API.
If you’re using Couchbase Capella, or deploying the Couchbase Operator in Kubernetes, this configuration happens automatically. But if you’re deploying by hand, it’s necessary to configure the alternate address settings yourself.
You’d want to configure it so that Couchbase Server advertises the external hostname and port for each service, in addition to the local hostname and port. Then you tell your client (the connector, in this case) to connect to the external hostname, using the port that’s mapped to the KV service.
Or… you could just run the connector in the same network as Couchbase, which is probably how you’d want to do things in a production environment anyway.
Thanks,
David