search

pabloromeo / clusterplex

ClusterPlex is an extended version of Plex, which supports distributed Workers across a cluster to handle transcoding requests.
MIT License
450 stars 35 forks source link

ORCHESTRATOR question. #331

Closed Nullvoid3771 closed 4 weeks ago

Nullvoid3771 commented 4 weeks ago

Do I need to change the orchestrator url? When I go to the url nothing happens so I'm wondering if their is any setup on my end to make this local domain work?

"The url where the orchestrator service can be reached (ex: http://plex-orchestrator:3500)"

Nullvoid3771 commented 4 weeks ago

or is "plex-orchestrator" a placeholder for the ip the orchestrator lives on which leads me to another question. If that's the case what happens when orchestrator moves to another system in a docker swarm, wouldn't the url change? or can we put multiple?

pabloromeo commented 4 weeks ago

It refers to the service name. So in Swarm it would resolve even if it moves from node. The same applies when it's a kubernetes Service.

The orchestrator is used for internal system to system communication, you won't find content there except for the healthcheck.

Nullvoid3771 commented 4 weeks ago

It refers to the service name. So in Swarm it would resolve even if it moves from node. The same applies when it's a kubernetes Service.

The orchestrator is used for internal system to system communication, you won't find content there except for the healthcheck.

Ah okay. So defining a ip is the wrong way to go. What I did was in env pms and worker I defined it as http://192.168.1.x:3500 and then increased the plex-orchestrator replication to two so it would be on both nodes. And at least one would resolve. So guessing I didn’t have to do that and could have kept it as http://plex-orchestrator:3500/ since it’s internal.

pabloromeo commented 4 weeks ago

Ah, no, don't do it that way. You must have a single orchestrator, that will talk to all workers and receive requests from PMS.