The issue tracker is **ONLY** used for bug report and feature request. Keep in mind, please check whether there is an existing same report before your raise a new one.
Alternately (especially if your communication is not a bug report), you can send mail to our [mailing lists](http://rocketmq.apache.org/about/contact/). We welcome any friendly suggestions, bug fixes, collaboration and other improvements. Please ensure that your bug report is clear and that it is complete. Otherwise, we may be unable to understand it or to reproduce it, either of which would prevent us from fixing the bug. We strongly recommend the report(bug report or feature request) could include some hints as the following: **BUG REPORT** 1. Please describe the issue you observed: - What did you do (The steps to reproduce)? Update the value of the maxMessageSize in broker by using command `mqadmin updateBrokerConfig` to send big message. - What did you expect to see? Send message succeed without restart broker. - What did you see instead? The new valuse of maxMessageSize is invalid without restarting, but it will be done if you restart broker. 2. Please tell us about your environment: CentOS7.3 3. Other information (e.g. detailed explanation, logs, related issues, suggestions how to fix, etc): **FEATURE REQUEST** 1. Please describe the feature you are requesting. Updating the maxMessageSize of broker by command `mqadmin updateBrokerConfig` and the value will done quickly without restarting. 2. Provide any additional detail on your proposed use case for this feature. In my opinion, command `mqadmin updateBrokerConfig` will update the value in MessageStoreConfig and properties file without restarting but DefaultAppendMessageCallback. DefaultAppendMessageCallback is used when putMessage to commitLog, and it depends on the value of maxMessageSize initilized in first starting, command `mqadmin updateBrokerConfig` is invalid if not restarting. 2. Indicate the importance of this issue to you (blocker, must-have, should-have, nice-to-have). Are you currently using any workarounds to address this issue? 4. If there are some sub-tasks using -[] for each subtask and create a corresponding issue to map to the sub task: - [sub-task1-issue-number](example_sub_issue1_link_here): sub-task1 description here, - [sub-task2-issue-number](example_sub_issue2_link_here): sub-task2 description here, - ... [ Full content available at: https://github.com/apache/rocketmq/issues/480 ] This message was relayed via gitbox.apache.org for [email protected]
