Saltar al contenido

dynamodb us-east-1 DynamoDB:InternalServerErrorException

0

Is there a problem with dynamodb in us-east-1? i've been getting the following intermittent errors for the last hour or two:

ApolloError: GraphQL error: Service returned error code InternalServerError (Service: DynamoDb, Status Code: 500, Request ID: 7FDI1HEE3LJCU9NH14LRD49KORVV4KQNSO5AEMVJF66Q9ASUAAJG) (SDK Attempt Count: 2)
at new ApolloError (/app/node_modules/aws-appsync/node_modules/apollo-client/bundle.umd.js:85:32)
at new ApolloError (/app/node_modules/aws-appsync/node_modules/apollo-client/bundle.umd.js:85:32)
at /app/node_modules/aws-appsync/node_modules/apollo-client/bundle.umd.js:1039:45
at /app/node_modules/aws-appsync/node_modules/apollo-client/bundle.umd.js:1411:21
at Array.forEach (<anonymous>)
at /app/node_modules/aws-appsync/node_modules/apollo-client/bundle.umd.js:1410:22
at Map.forEach (<anonymous>)
at QueryManager.broadcastQueries (/app/node_modules/aws-appsync/node_modules/apollo-client/bundle.umd.js:1405:26)
at Object.next (/app/node_modules/aws-appsync/node_modules/apollo-client/bundle.umd.js:1462:35)
at notifySubscription (/app/node_modules/zen-observable/lib/Observable.js:135:18)
at onNotify (/app/node_modules/zen-observable/lib/Observable.js:179:3)
at SubscriptionObserver.next (/app/node_modules/zen-observable/lib/Observable.js:235:7)
at /app/node_modules/apollo-link-dedup/lib/dedupLink.js:33:81
at Set.forEach (<anonymous>)
at Object.next (/app/node_modules/apollo-link-dedup/lib/dedupLink.js:33:45)
at notifySubscription (/app/node_modules/zen-observable/lib/Observable.js:135:18)
at onNotify (/app/node_modules/zen-observable/lib/Observable.js:179:3)
at SubscriptionObserver.next (/app/node_modules/zen-observable/lib/Observable.js:235:7)
... collapsed 6 duplicate lines matching above 3 lines 2 times...
at RetryableOperation.onNext [as next] (/app/node_modules/apollo-link-retry/lib/bundle.umd.js:110:30)
at notifySubscription (/app/node_modules/zen-observable/lib/Observable.js:135:18)
at onNotify (/app/node_modules/zen-observable/lib/Observable.js:179:3)
at SubscriptionObserver.next (/app/node_modules/zen-observable/lib/Observable.js:235:7)
... collapsed 6 duplicate lines matching above 3 lines 2 times...
at /app/node_modules/apollo-link-http/lib/bundle.umd.js:127:30
at process.processTicksAndRejections (node:internal/process/task_queues:105:5) {
graphQLErrors: [
{
path: [Array],
data: null,
errorType: 'DynamoDB:InternalServerErrorException',
errorInfo: null,
locations: [Array],
message: 'Service returned error code InternalServerError (Service: DynamoDb, Status Code: 500, Request ID: 7FDI1HEE3LJCU9NH14LRD49KORVV4KQNSO5AEMVJF66Q9ASUAAJG) (SDK Attempt Count: 2)'
}
],
networkError: null,
extraInfo: undefined
}
/app/_utils.js:118
throw new Error(err.message)

preguntada hace 9 meses96 visualizaciones

2 Respuestas
1

Hi Daniel,

Internal server errors (HTTP 500) in Amazon DynamoDB indicate that the service was unable to process the request. These errors can occur due to several underlying reasons, including transient network issues within the DynamoDB fleet, infrastructure problems, or storage-node–related failures.

When encountering these errors, it is recommended to:

  • Check the AWS Health Dashboard for any ongoing service disruptions.
  • If no issues are reported, raise an AWS Support ticket for further investigation.

Note: I did not find any service-related issues reported in the AWS Health Dashboard at the time of checking.

Ref: https://docs.aws.amazon.com/amazondynamodb/latest/developerguide/TroubleshootingInternalServerErrors.html

respondido hace 9 meses

AWS
EXPERTO

revisado hace 8 meses

0

For health status of AWS services see https://health.aws.amazon.com/health/status. If you are having specific problems, your best move is to open a support case.

AWS
EXPERTO

respondido hace 8 meses

No has iniciado sesión. Iniciar sesión para publicar una respuesta.

Una buena respuesta responde claramente a la pregunta, proporciona comentarios constructivos y fomenta el crecimiento profesional en la persona que hace la pregunta.