allora-worker-manager

You can manage multiple Allora SDK workers by topic and address using a worker manager. It maintains lightweight local state to coordinate lifecycle operations and prevent duplicate active workers per topic.

Worker mapping assigns a unique identifier based on topic ID and address to each worker. This ensures one active worker per topic or address, eliminating deployment conflicts and duplicate prediction streams.

Lifecycle commands include add, deploy, start, stop, and replace operations for Allora workers. These commands feature built-in safety checks and simple health monitoring to streamline fleet orchestration.

Yes, the worker management interface provides per-topic health visibility and host-agnostic orchestration. This allows you to monitor worker status and coordinate restarts across diverse deployment hosts.

Yes, per-worker wallets are implemented for secure key management during worker deployment. This ensures each worker operates with its own isolated credentials when handling inference tasks.

Use the replace lifecycle command to substitute a stopped worker for a specific topic. This operation applies safety checks against the local state to ensure no duplicate active workers are created.