Background jobs distributed lock #10325
Merged
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.
Resolves #10032.
Volo.Abp.DistributedLocking.Abstractions
package as a local, multi-thread named locking package - we use it if the application is not clustered. It is the default unless you configure a real distributed lock provider.IAbpDistributedLock
is the main service that we can acquire locks. It can be improved in the future, but enough for now. I consider the distributed locking as an internal framework feature for now.Volo.Abp.EventBus.Boxes
package and moved code to theVolo.Abp.EventBus
package.BackgroundJobWorker
, so it can work in a clustered environment.EventBusBoxesOptions.DistributedLockWaitDuration.Milliseconds
. It should be TotalMilliseconds, not Milliseconds.