Database Group - 15.5 Planning

This page may contain information related to upcoming products, features and functionality. It is important to note that the information presented is for informational purposes only, so please do not rely on the information for purchasing or planning purposes. Just like with all projects, the items mentioned on the page are subject to change or delay, and the development, release, and timing of any products, features, or functionality remain at the sole discretion of GitLab Inc.

Capacity

In %15.5 the Database group will be at 40% capacity due to continuing capacity issues combined with planned vacations. Also, given the recent departure of @iroussos, the Group is stuck with an acting PM who happens to be on OOO when 15.5 planning needs to be finalized (gabe wrote this). PM duties are performed on a life support basis.

In good news, this is @jon_jenkins first full milestone with it

Boards

Planning

We will keep our focus on the initiatives that affect the most the availability and reliability of GitLab.com and self managed instances.

Top Priorities for 15.5

Batched Background Migrations

Who: @dfrazao-gitlab, @krasio

What: Continue our work to provide a stable, reliable framework for executing the most complex, error prone database operations. Throttling mechanics are being included in this scope for now.

Why: This final stages of this effort will help us accomplish some long term goals. First, extra safety on gitlab.com migrations from the automated throttling mechancis. Second, developer observability via chatops will reduce load on database experts by allowing members of the team to self service information about their background migrations in production. The additional batch handling work will also help our self managed customers execute migrations more reliably.

Priority topics for %15.5:

CI Partitioning Support

Who: @stomlinson @mattkasa

We're starting work aiding the CI groups to partition their tables. The two main aids we're providing are helpers for partitioning tasks, and the initial phase of Single query testing which provides assistance in identifying partitioning keys.

Priority topics for %15.5:

Database testing

Who: @mattkasa @jon_jenkins @dfrazao-gitlab

We're picking up some high priority issues with database testing in order to alleviate continued strain on database maintainers and help teams increase velocity. We're also hoping to start work on some of the single query testing work in order to aid the CI Partitioning effort in identifiying queries that lack partitioning keys.

Priority topics for %15.5:

High Severity / Priority issues

https://gitlab.com/gitlab-org/gitlab/issues/372881+

Who: TBD

We're investigating an issue during releases where we're unable to release an advisory lock at the end of migrations. typebug

Report AlloyDB usage in usage ping (gitlab-org/gitlab#367426 - closed)

Who: @jon_jenkins

We'd like to use usage data to identify instances using AlloyDB to understand usage and be aware of any ongoing issues.

Kickoff Video

Edited by Alex Ives