Resource Policy: Login Nodes
Login nodes are for administrative tasks only. Compute-intensive processes will be terminated to ensure system stability for all users.
Prohibited Activities
The login node is a shared "reception desk." Do not run the following directly on the login node:
- Python, R, or Slurm Scripts: Even brief executions can spike shared resources.
- Data Compression: Using
tar,zip, orpigzon large datasets. - AI Applications: Triggering code execution or data-heavy workflows locally.
Environment Comparison
| Feature | Login Node | Compute Node |
|---|---|---|
| Purpose | File management / Editing | Actual job execution |
| Shared by | All users | Allocated to you |
| Running Jobs | ❌ Prohibited | ✅ Required |
The Correct Workflow
Option A: Interactive Testing
# Request a compute node for debugging
srun --partition=interactive --cpus-per-task=1 --mem=4G --time=02:00:00 --pty bash
srun --partition=interactive --cpus-per-task=1 --mem=4G --time=02:00:00 --pty bash
Option B: Batch Processing
#!/bin/bash
#SBATCH --job-name=compression
#SBATCH --mem=8G
tar -czf data.tar.gz ./large_folder
💡 System Tip: If using
screen, always start the session after you have successfully landed on a compute node via srun.