Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Cache invalidation considerUow problem #19633

Closed
ahmetfarukulu opened this issue Apr 26, 2024 · 1 comment · Fixed by #19671
Closed

Cache invalidation considerUow problem #19633

ahmetfarukulu opened this issue Apr 26, 2024 · 1 comment · Fixed by #19671
Assignees
@maliming
Labels
bug
Milestone
8.1-patch

Comments

@ahmetfarukulu
Copy link
Member

When handling cache invalidation, it's crucial to set the considerUow parameter to true. If this parameter is not set correctly, the cache gets removed immediately. However, if there are other HTTP requests for related cache before the unit of work is complete, the cache might remain in a dirty state.

We should do this for all invalidators such as; PermissionGrantCacheItemInvalidator, TenantConfigurationCacheItemInvalidator etc.
@ahmetfarukulu ahmetfarukulu added this to the 8.1-patch milestone Apr 26, 2024
@maliming maliming mentioned this issue May 2, 2024
Merged
@ahmetfarukulu
Copy link
Member Author

#19671

@ahmetfarukulu ahmetfarukulu linked a pull request May 2, 2024 that will close this issue
Set considerUow when clearing the cache. #19671
Merged
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@maliming maliming

Labels
bug
Projects
None yet
Milestone
8.1-patch
Development

Successfully merging a pull request may close this issue.

Set considerUow when clearing the cache. abpframework/abp
2 participants
@maliming @ahmetfarukulu