mukesh154 opened a new pull request, #23681:
URL: https://github.com/apache/pulsar/pull/23681

   ### Motivation
   
   The current behavior does not provide clear visibility when the message size 
exceeds the configured maximum size, often leading to `InvalidMessageException` 
error. This change introduces a log statement to notify when the message size 
exceeds the threshold, helping users identify and troubleshoot message size 
issues more easily.
   
   ### Modifications
   
   Added a `log.warn` statement before releasing the semaphore and throwing the 
`InvalidMessageException`.
   The log includes details about the message size, the configured threshold, 
and the producer/topic involved, improving visibility for debugging and 
troubleshooting.
   
   ### Verifying this change
   
   - [X] Make sure that the change passes the CI checks.
   
   This change is a trivial rework / code cleanup without any test coverage.
   
   ### Does this pull request potentially affect one of the following parts:
   
   <!-- DO NOT REMOVE THIS SECTION. CHECK THE PROPER BOX ONLY. -->
   
   *If the box was checked, please highlight the changes*
   
   - [ ] Dependencies (add or upgrade a dependency)
   - [ ] The public API
   - [ ] The schema
   - [ ] The default values of configurations
   - [ ] The threading model
   - [ ] The binary protocol
   - [ ] The REST endpoints
   - [ ] The admin CLI options
   - [ ] The metrics
   - [ ] Anything that affects deployment
   
   ### Documentation
   
   <!-- DO NOT REMOVE THIS SECTION. CHECK THE PROPER BOX ONLY. -->
   
   - [ ] `doc` <!-- Your PR contains doc changes. -->
   - [ ] `doc-required` <!-- Your PR changes impact docs and you will update 
later -->
   - [X] `doc-not-needed` <!-- Your PR changes do not impact docs -->
   - [ ] `doc-complete` <!-- Docs have been already added -->
   


-- 
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: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to