AWS Neptune returning InternalFailureException

Question

I was trying to do iterate over AWS Neptune graph and do some manipulation from my Lambda function but I am getting an error of

2023-05-22T01:34:38.352Z	f8bfa54b-8230-47eb-a5ab-be56e8ae6190	ERROR	Error: ResponseError: Server error: {
    "requestId": "5d69c1d4-5db0-4632-8604-50eab55b9c16",
    "code": "InternalFailureException"
} (599)
    at Connection._handleMessage (/var/task/node_modules/gremlin/lib/driver/connection.js:341:9)
    at WebSocket. (/var/task/node_modules/gremlin/lib/driver/connection.js:144:43)
    at WebSocket.emit (node:events:513:28)
    at Receiver.receiverOnMessage (/var/task/node_modules/ws/lib/websocket.js:1184:20)
    at Receiver.emit (node:events:513:28)
    at Receiver.dataMessage (/var/task/node_modules/ws/lib/receiver.js:526:14)
    at /var/task/node_modules/ws/lib/receiver.js:492:23
    at /var/task/node_modules/ws/lib/permessage-deflate.js:309:9
    at /var/task/node_modules/ws/lib/permessage-deflate.js:392:7
    at afterWrite (node:internal/streams/writable:500:5) {
  statusCode: 599,
  statusMessage: '{"rquestId":"5d69c1d4-5db0-4632-8604-50eab55b9c16","code":"InternalFailureException"}',
  statusAttributes: Map(0) {}
}
I have no idea what the problem is , the code is correct and clean .

Answer

InternalFailureExceptions are generally a catch-all for unexpected error conditions in Neptune. These are not always server-side error conditions, but can sometimes be caused by a poorly formed query. If you see an InternalFailureException, please open an AWS Support case with the details of your cluster so that we can assess the situation and determine the cause of the failure.

For other users that may see this thread in the future, please open a support case or reach out to neptune-reppost@amazon.com with details where/when you are seeing an InternalFailureException.

AWS Neptune returning InternalFailureException

相關內容