fix: audit logger backpressure handling #97
Closed
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR prevents memory exhaustion (OOM) in the Audit Logger service during high-velocity logging events.
1. Backpressure Handling
stream.write(). In scenarios like DDOS attacks or high-traffic bursts, logging thousands of events per second filled the Node.js internal buffer faster than it could be flushed to disk, causing massive memory spikes (verified 170MB+ in seconds).stream.write()return value. If it returnsfalse(buffer full), thelogEventmethod nowawaitsthe'drain'event before proceeding.logEventwill pause, preventing the process from crashing.Result: Stable memory usage under high load.