You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@pulsar.apache.org by GitBox <gi...@apache.org> on 2018/01/30 18:52:14 UTC

[GitHub] merlimat opened a new issue #1149: Network interface max speed information can be unreliable on VMs

merlimat opened a new issue #1149: Network interface max speed information can be unreliable on VMs
URL: https://github.com/apache/incubator-pulsar/issues/1149
 
 
   #### Expected behavior
   
   The Pulsar load manager is relying on the network traffic information of a broker to decide whether it's overloaded or not. To calculate the network usage absolute and %, we currently rely on the info coming from Linux as reported on 
   
   ```
   /sys/class/net/$NIC/speed
   ```
   
   #### Actual behavior
   
   This works reliably on bare metal machines and reports either 1Gbps or 10Gbps depending on the NIC. On the contrary, in VMs environments such as EC2, Linux is reporting the max speed as 10Gbps but the traffic is actually throttled at 1Gbps.
   
   The result is that Pulsar thinks the current network usage is 1/10th of the available bandwidth and doesn't mark the broker as overloaded.
   
   We need to have a way to override the max NIC speed to the real available bandwidth.
   

----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
users@infra.apache.org


With regards,
Apache Git Services