Skip to main content
RunBook Academy

← All break/fix scenarios in Ceph

intermediateceph-rgw-quota~18 min

RGW user quota tripped - upload fails

Reported symptoms

  • ●S3 PUT request returns SlowDown and 503
  • ●The user is at or over their quota
  • ●Other users can upload to the same bucket

Evidence

  • · radosgw-admin user info shows the user quota and used
  • · radosgw-admin quota get --uid=<user> confirms the quota
  • · radosgw-admin log show lists the quota-related errors
Diagnosis and resolutionclick to reveal

Root cause

The user has reached their RGW quota (objects or bytes). Quotas cap per-user storage.

Remediation

Increase the quota (radosgw-admin quota set), or remove unused objects, or split the workload across multiple users.

Verification

The user can upload successfully; the application proceeds.

Prevention

Set quotas with headroom; alert at 80% of quota; document the per-tenant quota policy.

Architecture

The student examines the broken architecture diagram and identifies the responsible component. The cluster is running Ceph Tentacle (20.2.x); the incident is one a production operator must diagnose from the evidence presented.

Symptoms

  • S3 PUT request returns SlowDown and 503
  • The user is at or over their quota
  • Other users can upload to the same bucket

Evidence

  • radosgw-admin user info shows the user quota and used
  • radosgw-admin quota get —uid=<user> confirms the quota
  • radosgw-admin log show lists the quota-related errors

Student investigation

The student follows the methodology: define the symptom, determine the impact, gather evidence, identify the component, form a hypothesis, test safely, restore, validate.

Progressive hints

  • Hint 1: check the cluster state with ceph -s first.
  • Hint 2: read ceph health detail and identify the affected PGs / OSDs / daemons.
  • Hint 3: use ceph osd tree, ceph pg dump, or ceph mds stat as the next-level diagnostic.
  • Hint 4: the root cause is documented in the frontmatter root_cause field.

Validation

The student runs the verification steps and confirms the symptom cleared.

Root cause

See the frontmatter root_cause field.

Remediation

Apply the fix from the frontmatter remediation field.

Prevention

Apply the prevention measures from the frontmatter prevention field.