Connection limit and Created new Failed Manifest
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 25/100
- Issue type
- Feature
- Clarity
- Needs clarification
- Activity status
- Stale
- Tech stack
- aws, javascript
Research direction
Start with the Lambda failure flow described in the issue, including failureTopicARN and failedManifestKey, and review the logged connection-limit and Cluster Load Failure errors. Determine whether failed manifests are expected to be retried automatically and what completion behavior should be observable for the requester.
Written by the indexing model from the issue text.
Description
Hi, I have two kind of errors:
How I can make a way to reprocess automatically (not manually)?
I have the failureTopicARN but for this kind of error is not called right?
and I have the failedManifestKey that are saved in s3 bucket but the flow ends here.
Cluster Load Failure error: abort query on Cluster xxxxxx.amazonaws.com
...
error: abort query\n code: 1020\n context: system requested abort\n query: 10119908\n location: queryabort.hpp:62\n process: padbmaster [pid=32211]\n
...
Cluster Load Failure error: connection limit "500" exceeded for non-bootstrap users on Cluster xxxxxxx.redshift.amazonaws.com
end of lambda:
Created new Failed Manifest xxxxxx
{
"xxxxxxxxxx.redshift.amazonaws.com": {
"status": -1,
"error": {
"name": "error",
"length": 157,
"severity": "FATAL",
"code": "53300",
"file": "/home/ec2-user/padb/src/pg/src/backend/utils/init/postinit.c",
"line": "571",
"routine": "InitPostgres"
}
}
}
2019-06-04T06:06:15.613Z d4f668ac-7193-4a16-8123-0a50c4eff75c
{
"errorMessage": "error"
}
- 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 1388 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
-
chore v2
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
modelcontextprotocol/servers#5115 ·
Maintainers usually reply within 1 day
-
beginner bug good first issue
Difficulty 1/5 Under an hour Newbie friendliness 85/100
philaconvalley/website#168 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 66/100
druxt/umami.demo.druxtjs.org#527 ·
Maintainers usually reply within 9 days
-
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
NuSkooler/enigma-bbs#907 ·
Maintainers usually reply within 1 day
-
documentation good first issue
Difficulty 2/5 1-3 hours Newbie friendliness 72/100