codelipenghui commented on issue #4320: Change default backlog quota retention policy to consumer_backlog_eviction URL: https://github.com/apache/pulsar/pull/4320#issuecomment-494677451 @merlimat If I didn’t understand it wrong, this is just to guarantee that the data that has been written is not be lost. If we look at the user's entire system, pulsar is the important part, serving real-time streaming data. If it becomes unwritable, this is also data loss for the user. The core of the problem is how the user should handle when the backlog has exceeded the threshold, delete old data or reject new data. For streaming data platforms, i think rejecting new data is basically unacceptable. Users can use the retention mechanism to confirm how long they retain data. For the backlog, this is for a subscriber. There will be one subscriber's backlog cause all new data to be rejected. If the default configuration is inclined to not lost data. reject new data should also be considered. If do not consider resource limitations, not limit the backlog by default can match both two . My suggestion is to prefer the configuration with the least loss to the user as the default configuration.
---------------------------------------------------------------- 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: us...@infra.apache.org With regards, Apache Git Services
