Recommendation for media server volume expansion
All media server pods are terminated if media server volumes are expanded. Ensure that no jobs are running on media servers when volume must be expanded.
During media server volume expansion, it is recommended that the value of must be equal to or greater than the media servers added in primary server. Navigate to > to check the number of media servers added in primary server on Web UI.
Primary server is also a media server that must not be considered. External media servers must not be considered.
During volume expansion, if media servers added in primary server are more than the value of (that is, user has reduced the value for replicas field) then the volumes of provided value would be expanded. If the value for is increased again irrespective of volume expansion and if media server must be scaled up, then all the media server pods would be terminated and would be re-deployed with all PVCs expanded. This might fail the backup jobs as media servers may be terminated.
Expanding the volume of a media server may trigger pod restarts to apply the changes, and existing PVCs can be updated to ensure that the media server pods have sufficient storage volumes available for their operation. These scenarios are described in detail as follows:
Pod restart on volume expansion
If the volume of a running media server's data/log volume is expanded, the pod associated with that volume will restart automatically to apply the changes. This is because Kubernetes dynamically manages volumes and mounts, so any changes to the underlying volume will require the associated pod to restart to pick up the changes.
Updating PVCs for insufficient volumes
If there are existing Persistent Volume Claims (PVCs) running but with insufficient amounts of log/data volume, they can be updated to meet the requirements of the media server pods.
PVCs define the requirements for storage volumes used by pods. By updating the PVCs, you can specify larger volumes to accommodate the media server's needs.
Once the PVCs are updated, Kubernetes will automatically resize the underlying volumes to match the new PVC specifications, ensuring that the media server pods have access to the required storage capacity.