Guarantee ordering between plugin hooks
Open
enhancement
- Dominant language
- Python
- Stars
- 1.7k
- Forks
- 778
- Avg merge
- 2h 50m
- Merged PRs (30d)
- 3
Description
**Problem**
Currently, there are no ordering guarantees between plugin hooks. In particular, `start/setup` and `close/teardown` get executed concurrently for all plugins. This creates problems in some cases (e.g., #8485) and makes it generally harder to reason about things.
**Proposed Solution**
It would be nice if we could guarantee ordering between the individual plugins. This probably means that we choose their registration order to ensure that the ordering is _always_ the same, e.g. for existing and new workers.
**Notes**
There are some caveats to this, like non-ordered RPC calls (#7480), that we need to consider.
Contributor guide
Assessment
This issue has not been assessed yet.