Skip to content

serialize event count in store function call #1065

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
May 29, 2025
Merged

Conversation

raju-opti
Copy link
Contributor

if multiple events are processed concurrently, all event process request might read the initial store size and write to the store, potentially exceeding the store size limit. Serializing the store size read should fix this. Once the size is loaded in memory, further event process read should just read the in memory value

if multiple events are processed concurrently, all event process
request might read the initial store size and write to the store,
potentially exceeding the store size limit. Serializing the
store size read should fix this. Once the size is loaded in memory,
further event process read should just read the in memory value
@coveralls
Copy link

Coverage Status

coverage: 79.7% (-0.03%) from 79.732%
when pulling 3b444e1 on raju/event_limit_fix
into 49f19a6 on master.

@raju-opti raju-opti merged commit e46273a into master May 29, 2025
13 of 19 checks passed
@raju-opti raju-opti deleted the raju/event_limit_fix branch May 29, 2025 15:29
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants