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/22 05:56:20 UTC

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

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


   > What I am trying to ensure is if there is a reader actively reading events, we should be able to make sure the continuity of the events it read.
   
   The only way to give a guarantee of that is through a "durable" resource that is maintained by the system: similar to a subscription.
   
   And that, of course, comes with the same strings as a subscription. eg: it has to manually deleted since we don't know upfront whether a user is done or it's just down.
   
   That and also that we need a "storage quota" policy as well, because the disk space is finite.
   
   > The current behavior of a reader is that readers are included in the backlog quota
   
   No, no and no..
   That's just a bug that goes against the documented behavior and that it's absolutely non reliable, in that is only works if ***nothing*** gets restarted.
   
   That's not the "current behavior".  
   
   


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