Expose SQS redrive button to users

tnc-ca-geo / animl-frontend

A frontend web app for viewing & labeling camera trap data by The Nature Conservancy.

https://animl.camera

Other

16 stars 0 forks source link

Expose SQS redrive button to users #144

Closed nathanielrindlaub closed 9 months ago

nathanielrindlaub commented 1 year ago

@ingalls is implementing the ability for users to trigger a redrive of their batch SQS messages that failed for some reason and wound-up in the DLQ (see PR 103).

Questions:

How will the user know that the images are in the DLQ and that re-driving them might get them to be successfully processed?
How common will this actually be? Given the results of testing our current downstream inference handler and sagemaker endpoint concurrency settings I am hopeful that it will be very rare for images to fail to get inference results > 5 times (our current SQS queue redrive policy MaxRecieveCount).

nathanielrindlaub commented 1 year ago

Answer to question 1: use dead property returned from batch polling payload.

I think that makes it pretty simple to implement on the front end: if dead > 0, expose a button that makes the RedriveBatch mutation request to the api. It might warrant some instructions for the user on what "redriving" means, exactly, but maybe just "retry" is sufficient.

nathanielrindlaub commented 9 months ago

Done at #179