Glad to hear that you issue is fixed now!
On 6/2/16, 2:11 PM, "Marco B." wrote:
>Hi Mudit,
>
>Thanks a lot for your answer.
>
>However, today we have set "advertised.host.name" on each kafka instance to
>the specific IP address of each node. For example, by default kafka tries
>to read the ma
Hi Mudit,
Thanks a lot for your answer.
However, today we have set "advertised.host.name" on each kafka instance to
the specific IP address of each node. For example, by default kafka tries
to read the machine's hostname, specifically ip-10-1-83-5.ec2.internal -
now it's "10.1.83.5" (of course, w
I donot think you need public hostname.I have a similarsetup and its perfectly
fine.
What I would suggest you to change the hostname,make it persistent,and use FQDN
everywhere with /etc/hosts entry locally and on AWS machines.Your problem will
get fixed.
On 6/1/16, 8:54 PM, "Marco B." wrote
Hi Ben,
Thanks for your answer. What if the instance does not have a public DNS
hostname?
These are all private nodes without public/elastic IP, therefore I don't
know what to set.
Marco
2016-06-01 15:09 GMT+02:00 Ben Davison :
> Hi Marco,
>
> We use the public DNS hostname that you can get fro
Hi Marco,
We use the public DNS hostname that you can get from the AWS metadata
service.
Thanks,
Ben
On Wed, Jun 1, 2016 at 1:54 PM, Marco B. wrote:
> Hello everyone,
>
> I am trying to setup a MirrorMaker between my company's local cluster and
> another cluster in AWS to have replication ove
Hello everyone,
I am trying to setup a MirrorMaker between my company's local cluster and
another cluster in AWS to have replication over clusters. We have setup a
VPN between these two clusters, and as far as I can see, everything works
correctly, meaning that I can ping the nodes and telnet into
