michaeljmarshall commented on pull request #9393: URL: https://github.com/apache/pulsar/pull/9393#issuecomment-773459986
@lhotari - for what it's worth, it looks like the failure is related to the cpu usage again, although this time it's not necessarily a value I would have expected--Infinity. ```text 07:39:57.219 [TestNG-method=testBrokerSelectionForAntiAffinityGroup-1] INFO org.apache.pulsar.broker.loadbalance.impl.ModularLoadManagerImpl - 2 brokers being considered for assignment of tenant-010508de-9e58-4c86-95d8-d9b28f60a7ec/use/ns1/0x00000000_0xffffffff 07:39:57.219 [TestNG-method=testBrokerSelectionForAntiAffinityGroup-1] WARN org.apache.pulsar.broker.loadbalance.impl.LeastLongTermMessageRate - Broker http://localhost:42477 is overloaded: max usage=Infinity 07:39:57.220 [TestNG-method=testBrokerSelectionForAntiAffinityGroup-1] WARN org.apache.pulsar.broker.loadbalance.impl.LeastLongTermMessageRate - Broker localhost:42477 is overloaded: CPU: Infinity%, MEMORY: 17.458387%, DIRECT MEMORY: 2.4414062%, BANDWIDTH IN: NaN%, BANDWIDTH OUT: NaN% 07:39:57.224 [TestNG-method=testBrokerSelectionForAntiAffinityGroup-1] INFO org.apache.pulsar.broker.loadbalance.impl.ModularLoadManagerImpl - 1 brokers being considered for assignment of tenant-010508de-9e58-4c86-95d8-d9b28f60a7ec/use/ns2/0x00000000_0xffffffff 07:39:57.224 [TestNG-method=testBrokerSelectionForAntiAffinityGroup-1] WARN org.apache.pulsar.broker.loadbalance.impl.LeastLongTermMessageRate - Broker http://localhost:42477 is overloaded: max usage=Infinity 07:39:57.224 [TestNG-method=testBrokerSelectionForAntiAffinityGroup-1] WARN org.apache.pulsar.broker.loadbalance.impl.LeastLongTermMessageRate - Broker localhost:42477 is overloaded: CPU: Infinity%, MEMORY: 17.458387%, DIRECT MEMORY: 2.4414062%, BANDWIDTH IN: NaN%, BANDWIDTH OUT: NaN% 07:39:57.225 [TestNG-method=testBrokerSelectionForAntiAffinityGroup-1] WARN org.apache.pulsar.broker.loadbalance.impl.LeastLongTermMessageRate - Broker http://localhost:42477 is overloaded: max usage=Infinity 07:39:57.225 [TestNG-method=testBrokerSelectionForAntiAffinityGroup-1] WARN org.apache.pulsar.broker.loadbalance.impl.LeastLongTermMessageRate - Broker localhost:42477 is overloaded: CPU: Infinity%, MEMORY: 17.458387%, DIRECT MEMORY: 2.4414062%, BANDWIDTH IN: NaN%, BANDWIDTH OUT: NaN% !!!!!!!!! FAILURE-- [TestClass name=class org.apache.pulsar.broker.loadbalance.AntiAffinityNamespaceGroupTest].testBrokerSelectionForAntiAffinityGroup([])------- ``` I'm not positive what solutions make sense here, but it does seem like a surprising behavior that the logic calculated the CPU usage at `Infinity%`. Seems like something worth looking into. Ultimately, it's the same logic for overloading that is the problem here. ---------------------------------------------------------------- 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. For queries about this service, please contact Infrastructure at: [email protected]
