Re: Flink Elastic Sink AWS ES

It seems AWS ES setup is hiding the nodes ip. Then I think you can try @vinay patil's solution. Thanks, Arpit On Tue, Aug 29, 2017 at 3:56 AM, ant burton wrote: > Hey Arpit, > > _cat/nodes?v=ip,port > > > returns the following which I have not added the x’s they were

Re: Flink Elastic Sink AWS ES

Hey Arpit, > _cat/nodes?v=ip,port returns the following which I have not added the x’s they were returned on the response ipport x.x.x.x 9300 Thanks your for you help Anthony > On 28 Aug 2017, at 10:34, arpit srivastava wrote: > > Hi Ant, > > Can you try

Re: Flink Elastic Sink AWS ES

Hi Ant, Can you try this. curl -XGET 'http:///_cat/nodes?v=ip,port' This should give you ip and port On Mon, Aug 28, 2017 at 3:42 AM, ant burton wrote: > Hi Arpit, > > The response fromm _nodes doesn’t contain an ip address in my case. Is > this something that you

Re: Flink Elastic Sink AWS ES

Hi Arpit, The response fromm _nodes doesn’t contain an ip address in my case. Is this something that you experienced? > curl -XGET 'http:///_nodes' Thanks, > On 27 Aug 2017, at 14:32, ant burton wrote: > > Thanks! I'll check later this evening. > > On Sun, 27 Aug

Re: Flink Elastic Sink AWS ES

ES. >>>> >>>> I don’t believe this is possible as AWS ES only allows access to port >>>> 9200 (via port 80) on the master node of the ES cluster, and not port 9300 >>>> used by the the Flink Elasticsearch connector. >>>> >>>> The error message that occurs when attem

Re: Flink Elastic Sink AWS ES

We also had same setup where ES cluster was behind a proxy server for which port 80 was used which redirected it to ES cluster 9200 port. For using Flink we got the actual ip address of the ES nodes and put that in ips below. transportAddresses.add(new

Re: Flink Elastic Sink AWS ES

Hi Ted, Changing the port from 9300 to 9200 in the example you provides causes the error in the my original message my apologies for not providing context in the form of code in my original message, to confirm I am using the example you provided in my application and have it working using

Re: Flink Elastic Sink AWS ES

If port 9300 in the following example is replaced by 9200, would that work ? https://ci.apache.org/projects/flink/flink-docs-release-1.3/dev/connectors/elasticsearch.html Please use Flink 1.3.1+ On Sat, Aug 26, 2017 at 3:00 PM, ant burton wrote: > Hello, > > Has anybody

Flink Elastic Sink AWS ES

Hello, Has anybody been able to use the Flink Elasticsearch connector to sink data to AWS ES. I don’t believe this is possible as AWS ES only allows access to port 9200 (via port 80) on the master node of the ES cluster, and not port 9300 used by the the Flink Elasticsearch connector. The