Skip to content

Upload: wait up to 6 h for the Cloud SQL CSV import (was 20 min) - #259

Merged
fcollman merged 1 commit into
masterfrom
fix-sql-import-timeout
Oct 25, 2026
Merged

fcollman merged 1 commit into
masterfrom
fix-sql-import-timeout

Conversation

@fcollman

Copy link
Copy Markdown
Collaborator

On minnie on 2026-10-25, a 337M-row upload's Cloud SQL CSV import ran for 28.5 min and finished successfully. But upload_to_database stopped waiting after 1200 s (SQL_IMPORT_TIMEOUT_SECONDS default) and marked the job failed, so the indexes, spatial lookup and transfer never ran. Before #257, CSV processing took hours, so this wait was never the limiting step.

  • Default wait for the import is now 21600 s (6 h). SQL_IMPORT_TIMEOUT_SECONDS still overrides it. upload_to_database is acked on receipt, so a long wait can't cause a redelivery.
  • The import logs its Cloud SQL operation name when it starts.
  • A timeout message now says the operation may still be running in Cloud SQL and gives the command to check it.

🤖 Generated with Claude Code

On minnie (2026-10-25) a 337M-row upload's import ran 28.5 min and finished
fine, but upload_to_database gave up waiting after 1200 s and failed the
job, so the indexes, spatial lookup and transfer never ran. CSV processing
used to take hours, so the import's wait was never the limit before.

The default is now 21600 s (SQL_IMPORT_TIMEOUT_SECONDS still overrides it);
upload_to_database is acked on receipt, so a long wait cannot be redelivered.
The import logs its operation name when it starts, and a timeout says the
operation may still be running and how to check it.

Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
@fcollman
fcollman merged commit 6db8e91 into master Oct 25, 2026
1 check passed
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