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 2018/12/11 06:26:47 UTC

[GitHub] codelipenghui commented on issue #3155: Deferred messages for consumers

codelipenghui commented on issue #3155: Deferred messages for consumers
URL: https://github.com/apache/pulsar/pull/3155#issuecomment-446087409
 
 
   @lovelle 
   
   >The decision making of expired messages will be made at client side which depends on client clock, being more error prone and difficult to detect and fix by an administrator.
   
   If can't depends on client clock, i think publish time now be client-generated
   
   >There would be a lot of I/O overhead wasted between clients and brokers delivering unnecessary messages.
   
   Your worry is very necessary. 
   
   Through our discussion, we can get the following conclusions:
   
   1. Deferred messages consume can't depends on client clock include message publish time.
   2. Implement deferred message consume on client-side has lot of downsides(I/O waste, depends on client clock, un-acked messages limitation...)
   
   If on server-side, can delayed dispatch be simpler?
   
   Dispatcher read entries from ledger, i think we just need to check tail message(if generated on server side, publish time is already sorted)
   

----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on 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