You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, Indexers will run indefinitely. There is no way for developers to control or interrupt this process. Similarly, the system itself cannot intervene when needed, meaning we cannot stop indexers which are perpetually failing.
The current architecture isn't ideal for managing these lifecycle events. Runner needs to poll for configuration updates creating delays as well as additional latency during executions.
The goal of this epic is to refactor the current architecture to create a dedicated control layer, paving a way for lifecycle management of indexers.
The content you are editing has changed. Please copy your edits and refresh the page.
Description
Currently, Indexers will run indefinitely. There is no way for developers to control or interrupt this process. Similarly, the system itself cannot intervene when needed, meaning we cannot stop indexers which are perpetually failing.
The current architecture isn't ideal for managing these lifecycle events. Runner needs to poll for configuration updates creating delays as well as additional latency during executions.
The goal of this epic is to refactor the current architecture to create a dedicated control layer, paving a way for lifecycle management of indexers.
Indexer Lifecycle
Control/Data Plane Separation
StartBlock
config options #521StartBlock::Continue
via UI #535allowlist
#543allowlist
#568The text was updated successfully, but these errors were encountered: