A master process coordinates a distributed training group. During initialization, every process registers with it; one process takes the master role while the others act as workers, and registration waits until the group is complete. section 4.2.3
The master role supports several operational responsibilities:
- Uses a globally unique rank, with rank 0 identifying the master, alongside world_size and the master's address and port. section 4.2.3
- Provides the coordination point for distributed execution; in Kubernetes, a master-worker pod receives a dedicated service for worker connectivity. section 4.3.2
- Acts as the reporting and persistence authority: inspect the master worker for synchronized progress, and save models or checkpoints only from the master. section 4.5
Three-worker Kubernetes training group
Submitting PARALLEL_INSTANCES=3 creates three training pods: one master worker and two normal workers. Kubernetes also creates a master service, while training status can be checked through the service API or the master worker. section 4.3.2
