pulsar-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From GitBox <...@apache.org>
Subject [GitHub] codelipenghui opened a new issue #3280: [Feature Request] Control the network bandwidth of the broker
Date Wed, 02 Jan 2019 09:34:07 GMT
codelipenghui opened a new issue #3280: [Feature Request] Control the network bandwidth of
the broker
URL: https://github.com/apache/pulsar/issues/3280
 
 
   #### Network bandwidth in of broker
   
   1. Client send message to broker
   2. Read entries from bookie
   
   #### Network bandwidth out of broker
   
   1. Dispatch message to consumer
   2. Write entries to bookie
   
   Broker will be the network convergence point. 
   
   User send messages to pulsar will cause broker write entries to bookie, if broker dispatch
messages use the high network bandwidth, latency of produce message will becomes higher.
   
   When user consume the cold message(messages is already evict in cache), broker network
bandwidth will becomes higher to read entries from bookie, latency of produce message will
becomes higher.
   
   So, if we can config dispatch rate in bytes and bookie read rate in bytes limit guarantee
that the broker has a certain bandwidth for writing messages.
   
   #### System configuration
   **Pulsar version**: 2.2.0
   

----------------------------------------------------------------
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

Mime
View raw message