Keep Room Routing Metadata Alive

[Harxhit]

Problem

Room routing metadata in Redis currently expires after one hour. If the room is still active after the TTL expires, subsequent viewer heartbeats cannot retrieve nodeId and therefore cannot determine which pod owns the room.

This causes cross-pod heartbeat routing to fail and prevents viewer presence from being refreshed.

Proposed Solution

Increase the room metadata TTL and add a periodic task that checks the room's active state.

• Periodically check whether the room is still active.
• If the room is active, refresh/extend its Redis TTL.
• If the room is no longer active, allow the metadata to expire or remove it.
• Ensure the routing metadata remains available for the entire lifetime of an active room.

Expected Result

Active rooms should retain their Redis routing metadata, allowing heartbeats to continue resolving the owning pod throughout the room's lifetime.