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 2019/10/23 21:31:58 UTC

[GitHub] [pulsar] rdhabalia commented on issue #4400: PIP 37: [pulsar-client] support large message size

rdhabalia commented on issue #4400: PIP 37: [pulsar-client] support large message size
URL: https://github.com/apache/pulsar/pull/4400#issuecomment-545645477
 
 
   @jiazhai sorry for late response as I had missed your comment.
   
   > After PIP36 (#4247 ), pulsar could support message size large than 5MB.
   
   That's incorrect. #4247 is not a useful feature and that could be used for a specific usecase but we can not use for large scale and multi tenant system where same bookie is serving topics from different tenants. 
   For example, If client wants to publish message with 100MB and if broker allows to store one message with 100MB into bookie then bookie will max out in 1 or 2 messages and it can directly impact to other tenants for publish and draining backlog. Also, it will be hard to force throttling for one message with 100MB payload size. I have also described this scenario into the PIP.
   Right now, we have multiple users who are chunking the payload at producer side and merging at consumer side and they need this feature to avoid such complexity.
   So, we need this feature available for multiple users.

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


With regards,
Apache Git Services