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 2021/11/24 06:44:23 UTC

[GitHub] [pulsar] Jason918 opened a new issue #12958: [Bug] Inconsistent maxMessageSize meaning between broker config and topicPolicy config.

Jason918 opened a new issue #12958:
URL: https://github.com/apache/pulsar/issues/12958


   **Describe the bug**
   Currently, we have two maxMessageSize settings. 
   
   1. maxMessageSize in broker.conf. This is used by client. It limits the size of final **message payload** bytes (after compression/encryption).
   2. maxMessageSize in TopicPolicy, set by `org.apache.pulsar.client.admin.TopicPolicies#setMaxMessageSize`. It limits the size of message **header and payload**. See https://github.com/apache/pulsar/blob/6b8ebbd288085dc5a93a9e92706eb5f5ad397cb8/pulsar-broker/src/main/java/org/apache/pulsar/broker/service/persistent/PersistentTopic.java#L413
   
   
   **To Reproduce**
   Steps to reproduce the behavior:
   1. call admin.topicPolicies().setMaxMessageSize(5);
   2. Produce message with body  byte[5]{}
   4. Send fail with message size exceeded error.
   
   **Expected behavior**
   Message should produce success.
   
   **Screenshots**
   NA
   
   **Desktop (please complete the following information):**
    - OS: macOS
   
   **Additional context**
   NA
   


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

To unsubscribe, e-mail: commits-unsubscribe@pulsar.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org



[GitHub] [pulsar] Jason918 commented on issue #12958: [Bug] Inconsistent maxMessageSize meaning between broker config and topicPolicy config.

Posted by GitBox <gi...@apache.org>.
Jason918 commented on issue #12958:
URL: https://github.com/apache/pulsar/issues/12958#issuecomment-977580610


   I think we can add new field "payload size" in CommandSend API. 
   And make topic policy only checks the payload size.
   What do you think? @codelipenghui @315157973 @eolivelli 


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

To unsubscribe, e-mail: commits-unsubscribe@pulsar.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org



[GitHub] [pulsar] Jason918 commented on issue #12958: [Bug] Producer fails to send message size equals to maxMessageSize in topic policy setting.

Posted by GitBox <gi...@apache.org>.
Jason918 commented on issue #12958:
URL: https://github.com/apache/pulsar/issues/12958#issuecomment-1016054861


   This will be fixed by PIP-132 in #13591
   Close this issue.


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

To unsubscribe, e-mail: commits-unsubscribe@pulsar.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org



[GitHub] [pulsar] Jason918 closed issue #12958: [Bug] Producer fails to send message size equals to maxMessageSize in topic policy setting.

Posted by GitBox <gi...@apache.org>.
Jason918 closed issue #12958:
URL: https://github.com/apache/pulsar/issues/12958


   


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

To unsubscribe, e-mail: commits-unsubscribe@pulsar.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org