Remaining duration of <negativenumber> insufficient to load cluster
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 35/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Stale
- Tech stack
- aws, javascript
Research direction
Start by tracing the Lambda code path that logs "Remaining duration ... insufficient to load cluster" and the call to context.getRemainingTimeInMillis(). Reproduce with the reported runtimes and timeout, then compare invocation timing with the batches table and request logs. Done means the cause of the negative value is identified and the loader no longer rejects a healthy invocation incorrectly.
Written by the indexing model from the issue text.
Description
Setup
Runtime 10.x and 12.x
Timeout 2mins 30 seconds
Error Details
2020-08-12T13:48:12.102+01:00
START RequestId: 1a5aa337-9f84-5f13-9486-f49a78bcbb46 Version: $LATEST
2020-08-12T13:48:12.115+01:00
info: Failing Batch 48e2e469-2fbd-4e98-99c6-9b028831a612 due to "Remaining duration of -89145 insufficient to load cluster"
2020-08-12T13:48:12.458+01:00
END RequestId: 1a5aa337-9f84-5f13-9486-f49a78bcbb46
REPORT RequestId: 1a5aa337-9f84-5f13-9486-f49a78bcbb46 Duration: 355.01 ms Billed Duration: 400 ms Memory Size: 256 MB Max Memory Used: 103 MB
I confirmed that the Remaining duration of -89145 insufficient to load cluster did pertain to the same request 1a5aa337-9f84-5f13-9486-f49a78bcbb46 by checking the batches table.
Expected Behaviour
Given that the Lambda timeout was well above the execution time of the request, it's expected that the function has well above adequate time to execute.
Based on the log statements above, this suggests that the call to context.getRemainingTimeInMillis() function returned -89145, 13ms after request invocation.
This occurred 3 times out of 48 batches in my test envrionment.
- Dominant language
- JavaScript
- Stars
- 595
- Forks
- 161
- PR merge metrics
- No merged PRs in 30d
Getting set up
- No Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from awslabs/aws-lambda-redshift-loader
-
Difficulty 1/5 Under an hour Newbie friendliness 68/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 32/100
awslabs/aws-lambda-redshift-loader#247 · 3 comments ·
-
Manifest missing file returned in describeBatch.jsMay be free again @IanMeyers claimed this 1390 days ago, and no pull request is open. Open
awslabs/aws-lambda-redshift-loader#244 · 4 comments · 1 assignee ·
-
Difficulty 4/5 3-5 days Newbie friendliness 25/100
awslabs/aws-lambda-redshift-loader#239 · 4 comments ·
-
Difficulty 4/5 3-5 days Newbie friendliness 20/100
awslabs/aws-lambda-redshift-loader#238 · 1 comment ·
All issues in awslabs/aws-lambda-redshift-loader
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
swc-project/swc#12516 ·
Maintainers usually reply within 1 day
-
feature-request
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
omegaup/omegaup#10323 · 1 comment ·
Maintainers usually reply within 5 days
-
area/frontend good first issue kind/cooldown
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
kestra-io/kestra#20702 · 1 comment ·
Maintainers usually reply within 1 day
-
Form-data fields are not parsed when importing a cURL requestPossibly taken @aayushbaluni claimed this today. Openbug status-new
Difficulty 2/5 1-3 hours Newbie friendliness 69/100
Maintainers usually reply within 1 day
-
bug MVP
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
saayam-for-all/webapp#1911 ·
Maintainers usually reply within 1 day