You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
2024-03-05T13:01:55,951+0000 [main] INFO org.apache.pulsar.testclient.BrokerMonitor -
Broker Data for pinger-pinger-us-east-1a-pulsar-broker-1.pinger-pinger-us-east-1a-pulsar-broker.pinger.svc.cluster.local:8080:
===================================================================================================================
||SYSTEM |CPU % |MEMORY % |DIRECT % |BW IN % |BW OUT % |MAX % ||
|| |2.09 |39.87 |15.63 |0.03 |0.12 |15.63 ||
||COUNT |TOPIC |BUNDLE |PRODUCER |CONSUMER |BUNDLE + |BUNDLE - ||
|| | |6 | | | | ||
||LATEST |MSG/S IN |MSG/S OUT |TOTAL |KB/S IN |KB/S OUT |TOTAL ||
|| |297.83 |297.79 |595.62 |207.90 |207.88 |415.78 ||
===================================================================================================================
2024-03-05T13:01:55,952+0000 [main] INFO org.apache.pulsar.testclient.BrokerMonitor -
Broker Data for pinger-pinger-us-east-1a-pulsar-broker-0.pinger-pinger-us-east-1a-pulsar-broker.pinger.svc.cluster.local:8080:
===================================================================================================================
||SYSTEM |CPU % |MEMORY % |DIRECT % |BW IN % |BW OUT % |MAX % ||
|| |1.86 |64.68 |17.19 |0.04 |0.22 |17.19 ||
||COUNT |TOPIC |BUNDLE |PRODUCER |CONSUMER |BUNDLE + |BUNDLE - ||
|| | |9 | | | | ||
||LATEST |MSG/S IN |MSG/S OUT |TOTAL |KB/S IN |KB/S OUT |TOTAL ||
|| |392.05 |392.10 |784.16 |273.21 |273.23 |546.44 ||
===================================================================================================================
2024-03-05T13:01:55,953+0000 [main] INFO org.apache.pulsar.testclient.BrokerMonitor -
Broker Data for pinger-pinger-us-east-1a-pulsar-broker-2.pinger-pinger-us-east-1a-pulsar-broker.pinger.svc.cluster.local:8080:
===================================================================================================================
||SYSTEM |CPU % |MEMORY % |DIRECT % |BW IN % |BW OUT % |MAX % ||
|| |6.17 |44.01 |17.19 |0.17 |0.62 |17.19 ||
||COUNT |TOPIC |BUNDLE |PRODUCER |CONSUMER |BUNDLE + |BUNDLE - ||
|| | |10 | | | | ||
||LATEST |MSG/S IN |MSG/S OUT |TOTAL |KB/S IN |KB/S OUT |TOTAL ||
|| |1591.14 |1527.11 |3118.25 |1585.48 |1534.89 |3120.37 ||
===================================================================================================================
The bandwith metrics are all in the 0.X% range. So I'm wondering how the maximum bandwidth is defined?
Shouldn't the metrics at least be normalized based on the weights?
After the change the broker load score drops to almost 0. In order to fix this, I set the bandwidth weights to 100 which seems to give the correct results.
Please see the screenshot below that shows the broker load score before and after the 2 config changes.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
I want to use TransferShedder to load balance brokers purely on BandwidthIn and BandwidthOut metrics.
For this, I set the following:
Here is an excerpt of the broker load stats:
The bandwith metrics are all in the 0.X% range. So I'm wondering how the maximum bandwidth is defined?
Shouldn't the metrics at least be normalized based on the weights?
After the change the broker load score drops to almost 0. In order to fix this, I set the bandwidth weights to 100 which seems to give the correct results.
Please see the screenshot below that shows the broker load score before and after the 2 config changes.
I'm using pulsar version v3.2.0.
Beta Was this translation helpful? Give feedback.
All reactions