Skip to content

fix(ENGKNOW-3353): pgor write randomly fails in sm#121

Open
gmagnu wants to merge 5 commits into
mainfrom
ENGKNOW-3353-pgor-write-randomly-fails-in-sm
Open

fix(ENGKNOW-3353): pgor write randomly fails in sm#121
gmagnu wants to merge 5 commits into
mainfrom
ENGKNOW-3353-pgor-write-randomly-fails-in-sm

Conversation

@gmagnu
Copy link
Copy Markdown
Contributor

@gmagnu gmagnu commented Jun 2, 2026

  • Fix missing files if pgor | write was overwriting existing gord.
  • Add retry in S3 start upload.
  • Dont write empty files into gord.

gmagnu and others added 5 commits May 19, 2026 19:00
…ites

pgor rewrites each partition's write target from `ref_af.gord/` (folder mode) to
a specific `ref_af.gord/<signature>.gorz` (single-file mode). ForkWrite was
creating empty gorz files for every chromosome partition that produced no rows
(e.g. gorrows with a fixed range hits only 2 of ~48 partitions). These ~46
unnecessary S3 multipart uploads caused random throttling failures.

Fix 1 (ForkWrite): skip empty-file creation when the write target is inside a
gord folder. Empty partitions in pgor writes should produce no file; the
GORDICTFOLDER step builds the dictionary from meta files and correctly excludes
empty entries.

Fix 2 (S3MultipartOutputStream): add retry loop to initiateMultipartUpload()
matching the existing uploadWithRetry pattern, so transient S3 errors during
upload initiation don't cause permanent failures.

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
return sendCreateMultipartUploadRequest(req).uploadId();
} catch (Exception e) {
throw new IOException("Failed to initiate multipart upload", e);
for (int attempt = 1; attempt <= MAX_RETRIES; attempt++) {
@github-actions
Copy link
Copy Markdown

github-actions Bot commented Jun 2, 2026

Junit Tests - Summary

4 645 tests  +1   4 468 ✅ +1   18m 14s ⏱️ +30s
  473 suites ±0     177 💤 ±0 
  473 files   ±0       0 ❌ ±0 

Results for commit b93dd5d. ± Comparison against base commit cb978ca.

♻️ This comment has been updated with latest results.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant