Database Group Triage for week ending 2023-08-18
About
This issue is used by groupdatabase to triage issues and make sure they get properly assigned and prioritized. Each week, a bot will look up the old issue, pick the next assignee in the list, and submit a new issue with a list of any issues that may need attention from the team.
Process
-
Review any issues identified for triage -
Post any questions or pressing issues to the database group meeting doc -
Post a comment on the database group status issue For triage this week there were 1 issues in need of triage, 0 issues without throughput labels, and 6 other database issues reviewed.
<link to this issue>
databasetriage)
Issues needing triage (LabeledFor each issue below:
- If the issue needs further investigation, spend up to 1 hour of investigating or fixing the issue.
- If the issue is a typebug, assign it one of severity1, severity2, severity3, or severity4
- Document any findings you make in a comment on the issue, and if the issue still needs additional work or refinement, consider looping in
@alexives
and@rogerwoo
to help with scheduling and priority. - If the issue is incomplete, labeled ~"workflow::scheduled", and will take more than an hour to fix, remove databasetriage
database
Recent issues labeledFor each issue below:
- If the issue has no
group
label, consider if it should be addressed by groupdatabase and if so label it. - If the issue has a group, and you think they may need assistance from us:
- If the issue needs further investigation, add databasetriage and spend up to 1 hour of investigating the issue.
- Document any findings you make in a comment on the issue, and if the issue still needs additional work or refinement, consider looping in
@alexives
and/or@rogerwoo
-
groupthreat insights Database 2/2: Add hasMergeRequest filter to VulnerabilityReport -
~"group::not_owned" Upgrade fails: 16.1.x -> 16.2.x (PG::UndefinedColumn: ERROR: column "id_convert_to_bigint" of relation "ci_build_needs" does not exist) -
~"group::authentication and authorization" Remove application_settings.relay_state_domain_allowlist
column -
groupoptimize ClickHouse: Add queries to Rails logs -
grouppipeline execution Add an index on merge_trains that filters on status before target_branch -
grouprunner Filtering by runner upgrade status should rely on runner manager versions
@gitlab-org/database-team
Recent mentions of For each mention below:
- If the item already has an adequate response, move on to the next
- If the mention is from someone looking to provide feedback on database review, and nobody has responded yet, set up a coffee chat with them and make a note in the thread that you did. Record feedback in the feedback issue.
- If you know how to respond to the comment, post a response
- If you don't know how, redirect with a specific mention to someone who may be able to respond
-
@rogerwoo
mentioned the team on [DRAFT] Database Group - 16.4 Planning -
@alexives
mentioned the team on Enumerated List of ongoing and upcoming projects 16.4 -
@l.rosa
mentioned the team on Avoid name collision between migrations
Customer Issue Hand-offs
@mattkasa please add a comment providing any hand-off details to @praba.m7n about the following issues. If an issue won't be handed off, make a comment on this issue.
- ActionView::Template::Error (key not found: "internal"): after upgrade to 15.8.6~"Help group::Database"
- Patroni failover breaks cluster and requires a manual restart on PgBouncer hosts~"Help group::Database"
- Questions regarding fine tuning PgBouncer connection pooling and PSQL max connections~"Help group::Database"
@alexives if @praba.m7n isn't available this week, please reassign to @stomlinson
cc @rogerwoo