You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@bookkeeper.apache.org by "Sijie Guo (JIRA)" <ji...@apache.org> on 2013/04/26 02:22:17 UTC

[jira] [Commented] (BOOKKEEPER-607) Filtered Messages Require ACK from Client Causes User Being Throttled Incorrectly Forever

    [ https://issues.apache.org/jira/browse/BOOKKEEPER-607?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13642422#comment-13642422 ] 

Sijie Guo commented on BOOKKEEPER-607:
--------------------------------------

the issue would also affect cross region delivery. we need to track the filtered msg id range and last consumed seq id to address the sequence id gap introduced by filter out messages.
                
> Filtered Messages Require ACK from Client Causes User Being Throttled Incorrectly Forever
> -----------------------------------------------------------------------------------------
>
>                 Key: BOOKKEEPER-607
>                 URL: https://issues.apache.org/jira/browse/BOOKKEEPER-607
>             Project: Bookkeeper
>          Issue Type: Bug
>          Components: hedwig-server
>    Affects Versions: 4.2.0, 4.2.1
>            Reporter: Jiannan Wang
>            Assignee: Jiannan Wang
>            Priority: Blocker
>             Fix For: 4.3.0
>
>
> In current FIFODeliveryManager, once a message is filtered in ActiveSubscriberState#messageScanned(), it just call ActiveSubscriberState#sendingFinished() and wait client's acknowledgement. However, the message isn't being delivered to client side, and once the number of such filtered messages larger than the delivery window size, the user cannot receive messages anymore!

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira