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 2019/05/21 07:10:53 UTC

[GitHub] [pulsar] codelipenghui opened a new pull request #4320: Change default backlog quota retention policy to consumer_backlog_eviction

codelipenghui opened a new pull request #4320: Change default backlog quota retention policy to consumer_backlog_eviction
URL: https://github.com/apache/pulsar/pull/4320
 
 
   ### Motivation
   
   Previously we used producer_request_hold as the default backlog quota retention policy. But producer_request_hold is unfriendly for online business, even online business faces big risks. When users ask us to apply pulsar to the online environment, what should be paid attention to? Change the default backlog quota retention policy often mentioned by the first, and initially at zhaopin.com, we have also had such problems.
   
   So, I propose to change the default backlog quota retention policy to consumer_backlog_eviction, from our practice shows that this is a choice for most situations and the most important thing is that this option allows users to avoid taking greater risks.
   
   This change will affect the way our existing users use it. I want to discuss it together to make some trade-offs. If necessary, i can start a email thread.
   
   ### Modifications
   
   Change broker level default backlog quota retention policy to consumer_backlog_eviction.
   
   *If `yes` was chosen, please highlight the changes*
   
     - Dependencies (does it add or upgrade a dependency): (no)
     - The public API: (no)
     - The schema: (no)
     - The default values of configurations: (yes)
     - The wire protocol: (no)
     - The rest endpoints: (no)
     - The admin cli options: (no)
     - Anything that affects deployment: (no)
   
   ### Documentation
   
     - Does this pull request introduce a new feature? (no)
   

----------------------------------------------------------------
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:
users@infra.apache.org


With regards,
Apache Git Services