Server redundancy/load-balancing

Feature Suggestions
1

Redundancy can be handled at the infrastructure level by running a VM in a clustered setup with e.g. VMware HA enabled. However, that can incur a downtime of a few minutes while the new VM boots up, and can possibly incur issues of unclean filesystems, etc.

Load-balancing can be handled by running multiple servers, but requires that users be manually, statically divided between the servers.

I’ve seen a few projects that aim to address the load-balancing problem (PlexRemoteTranscoder, which seems to be dead, and UnicornTranscoder), but these are third-party solutions. That’s not great for a few reasons. 1) Development could stop at any time, as we saw with PRT. 2) I have to delay updating the server until the new release has been tested by the 3rd party. 3) Full feature parity has not been achieved (e.g. UnicornTranscoder can’t do GPU transcoding and auto-quality.)

I realize that one of the major goals of Plex as a product is to make it simple to use, and that most users in the target audience probably have no interest in redundancy or load-balancing. But I’m curious if these are things that we’ll ever see from Plex directly. I’m hoping a dev can weigh in here.

Thanks!

1 Like
2

Plex doesn’t disclose their roadmap; not even to many of us internally.
The product team and that part of Engineering are very tight-lipped.

I am moving this to Feature Request because it speaks to the larger audience and not linux-specific.

As a Feature Request, others can vote and provide that secondary Level-of-Interest information to both teams.

3

Yeah, good point.

4

This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.