You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@pulsar.apache.org by wa...@apache.org on 2022/01/31 20:13:44 UTC
[pulsar] branch dave2wave-proxy-documentation created (now e4061d1)
This is an automated email from the ASF dual-hosted git repository.
wave pushed a change to branch dave2wave-proxy-documentation
in repository https://gitbox.apache.org/repos/asf/pulsar.git.
at e4061d1 Update Proxy Configuration write up.
This branch includes the following new commits:
new e4061d1 Update Proxy Configuration write up.
The 1 revisions listed above as "new" are entirely new to this
repository and will be described in separate emails. The revisions
listed as "add" were already present in the repository and have only
been added to this reference.
[pulsar] 01/01: Update Proxy Configuration write up.
Posted by wa...@apache.org.
This is an automated email from the ASF dual-hosted git repository.
wave pushed a commit to branch dave2wave-proxy-documentation
in repository https://gitbox.apache.org/repos/asf/pulsar.git
commit e4061d1e7996eff082d3bc2c87b260bc61273da1
Author: Dave Fisher <da...@comcast.net>
AuthorDate: Mon Jan 31 12:10:18 2022 -0800
Update Proxy Configuration write up.
---
site2/docs/administration-proxy.md | 26 ++++++++++++++------------
1 file changed, 14 insertions(+), 12 deletions(-)
diff --git a/site2/docs/administration-proxy.md b/site2/docs/administration-proxy.md
index 9d99c5f..f9ead9a 100644
--- a/site2/docs/administration-proxy.md
+++ b/site2/docs/administration-proxy.md
@@ -8,19 +8,9 @@ Pulsar proxy is an optional gateway. Pulsar proxy is used when direct connection
## Configure the proxy
-Before using the proxy, you need to configure it with the brokers addresses in the cluster. You can configure the proxy to connect directly to service discovery, or specify a broker URL in the configuration.
+Before using the proxy, you need to configure it with the brokers addresses in the cluster. You can configure the broker URL in the proxy configuration, or the proxy to connect directly using service discovery.
-### Use service discovery
-
-Pulsar uses [ZooKeeper](https://zookeeper.apache.org) for service discovery. To connect the proxy to ZooKeeper, specify the following in `conf/proxy.conf`.
-```properties
-zookeeperServers=zk-0,zk-1,zk-2
-configurationStoreServers=zk-0:2184,zk-remote:2184
-```
-
-> To use service discovery, you need to open the network ACLs, so the proxy can connects to the ZooKeeper nodes through the ZooKeeper client port (port `2181`) and the configuration store client port (port `2184`).
-
-> However, it is not secure to use service discovery. Because if the network ACL is open, when someone compromises a proxy, they have full access to ZooKeeper.
+> In a production environment service discovery is not recommended.
### Use broker URLs
@@ -49,6 +39,18 @@ The ports to connect to the brokers (6650 and 8080, or in the case of TLS, 6651
Note that if you do not use functions, you do not need to configure `functionWorkerWebServiceURL`.
+### Use service discovery
+
+Pulsar uses [ZooKeeper](https://zookeeper.apache.org) for service discovery. To connect the proxy to ZooKeeper, specify the following in `conf/proxy.conf`.
+```properties
+zookeeperServers=zk-0,zk-1,zk-2
+configurationStoreServers=zk-0:2184,zk-remote:2184
+```
+
+> To use service discovery, you need to open the network ACLs, so the proxy can connects to the ZooKeeper nodes through the ZooKeeper client port (port `2181`) and the configuration store client port (port `2184`).
+
+> However, it is not secure to use service discovery. Because if the network ACL is open, when someone compromises a proxy, they have full access to ZooKeeper.
+
## Start the proxy
To start the proxy: