Skip to content

Optimize retry in failbackregistry #2752

@carryxyh

Description

@carryxyh

Currently our retry will start executing when the FailbackRegistry starts. We can completely retry it more regularly.

At present, we have five collections that need to be checked regularly. Why not check regularly when the collection is not empty, check and retry will continue until the collection is empty. If the collection has new elements that require retry, continue to open a task.

So we need to open up to five tasks at most, at least we can do not need to retry.

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

No type
No fields configured for issues without a type.

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions