Gustascern opened a new issue, #18383:
URL: https://github.com/apache/pulsar/issues/18383

   ### Search before asking
   
   - [X] I searched in the [issues](https://github.com/apache/pulsar/issues) 
and found nothing similar.
   
   
   ### Version
   
   Pulsar version 2.9.1
   Debian 11
   
   ### Minimal reproduce step
   
   I have a cluster of 6 machines. 3 servers run broker and bookkeeper, 3 run 
zookeeper. Firstly, I configured functions_worker.yml like this on 3 separate 
broker servers. first one looks like this. config is similar in all three 
machines.
   
   workerId: "test"
   workerHostname: "vtst-eims-pbb1.corp.rst.lt"
   workerPort: 6750
   workerPortTls: 6751
   configurationMetadataStoreUrl: 
zk:172.28.80.233:2181,172.28.80.234:2181,172.28.80.235:2181
   
   Then set this parameter in broker.conf and restarted the broker.
   functionsWorkerEnabled=true
   
   
   ### What did you expect to see?
   
   I expected the broker to call the correct zookeeper cluster and display 
correct values.
   
   ### What did you see instead?
   
   But for some reason my worker id is not changing, 
   
{"workerId":"c-pulsartst-fw-vtst-eims-pbb1.corp.rst.lt-8080","workerHostname":"vtst-eims-pbb1.corp.rst.lt","port":8080}
   
   and broker keeps connecting to local zookeeper, which this server doesn't 
have. My config file has no mention of localhost connection, i have no idea why 
it keeps doing that
   Nov 03 14:14:33 vtst-eims-pbb1.corp.rst.lt pulsar[2390139]: 
2022-11-03T14:14:33,903+0200 
[DLM-/pulsar/functions-OrderedScheduler-1-0-SendThread(localhost:2181)] WARN  
org.apache.zookeeper.ClientCnxn - Session 0x0 for sever 
localhost/127.0.0.1:2181, Closing socket connection. Attempting reconnect 
except it is a SessionExpiredException..
   
   ### Anything else?
   
   _No response_
   
   ### Are you willing to submit a PR?
   
   - [X] I'm willing to submit a PR!


-- 
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.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to