Closed oneum72 closed 1 year ago
@oneum72 it seems that your problem is similar to apache/pulsar#6141 which is related to apache/pulsar-manager#252. I think pulsar-manager is sending some HTTP requests that are not able to be recognized by the pulsar proxy. Can you first try to disable pulsar-manager in your docker-compose file?
@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
Now this behavior raised questions:
In other words pulsar-manager:v0.1.0 does not work if used with proxy version >pulsar-proxy:v2.4.1 as environment !!!
What does pulsar-admin
interface mean here? Do you mean pulsar-admin
CLI tool or pulsar-manager?
What does
pulsar-admin
interface mean here? Do you meanpulsar-admin
CLI tool or pulsar-manager?
Edited the previous repy!
@oneum72 I don't think the problem is pulsar-manager.
I have tested as you suggested and there is only one error:
What did you change? I don't have any context about what you have changed to answer your question.
@oneum72 Can you first try to disable pulsar-manager in your docker-compose file?
So I did tried the initial docker-compose with pulsar-proxy:v2.5.2 and disabled pulsar-manager as you suggested and found out the following as already described above. I can provide additional info if required.
Closed as stale. Please open a new issue if it's still relevant to the maintained versions.
Within docker-compose, using the pulsar:2.4.1 image everything is ok and proxy is running ok... docker-compose.yml: But using the the same docker-compose.yml structure and only change pulsar image to newer version, any of >2.4.1 i.e. pulsar:2.5.2 the pulsar-proxy log is full of errors:
cut from pulsar-proxy (pulsar:2.5.2) log:
and that error repeats over and over again, this is not expected behaviour isn't it? Any Hints?