Skip to content

[Task]: More accurate timing: using DB to store elapsed time of crawl #3605

Description

@ikreymer

Description

Currently, the execution time is stored in the DB and on the k8s object, but the elapsed time to determine when to stop the crawl is only stored on the k8s. Execution time is also stored on the k8s object.
Due to possibility of reentrancy calls metacontroller, the DB should be the 'source of truth' for all crawl timing related data, and both data should be in sync.

Context

No response

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

Projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions