feat: add agent service to check availability #999
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
🧠 Rationale behind the change
In our production environment, we need to manage agents registered with LivekitServer. Through load testing, we can determine how many jobs a single agent worker can handle. Therefore, before dispatching an agent to a room, we want to check the availability of the agent.
However, the agent state is managed per LivekitServer instance, and we cannot retrieve all agent workers from the cluster. To address this, we plan to poll the agent state from all nodes and cache that state with a TTL in our dispatch service.