more gracefully report Amazon / other storage outages
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 1.1k
- Forks
- 564
- Avg merge
- 2d 2h
- Merged PRs (30d)
- 29
Description
S3 is having trouble ATM, and our server.log sez
java.io.IOException: ERROR: S3AccessIO - Failed to look up bucket my-bucket (is AWS properly configured?): We encountered an internal error. Please try again. with trailing Amazon S3 Status Code 500 and extended Request ID information.
Our Dataverse homepage contemplates its navel until the 4-retry timeout, then sez
Perhaps a more helpful or explanatory message could percolate back up to the end user in this situation, or is this something that sounds much more simple than it actually is?
Contributor 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.
Research direction
Start with the reported S3AccessIO error and trace how the Amazon S3 500 response propagates to the Dataverse homepage after retries. Reproduce an S3 outage if possible; done means the end user receives a helpful outage explanation instead of waiting for the retry timeout.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- aws, java
- Domain
- backend, cloud
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100