You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@pulsar.apache.org by GitBox <gi...@apache.org> on 2020/05/28 16:06:50 UTC
[GitHub] [pulsar] oneum72 commented on issue #7047: proxy errors using docker-compose
oneum72 commented on issue #7047:
URL: https://github.com/apache/pulsar/issues/7047#issuecomment-635442506
@sijie I have tested as you suggested and there is only one error:
```
15:34:08.471 [main-EventThread] WARN org.apache.pulsar.proxy.server.util.ZookeeperCacheLoader - Error updating broker info after broker list changed.
java.util.concurrent.TimeoutException: null
at java.util.concurrent.CompletableFuture.timedGet(CompletableFuture.java:1784) ~[?:1.8.0_252]
at java.util.concurrent.CompletableFuture.get(CompletableFuture.java:1928) ~[?:1.8.0_252]
at org.apache.pulsar.zookeeper.ZooKeeperDataCache.get(ZooKeeperDataCache.java:97) ~[org.apache.pulsar-pulsar-zookeeper-utils-2.5.2.jar:2.5.2]
at org.apache.pulsar.proxy.server.util.ZookeeperCacheLoader.updateBrokerList(ZookeeperCacheLoader.java:118) ~[org.apache.pulsar-pulsar-proxy-2.5.2.jar:2.5.2]
at org.apache.pulsar.proxy.server.util.ZookeeperCacheLoader.lambda$new$0(ZookeeperCacheLoader.java:82) ~[org.apache.pulsar-pulsar-proxy-2.5.2.jar:2.5.2]
at org.apache.pulsar.zookeeper.ZooKeeperChildrenCache.lambda$0(ZooKeeperChildrenCache.java:85) ~[org.apache.pulsar-pulsar-zookeeper-utils-2.5.2.jar:2.5.2]
at java.util.concurrent.CompletableFuture.uniAccept(CompletableFuture.java:670) ~[?:1.8.0_252]
at java.util.concurrent.CompletableFuture$UniAccept.tryFire(CompletableFuture.java:646) ~[?:1.8.0_252]
at java.util.concurrent.CompletableFuture.postComplete(CompletableFuture.java:488) ~[?:1.8.0_252]
at java.util.concurrent.CompletableFuture.complete(CompletableFuture.java:1975) ~[?:1.8.0_252]
at org.apache.pulsar.zookeeper.ZooKeeperCache.lambda$22(ZooKeeperCache.java:428) ~[org.apache.pulsar-pulsar-zookeeper-utils-2.5.2.jar:2.5.2]
at org.apache.zookeeper.ClientCnxn$EventThread.processEvent(ClientCnxn.java:618) [org.apache.pulsar-pulsar-zookeeper-2.5.2.jar:2.5.2]
at org.apache.zookeeper.ClientCnxn$EventThread.run(ClientCnxn.java:510) [org.apache.pulsar-pulsar-zookeeper-2.5.2.jar:2.5.2]
15:34:08.533 [main-EventThread] INFO org.apache.pulsar.zookeeper.ZooKeeperDataCache - [State:CONNECTED Timeout:30000 sessionid:0x100001abf490011 local:/172.20.0.8:42954 remoteserver:lzk1/172.20.0.2:2181 lastZxid:111 xid:6 sent:9 recv:12 queuedpkts:0 pendingresp:0 queuedevents:0] Received ZooKeeper watch event: WatchedEvent state:SyncConnected type:NodeDataChanged path:/loadbalance/brokers/apache-pulsar:8080
15:48:48.507 [main-EventThread] INFO org.apache.pulsar.zookeeper.ZooKeeperDataCache - [State:CONNECTED Timeout:30000 sessionid:0x100001abf490011 local:/172.20.0.8:42954 remoteserver:lzk1/172.20.0.2:2181 lastZxid:117 xid:7 sent:98 recv:101 queuedpkts:0 pendingresp:0 queuedevents:0] Received ZooKeeper watch event: WatchedEvent state:SyncConnected type:NodeDataChanged path:/loadbalance/brokers/apache-pulsar:8080
[spesa@localhost simple]$
```
Now this behavior raised questions:
1. How come the pulsar-admin interfere with proxy:v2.5.2. in the first place, even before configuring proxy environment?
2. Why the pulsar:v2.4.1. does not log errors while used with pulsar-admin?
3. Every successive version of pulsar throws errors if used with pulsar-admin and pulsar-admin is not operational with???
In other words pulsar-admin does not work if used with proxy version >pulsar:v2.4.1.
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
users@infra.apache.org