2018-03-28 16:36:55 UTC - Piotr: Any suggestions on how to best set up an
easily maintainable low cost apache pulsar cluster on AWS for production use?
----
2018-03-28 16:38:37 UTC - Matteo Merli: there are instructions for
terraform+ansible deployment at:
<http://pulsar.apache.org/docs/latest/deployment/aws-cluster/>
----
2018-03-28 16:39:13 UTC - Matteo Merli: these can be adapted to use smaller VMs
as well
----
2018-03-28 16:41:23 UTC - Piotr: would you prefer that over the kubernetes
option (since AWS has its own kubernetes service)?
----
2018-03-28 16:51:31 UTC - Matteo Merli: it’s mostly what you’re already using.
kubernetes in AWS is not yet supported out of the box. EKS is still in preview
as of now
----
2018-03-28 16:52:02 UTC - Karthik Palanivelu: @Karthik Palanivelu uploaded a
file:
<https://apache-pulsar.slack.com/files/U7VRE0Q1G/F9WULRT32/-.txt|Untitled> and
commented: @Matteo Merli This is regarding the Pulsar Geo Replication Test I am
trying using your instructions to pair the standalone. I opened all ports in
Security Group will all permissions. Still I am getting the following error. I
tried http or pulsar option getting the same error. Port 8080 and 8888 are
open. Can you please let me know what I am doing wrong here?
----
2018-03-28 16:55:59 UTC - Piotr: ahh ok, got it thanks
----
2018-03-28 16:57:42 UTC - Matteo Merli: @Karthikeyan Palanivelu the `--url
<pulsar://xx.xx.xx.xx:8080>` you’re passing is what you want to write as the
metadata to store the nominal url for that cluster
----
2018-03-28 16:58:19 UTC - Matteo Merli: (also, you should use port 6650 there:
`<pulsar://xx.xx.xx.xx:6650`>)
----
2018-03-28 16:58:37 UTC - Matteo Merli: the problem is the url that the client
tool itself is using to connect
----
2018-03-28 16:59:02 UTC - Matteo Merli: typically, you configure that in the
`conf/client.conf`
----
2018-03-28 19:02:47 UTC - Karthik Palanivelu: @Matteo Merli I reverted to 6650;
but still I am getting same error. Telnet on this port suggest it is open
between the instances but it is not working for pulsar-admin to create cluster.
Any recommendation? I opened all ports and protocol to test this connectivity,
fyi
----
2018-03-28 19:04:20 UTC - Matteo Merli: did you edit the url in `client.conf` ?
----
2018-03-28 19:04:49 UTC - Karthik Palanivelu: I reverted the ports to 6650 and
8080 for web.
----
2018-03-28 19:04:56 UTC - Karthik Palanivelu: Do I still need to update?
----
2018-03-28 19:05:35 UTC - Matteo Merli: Yes, that URL is what you set in the
metadata, but the admin client needs to connect to broker to do that
:slightly_smiling_face:
----
2018-03-28 19:05:55 UTC - Matteo Merli: for admin client, use the http port on
8080
----
2018-03-28 19:06:06 UTC - Karthik Palanivelu: ok
----
2018-03-28 19:07:01 UTC - Karthik Palanivelu: To clarify it points to localhost
now; should point to the IP address of the same box or the other one?
----
2018-03-28 19:07:17 UTC - Karthik Palanivelu: @Karthik Palanivelu uploaded a
file: <https://apache-pulsar.slack.com/files/U7VRE0Q1G/F9XLRQM99/-.txt|Untitled>
----
2018-03-28 19:11:13 UTC - Matteo Merli: it should point to the address of
broker you want to send the REST request to .
----
2018-03-28 19:12:15 UTC - Matteo Merli: ok, I was just going back the steps I
put into <https://gist.github.com/merlimat/bfdd3c66bfa7387fe6e3bfa3bb263051>
----
2018-03-28 19:12:15 UTC - Matteo Merli: @Matteo Merli shared a file:
<https://apache-pulsar.slack.com/files/U680ZCXA5/F9M31L1PS/StandaloneReplication_md.md|StandaloneReplication.md>
----
2018-03-28 19:13:17 UTC - Matteo Merli: The part:
```
For example, for cluster a we need to let him know where b and c are.
bin/pulsar-admin clusters create b --url pulsar://${IP_B}:6650
bin/pulsar-admin clusters create c --url pulsar://${IP_C}:6650
```
This should configured on cluster `a`
----
2018-03-28 19:14:00 UTC - Matteo Merli: so, if you are on the same VM as the
standalone broker for “cluster a”, then localhost is correct
----
2018-03-28 19:18:02 UTC - Karthik Palanivelu: Localhost did not work for me; I
updated to the box IP and it worked
----
2018-03-28 19:18:25 UTC - Karthik Palanivelu: I have the doc; Thanks for your
time. Now I can move on
----
2018-03-28 19:20:05 UTC - Matteo Merli: Ok, the standalone should bind on all
network interfaces by default. Not sure why that wouldn’t work there :confused:
----
2018-03-28 19:28:57 UTC - Karthik Palanivelu: 6650 is blocked from my dev box;
I need to change that to 8888. Is that ok if I update the client.conf and
standalone.conf to work?
----
2018-03-28 19:29:44 UTC - Matteo Merli: yes
----
2018-03-28 19:30:11 UTC - Matteo Merli: Also set the correct
`pulsar://${IP_B}:8888` for other clusters to connect back
----
2018-03-28 19:30:27 UTC - Karthik Palanivelu: Cool Thanks
----
