2024-06-24, 07:54 PM
(This post was last modified: 2024-06-25, 12:28 AM by pcm. Edited 6 times in total.)
It's possible, but not exactly the way you're imagining it to be. You'd technically never shut off your DietPi computer (or the Intel N100).
And you'd have a nginx running on another Pi as a load balancer.
Upstream to your load-balancer Pi you'd have your beefy-PC as one node and the low-power Pi as the other node. You'd do weighted load-balancing so that while your beefy-PC is on it takes almost all the load of serving up jellyfin.
And when you shutdown your beefy-PC, nginx, acting as a load-balancing-reverse-proxy, will direct all the load to the DietPi after noticing that the beefy-PC node is offline. All this will happen by design, because that's what load-balancers are designed to do.
NOTE: You'd want to also share some jellyfin directories between the two nodes.
So, you'll need to put the jellyfin directories on your NAS as well, besides your media files.
At the very least you'd want to mount a shared storage as
And you'd have a nginx running on another Pi as a load balancer.
Upstream to your load-balancer Pi you'd have your beefy-PC as one node and the low-power Pi as the other node. You'd do weighted load-balancing so that while your beefy-PC is on it takes almost all the load of serving up jellyfin.
And when you shutdown your beefy-PC, nginx, acting as a load-balancing-reverse-proxy, will direct all the load to the DietPi after noticing that the beefy-PC node is offline. All this will happen by design, because that's what load-balancers are designed to do.
NOTE: You'd want to also share some jellyfin directories between the two nodes.
So, you'll need to put the jellyfin directories on your NAS as well, besides your media files.
At the very least you'd want to mount a shared storage as
/var/lib/jellyfin on both your machines so that your data and metadata stay consistent.