Skip to content

ENH: increase timeout on spice query and batch starter lambda - #942

Merged
tech3371 merged 2 commits into
IMAP-Science-Operations-Center:devfrom
tech3371:lambda_timeout
Oct 16, 2025
Merged

ENH: increase timeout on spice query and batch starter lambda#942
tech3371 merged 2 commits into
IMAP-Science-Operations-Center:devfrom
tech3371:lambda_timeout

Conversation

@tech3371

@tech3371 tech3371 commented Oct 16, 2025

Copy link
Copy Markdown
Contributor

Change Summary

Overview

Increase timeout on those lambda since it can take longer than 1min

@tech3371 tech3371 changed the title ENH: increase timeout on spice query and batch starter lambda to avoi… ENH: increase timeout on spice query and batch starter lambda Oct 16, 2025
@greglucas

Copy link
Copy Markdown
Collaborator

😮 I'm mildly against this. Do we know what is taking the time? I hate APIs that take longer than a few seconds and we are going from 1 minute to 5!

@lacoak21

Copy link
Copy Markdown
Contributor

😮 I'm mildly against this. Do we know what is taking the time? I hate APIs that take longer than a few seconds and we are going from 1 minute to 5!

It was timing out on the spice metakernel api call. I was trying to reprocess the pointing-attitude job with this command:

imap-data-access --api-key <key> --url https://api.imap-mission.com/api-key reprocess --data-level l1a --instrument spacecraft --descriptor pointing-attitude --start-date 20250901 --end-date 20251014

@tech3371

Copy link
Copy Markdown
Contributor Author

Greg, do you want to try shorter than 5min? and then try again in the future?

@greglucas

Copy link
Copy Markdown
Collaborator

I think it is fine to get over hurdles, but we need a ticket to improve these in the future I think.

I'm guessing this is improvement in the code which might take a little while to debug and figure out. But I'm almost positive this should be doable in a few seconds (maybe I'm naive, but I don't see how it should take minutes)

@tech3371
tech3371 merged commit 2935bfa into IMAP-Science-Operations-Center:dev Oct 16, 2025
2 checks passed
@greglucas

Copy link
Copy Markdown
Collaborator

It was timing out on the spice metakernel api call. I was trying to reprocess the pointing-attitude job with this command:

imap-data-access --api-key --url https://api.imap-mission.com/api-key reprocess --data-level l1a --instrument spacecraft --descriptor pointing-attitude --start-date 20250901 --end-date 20251014

@lacoak21 are these API calls from local or remote? Is this another area that we should not be calling an external API but rather the functions we already have available through local imports.

@greglucas

Copy link
Copy Markdown
Collaborator

Also, you can drop this now with version 0.37 :) --url https://api.imap-mission.com/api-key

@lacoak21

Copy link
Copy Markdown
Contributor

I just checked and it is directly calling the metakernel lambda handler

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.

3 participants