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 2020/05/27 19:30:24 UTC

[GitHub] [pulsar] sijie commented on pull request #6787: Using Readers still causes backlog quota to be observed

sijie commented on pull request #6787:
URL: https://github.com/apache/pulsar/pull/6787#issuecomment-634892636


   > I have already heard from members of industry/community that there are too many tunables in Pulsar and its hard for people to navigate.
   
   Well, "tuneables" are *unfortunately* required in open source projects due to compatibility consideration or when introducing new features. I would suggest making the conversation staying on discussing the issue itself.
   
   ---
   
   Anyway, My request is simple - A reader should not experience any cursor reset or unexpected behaviors when reading a log. Before this change, a reader cursor is tracked in min-heap for retention. it is not a problem. After this change, the reader will experience unexpected behaviors. 
   
   We can do here:
   
   a) use a feature flag to control whether include reader cursors in the storage quota consideration; b) if you don’t want to introduce the feature flag, I would request documenting the behavior clearly and provide a clear guideline for applications who are using readers.
   
   


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