Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

3 retries and bigger machine for writeAPI ingest #7592

Merged
merged 2 commits into from
Dec 8, 2021

Conversation

RoriCremer
Copy link
Contributor

No description provided.

@@ -292,7 +292,8 @@ task LoadData {
>>>
runtime {
docker: docker
memory: "3.75 GB"
maxRetries: 3
memory: "6 GB"
Copy link
Contributor

Choose a reason for hiding this comment

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

Do you have reason to believe we need more memory? I didn't see this in the 2k samples (and upping the memory will double the cost)

@RoriCremer RoriCremer merged commit 6410940 into ah_spike_writeapi Dec 8, 2021
@RoriCremer RoriCremer deleted the rc-beef-up-writeAPI-machine branch December 8, 2021 14:50
ahaessly pushed a commit that referenced this pull request Dec 8, 2021
ahaessly added a commit that referenced this pull request Dec 8, 2021
* use pending BQ writer
* finalize stream before commit
* update create tables for ref ranges
* fix flushing and closing
* use python to update data model
* return error if response is not 200
* add bq table creation to assign ids, cleanup
* update import with ref_ranges as default and 40 as drop state. update docs
* fix tables for duplicate check
* create separate readme for AoU Gvs workspace
* handle null vet and pet creator
* add initial test for write api
* added sample_load_status table creation
* log load status and verify sample is not loaded
* used _default stream instead (#7588)
* safety checks for restarts via preemptibles (#7590)
* add is_loaded check back to GvsCreateFilterSet
* 3 retries and bigger machine for writeAPI ingest (#7592)
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.

2 participants