XuanYang-cn opened a new issue #13852:
URL: https://github.com/apache/pulsar/issues/13852
**Describe the bug**
A clear and concise description of what the bug is.
**To Reproduce**
Steps to reproduce the behavior:
1. Go to '...'
2. Click on '....'
3. Scroll down to '....'
4. See error
**Expected behavior**
A clear and concise description of what you expected to happen.
**Screenshots**
If applicable, add screenshots to help explain your problem.
**Desktop (please complete the following information):**
- OS: [e.g. iOS]
**Additional context**
Add any other context about the problem here.
```
5169 18:57:44.834 [Thread-178] INFO
org.apache.pulsar.broker.service.ServerCnx - [/10.244.0.61:52130] Created new
producer:
Producer{topic=PersistentTopic{topic=persistent://public/default/by-dev-rootcoord-dml_45},
client=/10.244.0.61:52130, producerName=test-pulsar-pod -kill-3-25,
producerId=25}
5170 18:57:48.642 [pulsar-load-manager-1-1] INFO
org.apache.pulsar.broker.loadbalance.impl.ModularLoadManagerImpl - Writing
local data to ZooKeeper because maximum change 33235.83459104782% exceeded
threshold 10%; time since last report written is 15.0 seconds
5171 18:57:48.649 [pulsar-ordered-OrderedExecutor-4-0-EventThread] INFO
org.apache.pulsar.zookeeper.ZooKeeperDataCache - [State:CONNECTED Timeout:30000
sessionid:0x100000a69f50002 local:/10.244.0.59:56396
remoteserver:test-pulsar-pod-kill-zookeeper-ca/10.96.26.160:2181
lastZxid:9946 xid:848 sent:848 recv:873 queuedpkts:0 pendingresp:1
queuedevents:0] Received ZooKeeper watch event: WatchedEvent
state:SyncConnected type:NodeDataChanged
path:/loadbalance/brokers/10.244.0.59:8080
5172 18:57:53.416 [pulsar-load-manager-1-1] INFO
org.apache.pulsar.broker.loadbalance.impl.ModularLoadManagerImpl - Only 1
broker available: no load shedding will be performed
5173 18:58:00.902 [pulsar-client-io-43-1] INFO
org.apache.pulsar.client.impl.ConsumerStatsRecorderImpl - Starting Pulsar
consumer status recorder with config: {
5174 "topicNames" : [
"persistent://pulsar/test-pulsar-pod-kill/10.244.0.59:8080/healthcheck" ],
```
Should I be worried about the L:5170? It's really slow and reports a
`maximum change 33235.83459104782% exceeded threshold 10%`
What's the meaning of the log anyway?
And this is the log 15s ago:
```
5105 18:57:33.642 [pulsar-load-manager-1-1] INFO
org.apache.pulsar.broker.loadbalance.impl.ModularLoadManagerImpl - Writing
local data to ZooKeeper because maximum change 11.047309637069702% exceeded
threshold 10%; time since last report written is 45.0 seconds
```
Is it realistic to accelerate from 11% to 33235% in just 15s?
--
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: commits-unsubscr...@pulsar.apache.org
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
