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.

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

TypeMissingException for very old TaskActivity, even for which orchestration have finished long back. #1059

Open
sainipankaj90k opened this issue Apr 3, 2024 · 0 comments

Comments

@sainipankaj90k
Copy link

Problem statement:

  • We are observing quite some task-activities that are failing with TypeMissing exception.
  • This results in backoff and reduces the performance significantly.
  • This becomes interesting, especially when the type (TaskActivity/TaskOrchestration) is intentionally removed assuming old ones would die eventually. (Especially for the case of testing).
  • We can't delete them manually, as message is read by taskhubworker and is hidden.
  • There are cases where orchestrator is already completed, while task-activity is still trying to run.

Ask:

  • Can there be a way, where one can provide the ETA for type, implies, when it is picked up for processing, if the time it queued was older than a threshold interval, just mark it finished.
  • For task-activities for which orchestration is already completed, can those just be removed without processing?
  • A way to kill one type of type (say orchestration of type A, just remove all those entries from the queue, similarly for task-activity and other work-items). Like some API etc. E.g., AddNoOpTaskOrchestration, AddNoOpTaskActivity.
@sainipankaj90k sainipankaj90k changed the title TypeMissingException for very old TaskActivity. TypeMissingException for very old TaskActivity, even for which orchestration have finished long back. Apr 3, 2024
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

No branches or pull requests

1 participant