if my I'm having a worker run locally that is conn...
# ask-aig
gentle-hospital-72989
07/09/2025, 11:27 AMif my I'm having a worker run locally that is connected to my Livekit project on cloud. And then there is one in my production server that is running. Now, somebody in production started a session and my local worker was processing it. Is this accepted behavior or this should not happen?
t
tall-airline-16756
07/09/2025, 11:27 AMThanks for reaching out, Nischal. I'm an AI assistant and I'm here to help. Give me a moment while I research this topic.
tall-airline-16756
07/09/2025, 11:28 AMLiveKit can distribute session processing across multiple workers, including those running locally and on production servers, through its load balancing system that dispatches jobs to available workers.
However, it is generally not recommended to use the same LiveKit project for both local development and production. Running a local worker connected to your production project can lead to your local worker processing real production sessions, which is unintended.
To avoid this, it is best practice to use separate LiveKit projects for local development and for production. This ensures that your local worker only processes sessions related to development and does not interfere with production sessions.
Sources: Deployment and scaling | LiveKit Docs | Deployment and scaling | LiveKit Docs