2025-10-30: [GPRD] Update DB duration limit in application settings

Production Change

Change Summary

Update the resource_usage_limit field in application setting via helper script glsh application_settings set resource_usage_limits on gprd.

Context: gitlab-com/gl-infra/data-access/durability/team#275

As observed in gitlab-com/gl-infra/data-access/durability/team#275 (comment 2852199559), we'd like to bump the limit for non-urgent workers on main DB duration to 60k DB seconds/minute.

Reference for the glsh application_settings script https://runbooks.gitlab.com/sidekiq/sidekiq-concurrency-limit/#updating-db-duration-limits

Change Details

Services Impacted - Rails/Sidekiq
Change Technician - @fshabir / @marcogreg
Change Reviewer - @fshabir
Scheduled Date and Time (UTC in format YYYY-MM-DD HH:MM) - 2025-10-31 7:45
Time tracking - 5 minutes
Downtime Component - NA

Important

If your change involves scheduled maintenance, add a step to set and unset maintenance mode per our runbooks. This will make sure SLA calculations adjust for the maintenance period.

Preparation

Note

The following checklists must be done in advance, before setting the label changescheduled

Prepare a PAT with admin access with api scope.

Change Reviewer checklist

C4 C3 C2 C1:

Check if the following applies:
- The scheduled day and time of execution of the change is appropriate.
- The change plan is technically accurate.
- The change plan includes estimated timing values based on previous testing.
- The change plan includes a viable rollback plan.
- The specified metrics/monitoring dashboards provide sufficient visibility for the change.

C2 C1:

Check if the following applies:
- The complexity of the plan is appropriate for the corresponding risk of the change. (i.e. the plan contains clear details).
- The change plan includes success measures for all steps/milestones during the execution.
- The change adequately minimizes risk within the environment/service.
- The performance implications of executing the change are well-understood and documented.
- The specified metrics/monitoring dashboards provide sufficient visibility for the change.
  - If not, is it possible (or necessary) to make changes to observability platforms for added visibility?
- The change has a primary and secondary SRE with knowledge of the details available during the change window.
- The change window has been agreed with Release Managers in advance of the change. If the change is planned for APAC hours, this issue has an agreed pre-change approval.
- The labels blocks deployments and/or blocks feature-flags are applied as necessary.

Change Technician checklist

Detailed steps for the change

Pre-execution steps

Note

The following steps should be done right at the scheduled time of the change request. The preparation steps are listed below.

Make sure all tasks in Change Technician checklist are done
For C1 and C2 change issues, the SRE on-call has been informed prior to change being rolled out. (Search the PagerDuty schedule for "SRE 8-hour" to find who will be on-call at the scheduled day and time. SREs on-call must be informed of plannable C1 changes at least 2 weeks in advance.)
- The SRE on-call provided approval with the eoc_approved label on the issue.
For C1, C2, or blocks deployments change issues, Release managers have been informed prior to change being rolled out. (In #production channel, mention @release-managers and this issue and await their acknowledgment.)
There are currently no active incidents that are severity1 or severity2
If the change involves doing maintenance on a database host, an appropriate silence targeting the host(s) should be added for the duration of the change.

Change steps - steps to take to execute the change

Estimated Time to Complete (mins) - Estimated Time to Complete in Minutes

Set label changein-progress /label ~change::in-progress

Prepare the following JSON file

❯ cat gprd_rules.json | jq .
{
  "rules": [
    {
      "name": "main_db_duration_limit_per_worker",
      "resource_key": "db_main_duration_s",
      "metadata": {
        "db_config_name": "main"
      },
      "scopes": [
        "worker_name"
      ],
      "rules": [
        {
          "selector": "urgency=high",
          "threshold": 100000,
          "interval": 60
        },
        {
          "selector": "*",
          "threshold": 60000,
          "interval": 60
        }
      ]
    },
    {
      "name": "ci_db_duration_limit_per_worker",
      "resource_key": "db_ci_duration_s",
      "metadata": {
        "db_config_name": "ci"
      },
      "scopes": [
        "worker_name"
      ],
      "rules": [
        {
          "selector": "urgency=high",
          "threshold": 100000,
          "interval": 60
        },
        {
          "selector": "*",
          "threshold": 20000,
          "interval": 60
        }
      ]
    },
    {
      "name": "sec_db_duration_limit_per_worker",
      "resource_key": "db_sec_duration_s",
      "metadata": {
        "db_config_name": "sec"
      },
      "scopes": [
        "worker_name"
      ],
      "rules": [
        {
          "selector": "urgency=high",
          "threshold": 100000,
          "interval": 60
        },
        {
          "selector": "*",
          "threshold": 20000,
          "interval": 60
        }
      ]
    }
  ]
}

Fetch latest master/main for runbooks repo to get updated glsh scripts.
Update the field with the following script, and follow the prompts by the script accordingly.
```
glsh application_settings set resource_usage_limits -e gprd -f gprd_rules.json
```

Confirm the values again with get

glsh application_settings get resource_usage_limits -e gprd

Set label changecomplete /label ~change::complete

Rollback

Rollback steps - steps to be taken in the event of a need to rollback this change

Estimated Time to Complete (mins) - 5 minutes

Prepare the following JSON file:

❯ cat gprd_rules.json | jq .
{
  "rules": [
    {
      "name": "main_db_duration_limit_per_worker",
      "resource_key": "db_main_duration_s",
      "metadata": {
        "db_config_name": "main"
      },
      "scopes": [
        "worker_name"
      ],
      "rules": [
        {
          "selector": "urgency=high",
          "threshold": 100000,
          "interval": 60
        },
        {
          "selector": "*",
          "threshold": 20000,
          "interval": 60
        }
      ]
    },
    {
      "name": "ci_db_duration_limit_per_worker",
      "resource_key": "db_ci_duration_s",
      "metadata": {
        "db_config_name": "ci"
      },
      "scopes": [
        "worker_name"
      ],
      "rules": [
        {
          "selector": "urgency=high",
          "threshold": 100000,
          "interval": 60
        },
        {
          "selector": "*",
          "threshold": 20000,
          "interval": 60
        }
      ]
    },
    {
      "name": "sec_db_duration_limit_per_worker",
      "resource_key": "db_sec_duration_s",
      "metadata": {
        "db_config_name": "sec"
      },
      "scopes": [
        "worker_name"
      ],
      "rules": [
        {
          "selector": "urgency=high",
          "threshold": 100000,
          "interval": 60
        },
        {
          "selector": "*",
          "threshold": 20000,
          "interval": 60
        }
      ]
    }
  ]
}

glsh application_settings set resource_usage_limits -e gprd -f gprd_rules.json
Set label changeaborted /label ~change::aborted

Monitoring

Key metrics to observe

Metric: NA
- Location:
- What changes to this metric should prompt a rollback:

Edited Oct 31, 2025 by Furhan Shabir