Skip to content

Comments

Fix: IT may mirror huge files (#7767)#7773

Merged
dsotirho-ucsc merged 4 commits intodevelopfrom
issues/nadove-ucsc/7767-it-may-mirror-huge-files
Feb 23, 2026
Merged

Fix: IT may mirror huge files (#7767)#7773
dsotirho-ucsc merged 4 commits intodevelopfrom
issues/nadove-ucsc/7767-it-may-mirror-huge-files

Conversation

@nadove-ucsc
Copy link
Contributor

@nadove-ucsc nadove-ucsc commented Feb 12, 2026

Linked issues: #7767

Checklist

Author

  • PR is assigned to the author
  • Status of PR is In progress
  • PR is a draft
  • Target branch is develop
  • Name of PR branch matches issues/<GitHub handle of author>/<issue#>-<slug>
  • PR is linked to all issues it (partially) resolves
  • Status of linked issues is In progress
  • PR description links to linked issues
  • PR title matches1 that of a linked issue or comment in PR explains why they're different
  • PR title references all linked issues
  • For each linked issue, there is at least one commit whose title references that issue

1 when the issue title describes a problem, the corresponding PR
title is Fix: followed by the issue title

Author (partiality)

  • Added p tag to titles of partial commits
  • This PR is labeled partial or completely resolves all linked issues
  • This PR partially resolves each of the linked issues or does not have the partial label

Author (reindex)

  • Added r tag to commit title or the changes introduced by this PR will not require reindexing of any deployment
  • This PR is labeled reindex:dev or the changes introduced by it will not require reindexing of dev
  • This PR is labeled reindex:anvildev or the changes introduced by it will not require reindexing of anvildev
  • This PR is labeled reindex:anvilprod or the changes introduced by it will not require reindexing of anvilprod
  • This PR is labeled reindex:prod or the changes introduced by it will not require reindexing of prod
  • This PR is labeled reindex:partial and its description documents the specific reindexing procedure for dev, anvildev, anvilprod and prod or requires a full reindex or carries none of the labels reindex:dev, reindex:anvildev, reindex:anvilprod and reindex:prod

Author (API changes)

  • This PR and its linked issues are labeled API or this PR does not modify a REST API
  • Added a (A) tag to commit title for backwards (in)compatible changes or this PR does not modify a REST API
  • Updated REST API version number in app.py or this PR does not modify a REST API

Author (upgrading deployments)

  • Ran make docker_images.json and committed the resulting changes or this PR does not modify azul_docker_images, or any other variables referenced in the definition of that variable
  • Documented upgrading of deployments in UPGRADING.rst or this PR does not require upgrading deployments
  • Added u tag to commit title or this PR does not require upgrading deployments
  • This PR is labeled upgrade or does not require upgrading deployments
  • This PR is labeled deploy:shared or does not modify docker_images.json, and does not require deploying the shared component for any other reason
  • This PR is labeled deploy:gitlab or does not require deploying the gitlab component
  • This PR is labeled deploy:runner or does not require deploying the runner image

Author (hotfixes)

  • Added F tag to main commit title or this PR does not include permanent fix for a temporary hotfix
  • Reverted the temporary hotfixes for any linked issues or the none of the stable branches (anvilprod and prod) have temporary hotfixes for any of the issues linked to this PR

Author (before every review)

  • Rebased PR branch on develop, squashed fixups from prior reviews
  • Ran make requirements_update or this PR does not modify Dockerfile, environment, requirements*.txt, common.mk, Makefile or environment.boot
  • Added R tag to commit title or this PR does not modify requirements*.txt
  • This PR is labeled reqs or does not modify requirements*.txt
  • make integration_test passes in personal deployment or this PR does not modify functionality that could affect the IT outcome
  • PR is awaiting requested review from a peer
  • Status of PR is Review requested
  • PR is assigned to only the peer and the author

Peer reviewer (after approval)

Note that after requesting changes, the PR must be assigned to only the author.

  • Actually approved the PR
  • PR is not a draft
  • PR is awaiting requested review from system administrator
  • Status of PR is Review requested
  • PR is assigned to only the system administrator and the author

System administrator (after approval)

  • Actually approved the PR
  • Labeled linked issues as demo or no demo
  • Commented on linked issues about demo expectations or all linked issues are labeled no demo
  • Decided if PR can be labeled no sandbox
  • A comment to this PR details the completed security design review
  • PR title is appropriate as title of merge commit
  • N reviews label is accurate
  • Status of PR is Approved
  • PR is assigned to only the operator and the author

Operator

  • Checked reindex:… labels and r commit title tag
  • Checked that demo expectations are clear or all linked issues are labeled no demo
  • Squashed PR branch and rebased onto develop
  • Sanity-checked history
  • Pushed PR branch to GitHub

Operator (deploy .shared and .gitlab components)

  • Ran _select dev.shared && CI_COMMIT_REF_NAME=develop make -C terraform/shared apply_keep_unused or this PR is not labeled deploy:shared
  • Ran _select dev.gitlab && CI_COMMIT_REF_NAME=develop make -C terraform/gitlab apply or this PR is not labeled deploy:gitlab
  • Ran _select anvildev.shared && CI_COMMIT_REF_NAME=develop make -C terraform/shared apply_keep_unused or this PR is not labeled deploy:shared
  • Ran _select anvildev.gitlab && CI_COMMIT_REF_NAME=develop make -C terraform/gitlab apply or this PR is not labeled deploy:gitlab
  • Checked the items in the next section or this PR is labeled deploy:gitlab
  • PR is assigned to only the system administrator and the author or this PR is not labeled deploy:gitlab

System administrator (post-deploy of .gitlab component)

  • Background migrations for dev.gitlab are complete or this PR is not labeled deploy:gitlab
  • Background migrations for anvildev.gitlab are complete or this PR is not labeled deploy:gitlab
  • PR is assigned to only the operator and the author

Operator (deploy runner image)

  • Ran _select dev.gitlab && make -C terraform/gitlab/runner or this PR is not labeled deploy:runner
  • Ran _select anvildev.gitlab && make -C terraform/gitlab/runner or this PR is not labeled deploy:runner

Operator (sandbox build)

  • Added sandbox label or PR is labeled no sandbox
  • Pushed PR branch to GitLab dev or PR is labeled no sandbox
  • Pushed PR branch to GitLab anvildev or PR is labeled no sandbox
  • Build passes in sandbox deployment or PR is labeled no sandbox
  • Build passes in anvilbox deployment or PR is labeled no sandbox
  • Reviewed build logs for anomalies in sandbox deployment or PR is labeled no sandbox
  • Reviewed build logs for anomalies in anvilbox deployment or PR is labeled no sandbox
  • Deleted unreferenced indices in sandbox or this PR does not remove catalogs or otherwise causes unreferenced indices in sandbox
  • Deleted unreferenced indices in anvilbox or this PR does not remove catalogs or otherwise causes unreferenced indices in anvilbox
  • Started reindex in sandbox or this PR is not labeled reindex:dev
  • Started reindex in anvilbox or this PR is not labeled reindex:anvildev
  • Checked for failures in sandbox or this PR is not labeled reindex:dev
  • Checked for failures in anvilbox or this PR is not labeled reindex:anvildev

Operator (merge the branch)

  • All status checks passed and the PR is mergeable
  • The title of the merge commit starts with the title of this PR
  • Added PR # reference to merge commit title
  • Collected commit title tags in merge commit title but only included p if the PR is also labeled partial
  • Pushed merge commit to GitHub
  • Status of PR is Merged lower
  • Status of blocked issues is Triage or no issues are blocked on the linked issues

Operator (main build)

  • Pushed merge commit to GitLab dev
  • Pushed merge commit to GitLab anvildev
  • Build passes on GitLab dev
  • Reviewed build logs for anomalies on GitLab dev
  • Build passes on GitLab anvildev
  • Reviewed build logs for anomalies on GitLab anvildev
  • Ran _select dev.shared && make -C terraform/shared apply or this PR is not labeled deploy:shared
  • Ran _select anvildev.shared && make -C terraform/shared apply or this PR is not labeled deploy:shared
  • Deleted PR branch from GitHub
  • PR is assigned to only the operator
  • Deleted PR branch from GitLab dev
  • Deleted PR branch from GitLab anvildev
  • Status of linked issues is Lower, or Triage, if PR is partial

Operator (reindex)

  • Deindexed all unreferenced catalogs in dev or this PR is neither labeled reindex:partial nor reindex:dev
  • Deindexed all unreferenced catalogs in anvildev or this PR is neither labeled reindex:partial nor reindex:anvildev
  • Deindexed specific sources in dev or this PR is neither labeled reindex:partial nor reindex:dev
  • Deindexed specific sources in anvildev or this PR is neither labeled reindex:partial nor reindex:anvildev
  • Indexed specific sources in dev or this PR is neither labeled reindex:partial nor reindex:dev
  • Indexed specific sources in anvildev or this PR is neither labeled reindex:partial nor reindex:anvildev
  • Started reindex in dev or this PR does not require reindexing dev
  • Started reindex in anvildev or this PR does not require reindexing anvildev
  • Checked for, triaged and possibly requeued messages in both fail queues in dev or this PR does not require reindexing dev
  • Checked for, triaged and possibly requeued messages in both fail queues in anvildev or this PR does not require reindexing anvildev
  • Emptied fail queues in dev or this PR does not require reindexing dev
  • Emptied fail queues in anvildev or this PR does not require reindexing anvildev
  • Restarted the Data Browser pipeline for the ucsc/hca/dev branch on GitLab in dev or this PR does not require reindexing dev
  • Restarted the Data Browser pipeline for the ucsc/lungmap/dev branch on GitLab in dev or this PR does not require reindexing dev
  • Restarted deploy_browser job in the GitLab pipeline for this PR in dev or this PR does not require reindexing dev
  • Restarted the Data Browser pipeline for the ucsc/anvil/anvildev branch on GitLab in anvildev or this PR does not require reindexing anvildev
  • Restarted deploy_browser job in the GitLab pipeline for this PR in anvildev or this PR does not require reindexing anvildev

Operator (mirroring)

  • Started mirroring in dev or this PR does not require mirroring dev
  • Started mirroring in anvildev or this PR does not require mirroring anvildev
  • Checked for, triaged and possibly requeued messages in mirror fail queue in dev or this PR does not require mirroring dev
  • Checked for, triaged and possibly requeued messages in mirror fail queue in anvildev or this PR does not require mirroring anvildev
  • Emptied mirror fail queue in dev or this PR does not require mirroring dev
  • Emptied mirror fail queue in anvildev or this PR does not require mirroring anvildev

Operator

  • Propagated the deploy:shared, deploy:gitlab, deploy:runner, API, reindex:partial, reindex:anvilprod and reindex:prod labels to the next promotion PRs or this PR carries none of these labels
  • Propagated any specific instructions related to the deploy:shared, deploy:gitlab, deploy:runner, API, reindex:partial, reindex:anvilprod and reindex:prod labels, from the description of this PR to that of the next promotion PRs or this PR carries none of these labels
  • PR is assigned to no one

Shorthand for review comments

  • L line is too long
  • W line wrapping is wrong
  • Q bad quotes
  • F other formatting problem

@nadove-ucsc nadove-ucsc self-assigned this Feb 12, 2026
@nadove-ucsc nadove-ucsc linked an issue Feb 12, 2026 that may be closed by this pull request
@codecov
Copy link

codecov bot commented Feb 12, 2026

Codecov Report

❌ Patch coverage is 0% with 12 lines in your changes missing coverage. Please review.
✅ Project coverage is 85.07%. Comparing base (5479aea) to head (5d6d1bf).
⚠️ Report is 5 commits behind head on develop.

Files with missing lines Patch % Lines
test/integration_test.py 0.00% 12 Missing ⚠️
Additional details and impacted files
@@           Coverage Diff            @@
##           develop    #7773   +/-   ##
========================================
  Coverage    85.07%   85.07%           
========================================
  Files          157      157           
  Lines        23293    23293           
========================================
  Hits         19816    19816           
  Misses        3477     3477           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
  • 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

@coveralls
Copy link

coveralls commented Feb 12, 2026

Coverage Status

coverage: 85.286%. remained the same
when pulling 5d6d1bf on issues/nadove-ucsc/7767-it-may-mirror-huge-files
into 5479aea on develop.

@achave11-ucsc achave11-ucsc force-pushed the issues/nadove-ucsc/7767-it-may-mirror-huge-files branch from 3a5650d to 135223b Compare February 12, 2026 06:03
Copy link
Member

@achave11-ucsc achave11-ucsc left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Slight indentation issue (see diff below) and consider consolidating the first commit into the second one, if removing the cache is part of the fix. Or alternatively add a slight description to the body of the first commit as to why the removal may be necessary.

Index: test/integration_test.py
IDEA additional info:
Subsystem: com.intellij.openapi.diff.impl.patch.CharsetEP
<+>UTF-8
===================================================================
diff --git a/test/integration_test.py b/test/integration_test.py
--- a/test/integration_test.py	(revision 135223b9e03da58228c9d3ee5bcfac038b225ed4)
+++ b/test/integration_test.py	(date 1770875616184)
@@ -799,9 +799,9 @@
         for filters in [self._fastq_filter(catalog), {}]:
             if max_size is not None:
                 filters.update({
-                   file_size_facet: {
-                       'within': [[1, max_size]],
-                   }
+                    file_size_facet: {
+                        'within': [[1, max_size]],
+                    }
                 })
             response = self._check_endpoint(method=GET,
                                             path='/index/files',

@achave11-ucsc achave11-ucsc removed their assignment Feb 12, 2026
@nadove-ucsc nadove-ucsc force-pushed the issues/nadove-ucsc/7767-it-may-mirror-huge-files branch 2 times, most recently from dbb8ed9 to 1a04108 Compare February 13, 2026 20:39
achave11-ucsc
achave11-ucsc previously approved these changes Feb 13, 2026
Copy link
Member

@achave11-ucsc achave11-ucsc left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Approved ✅

@achave11-ucsc achave11-ucsc marked this pull request as ready for review February 13, 2026 22:49
@hannes-ucsc hannes-ucsc force-pushed the issues/nadove-ucsc/7767-it-may-mirror-huge-files branch from 1a04108 to 71dd9d4 Compare February 17, 2026 17:44
Copy link
Member

@hannes-ucsc hannes-ucsc left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Please move my refactoring commits so that they precede the main commit. Use my commit titles (minus the REVIEW prefix) but don't preserve authorship.

@hannes-ucsc hannes-ucsc added the 0 reviews [process] Lead didn't request any changes label Feb 17, 2026
@hannes-ucsc hannes-ucsc removed their assignment Feb 17, 2026
@nadove-ucsc nadove-ucsc force-pushed the issues/nadove-ucsc/7767-it-may-mirror-huge-files branch 3 times, most recently from 997a174 to 6718a81 Compare February 18, 2026 04:10
Copy link
Member

@hannes-ucsc hannes-ucsc left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

As requested in my previous review, I shouldn't be listed as the author of any commits. Reordering the commits, resolving the conflicts, and fixing any bugs constitutes a significant enough contribution to warrant a change in authorship.

@hannes-ucsc hannes-ucsc added 1 review [process] Lead requested changes once and removed 0 reviews [process] Lead didn't request any changes labels Feb 18, 2026
@nadove-ucsc nadove-ucsc force-pushed the issues/nadove-ucsc/7767-it-may-mirror-huge-files branch from 6718a81 to dfbb85a Compare February 18, 2026 23:25
@nadove-ucsc
Copy link
Contributor Author

I observed an IT failure with these changes due there being no files in the source within the requested size range. Apparently, there are sources in dcp3 where every file is larger than the mirror limit. The public source with the largest minimum file size is hca_dev_955dfc2ca8c64d04aa4d907610545d11__20210831_20210903, whose smallest file is ~3.2 GB. Therefore, we may need to increase the mirror limit to prevent these changes from causing occasional IT failures.

@nadove-ucsc
Copy link
Contributor Author

Assignee to investigate the number of files and amount of data that was mirrored during integration tests in all seven shared deployments.

@nadove-ucsc
Copy link
Contributor Author

There are three public sources in dcp3 whose smallest file is larger than the mirror limit:

tdr:bigquery:gcp:datarepo-dev-3041c2cf:hca_dev_2af52a1365cb4973b51339be38f2df3f__20210830_20210903: 2.03 GB
tdr:bigquery:gcp:datarepo-dev-40283c27:hca_dev_3a69470330844ece9abed935fd5f6748__20210901_20210903: 1.77 GB
tdr:bigquery:gcp:datarepo-dev-788c3b52:hca_dev_955dfc2ca8c64d04aa4d907610545d11__20210831_20210903: 3.19 GB

I tested this on a personal deployment with a common prefix set, which should reflect the real status of the index during IT in sandbox and dev.

@nadove-ucsc
Copy link
Contributor Author

Summary of IT across the past 7 weeks:

Deployment Total file count Total file size Max individual file size Number of IT runs (estimate) Average file count per IT Average total file size per IT
sandbox 1120 706.7 GB 55.1 GB 47 23.8 15.0 GB
dev 1992 807.7 GB 4.8 GB 54 34.3 14.9 GB
prod 392 250.2 GB 18.1 GB 14 28.0 17.9 GB
anvilbox 3978 7.0 MB 1.8 KB 39 102.0 183.3 KB
anvildev 4794 8.4 MB 1.8 KB 47 102.0 183.3 KB
hammerbox 118 110.5 GB 10.7 GB 7 16.8 15.8 GB
anvilprod 629 450.4 GB 46.4 GB 9 69.9 50.0 GB

This doesn't detect duplicate files, so the "average total file size" figure is not reliable for anvilbox or anvildev, where every file is a duplicate.

Example query for the first three columns:

fields @timestamp, @message
| filter @message like 'Worker handling message'
| filter catalog like '-it' and action = 'MirrorFileAction'
| stats count(*) as file_count, sum(file.size) / (1024 * 1024 * 1024) as file_size, max(file.size) / (1024 * 1024 * 1024)  as max_file_size

Example query for counting the number of IT runs. We mirror each source twice to test idempotence, so seeing a source only once probably means a run failed. If IT was run twice with the same source and failed both times, the count will be off.

fields @timestamp, @message
| filter @message like 'Worker handling message'
| filter catalog == 'dcp12-it' and action = 'MirrorSourceAction'
| stats ceil(count(*) / 2) as c by source.id
| stats sum(c)

@dsotirho-ucsc
Copy link
Contributor

@hannes-ucsc: "Assignee to move forward with the fix without increasing the mirror limit for the IT catalogs. This will increase the probability of IT failures in case the filter used to find a file for the individual MirrorFileAction does not yield any results. We will reevaluate the need for fixing that later when we know the impact that has."

@nadove-ucsc nadove-ucsc force-pushed the issues/nadove-ucsc/7767-it-may-mirror-huge-files branch from dfbb85a to 174ba6f Compare February 20, 2026 21:45
@hannes-ucsc
Copy link
Member

Security design review

  • Security design review completed; this PR does not
    • … affect authentication; for example:
      • OAuth 2.0 with the application (API or Swagger UI)
      • Authentication of developers with Google Cloud APIs
      • Authentication of developers with AWS APIs
      • Authentication with a GitLab instance in the system
      • Password and 2FA authentication with GitHub
      • API access token authentication with GitHub
      • Authentication with Terra
    • … affect the permissions of internal users like access to
      • Cloud resources on AWS and GCP
      • GitLab repositories, projects and groups, administration
      • an EC2 instance via SSH
      • GitHub issues, pull requests, commits, commit statuses, wikis, repositories, organizations
    • … affect the permissions of external users like access to
      • TDR snapshots
    • … affect permissions of service or bot accounts
      • Cloud resources on AWS and GCP
    • … affect audit logging in the system, like
      • adding, removing or changing a log message that represents an auditable event
      • changing the routing of log messages through the system
    • … affect monitoring of the system
    • … introduce a new software dependency like
      • Python packages on PYPI
      • Command-line utilities
      • Docker images
      • Terraform providers
    • … add an interface that exposes sensitive or confidential data at the security boundary
    • … affect the encryption of data at rest
    • … require persistence of sensitive or confidential data that might require encryption at rest
    • … require unencrypted transmission of data within the security boundary
    • … affect the network security layer; for example by
      • modifying, adding or removing firewall rules
      • modifying, adding or removing security groups
      • changing or adding a port a service, proxy or load balancer listens on
  • Documentation on any unchecked boxes is provided in comments below

@dsotirho-ucsc dsotirho-ucsc force-pushed the issues/nadove-ucsc/7767-it-may-mirror-huge-files branch from 174ba6f to 5d6d1bf Compare February 23, 2026 02:51
@dsotirho-ucsc dsotirho-ucsc added the sandbox [process] Resolution is being verified in sandbox deployment label Feb 23, 2026
@dsotirho-ucsc dsotirho-ucsc merged commit aa3d181 into develop Feb 23, 2026
10 checks passed
@dsotirho-ucsc dsotirho-ucsc deleted the issues/nadove-ucsc/7767-it-may-mirror-huge-files branch February 23, 2026 05:51
@dsotirho-ucsc dsotirho-ucsc removed their assignment Feb 23, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

1 review [process] Lead requested changes once sandbox [process] Resolution is being verified in sandbox deployment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

IT may mirror huge files

5 participants