[BUG] About zookeeper - Githubissues

apache / hertzbeat

Apache HertzBeat(incubating) is a real-time monitoring system with agentless, performance cluster, prometheus-compatible, custom monitoring and status page building capabilities.

https://hertzbeat.apache.org/

Apache License 2.0

5.65k stars 979 forks source link

[BUG] About zookeeper #1693

Open ZachariahHu opened 7 months ago

ZachariahHu commented 7 months ago

Is there an existing issue for this?

[X] I have searched the existing issues

Current Behavior

Expected Behavior

No response

Steps To Reproduce

No response

Environment

HertzBeat version(s):

Debug logs

No response

Anything else?

No response

tomsun28 commented 7 months ago

can you provide more running log? and the zookeeper version, hertzbeat version, the way you run.

ZachariahHu commented 7 months ago

zookeeper: 3.4.14 hertzbeat: 1.5.0

wang1027-wqh commented 7 months ago

It seems to be caused by the timeout. I also encountered this situation when I connected zk before. I set the timeout time of the zk client to 100s, but it was only 40s when it expired. zk will also adjust the min session timeout and max session timeout parameters to obtain the final timeout value. By default, the two values are 2 times and 20 times of tick time respectively, and the default value of tick time is 3s, that is, the last effective timeout period is 6s < timeout < 60. If the timeout is within 40s, the tick time may be set to 2s. You can check the configuration and the execution time after launching the test connection, and make a comparison, hoping to help you

ZachariahHu commented 7 months ago

It seems to be caused by the timeout. I also encountered this situation when I connected zk before. I set the timeout time of the zk client to 100s, but it was only 40s when it expired. zk will also adjust the min session timeout and max session timeout parameters to obtain the final timeout value. By default, the two values are 2 times and 20 times of tick time respectively, and the default value of tick time is 3s, that is, the last effective timeout period is 6s < timeout < 60. If the timeout is within 40s, the tick time may be set to 2s. You can check the configuration and the execution time after launching the test connection, and make a comparison, hoping to help you

The zookeeper configuration. Can you tell me what configuration needs to be added ? ty.

leim commented 6 months ago

same situation, everything is default.

tancloud/hertzbeat:v1.5.0 bitnami/zookeeper:3.6.2

z23

z24