maytasm opened a new pull request #11078:
URL: https://github.com/apache/druid/pull/11078


   Introduce a new configuration that skip storing audit payload if payload 
size exceed configured limit
   
   ### Description
   
   Audit log such as coordinator.compaction.config can get very large as 
datasources and their configurations churn. This can cause problems such as 
   - Metadata database taking up too much space / running out of storage space
   - Configuration change (such as compaction configuration) failing as we are 
not able to insert new row into audit table due to exceeding the database size 
limit (max_allowed_packet, etc) 
   
   This PR introduce a new configuration that skip storing audit payload if 
payload size exceed configured limit. The default value is set to -1 which 
disables this check, meaning Druid will always store audit payload regardless 
of it's size.
   
   This PR has:
   - [x] been self-reviewed.
      - [ ] using the [concurrency 
checklist](https://github.com/apache/druid/blob/master/dev/code-review/concurrency.md)
 (Remove this item if the PR doesn't have any relation to concurrency.)
   - [x] added documentation for new or modified features or behaviors.
   - [ ] added Javadocs for most classes and all non-trivial methods. Linked 
related entities via Javadoc links.
   - [ ] added or updated version, license, or notice information in 
[licenses.yaml](https://github.com/apache/druid/blob/master/dev/license.md)
   - [x] added comments explaining the "why" and the intent of the code 
wherever would not be obvious for an unfamiliar reader.
   - [x] added unit tests or modified existing tests to cover new code paths, 
ensuring the threshold for [code 
coverage](https://github.com/apache/druid/blob/master/dev/code-review/code-coverage.md)
 is met.
   - [ ] added integration tests.
   - [x] been tested in a test Druid cluster.
   


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



---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to