图形引擎错误消息和代码 - Amazon Neptune
Amazon Web Services 文档中描述的 Amazon Web Services 服务或功能可能因区域而异。要查看适用于中国区域的差异,请参阅中国的 Amazon Web Services 服务入门

本文属于机器翻译版本。若本译文内容与英语原文存在差异,则一律以英文原文为准。

图形引擎错误消息和代码

在遇到时,Amazon Neptune 终端节点返回 Gremlin 和 SPARQL 的标准错误。

相同的终端节点也可以返回 Neptune 特定于的错误。本节介绍 Neptune 错误消息、代码和建议的操作。

注意

这些错误仅针对 Neptune 数据库集群终端节点。用于创建和修改 Neptune 资源的 APIAmazon开发工具包Amazon CLI有一组不同的常见错误。有关这些错误的更多信息,请参阅数据库集群管理 API 错误消息和代码

图形引擎错误格式

Neptune 错误消息返回相关的 HTTP 错误代码和 JSON 格式的响应。

HTTP/1.1 400 Bad Request x-amzn-RequestId: LDM6CJP8RMQ1FHKSC1RBVJFPNVV4KQNSO5AEMF66Q9ASUAAJG Content-Type: application/x-amz-json-1.0 Content-Length: 465 Date: Thu, 15 Mar 2017 23:56:23 GMT { "requestId": "0dbcded3-a9a1-4a25-b419-828c46342e47", "code": "ReadOnlyViolationException", "detailedMessage": "The request is rejected because it violates some read-only restriction, such as a designation of a replica as read-only." }

图形引擎查询错误

下表包含错误代码、消息和 HTTP 状态。

它还指示是否可以重试请求。一般而言,如果在新尝试中请求可能成功,则可以重试请求。

Neptune Service Error Code HTTP status Ok to Retry? Message
AccessDeniedException 403 No Authentication or authorization failure.
BadRequestException 400 No The request could not be completed.
BadRequestException 400 No Request size exceeds max allowed value of 157286400 bytes.
CancelledByUserException 500 Yes The request processing was cancelled by an authorized client.
ConcurrentModificationException 500 Yes The request processing did not succeed due to a modification conflict. The client should retry the request.
ConstraintViolationException 400 Yes The query engine discovered, during the execution of the request, that the completion of some operation is impossible without violating some data integrity constraints, such as persistence of in- and out-vertices while adding an edge. Such conditions are typically observed if there are concurrent modifications to the graph, and are transient. The client should retry the request.
InternalFailureException 500 Yes The request processing has failed.
无效的数字数据异常 400 No Invalid use of numeric data which cannot be represented in 64-bit storage size.
InvalidParameterException 400 No An invalid or out-of-range value was supplied for some input parameter or invalid syntax in a supplied RDF file.
MalformedQueryException 400 No The request is rejected because it contains a query that is syntactically incorrect or does not pass additional validation.
MemoryLimitExceededException 500 Yes The request processing did not succeed due to lack of memory, but can be retried when the server is less busy.
MethodNotAllowedException 405 No The request is rejected because the chosen HTTP method is not supported by the used endpoint.
MissingParameterException 400 No A required parameter for the specified action is not supplied.
QueryLimitExceededException 500 Yes The request processing did not succeed due to the lack of a limited resource, but can be retried when the server is less busy.
QueryLimitException 400 No Size of query exceeds system limit.
QueryTooLargeException 400 No The request was rejected because its body is too large.
ReadOnlyViolationException 400 No The request is rejected because it violates some read-only restriction, such as a designation of a replica as read-only.
ThrottlingException 500 Yes Rate of requests exceeds the maximum throughput. OK to retry.
TimeLimitExceededException 500 Yes The request processing timed out.
TooManyRequestsException 429 Yes The rate of requests exceeds the maximum throughput. OK to retry. IAM 身份验证仅在启用时,才会发生此异常。
UnsupportedOperationException 400 No The request uses a currently unsupported feature or construct.

IAM 身份验证错误

这些错误特定于已启用 IAM 身份验证的集群。

下表包含错误代码、消息和 HTTP 状态。

Neptune Service Error Code HTTP status Message
Incorrect IAM User/Policy 403 You do not have sufficient access to perform this action.
Incorrect or Missing Region 403 Credential should be scoped to a valid Region, not 'region'.
Incorrect or Missing Service Name 403 Credential should be scoped to correct service: 'neptune-db'.
Incorrect or Missing Host Header / Invalid Signature 403 The request signature we calculated does not match the signature you provided. Check your Amazon Secret Access Key and signing method. Consult the service documentation for details. Host header is missing or hostname is incorrect.
Missing X-Amz-Security-Token 403 'x-amz-security-token' is named as a 已签名头, but it does not exist in the HTTP request
Missing Authorization Header 403 The request did not include the required authorization header, or it was malformed.
Missing Authentication Token 403 Missing Authentication Token.
Old Date 403 Signature expired: 20181011T213907Z is now earlier than 20181011T213915Z (20181011T214415Z - 5 分钟.)
Future Date 403 Signature not yet current: 20500224T213559Z is still later than 20181108T225925Z (20181108T225425Z + 5 分钟.)
Incorrect Date Format 403 Date must be in ISO-8601 'basic format'. Got 'date'. See https://en.wikipedia.org/wiki/ISO_8601.
Unknown/Missing Access Key or Session Token 403 The security token included in the request is invalid.
Unknown/Missing Secret Key 403 The request signature we calculated does not match the signature you provided. Check your Amazon Secret Access Key and signing method. Consult the service documentation for details. Host header is missing or hostname is incorrect.
TooManyRequestsException 429 The rate of requests exceeds the maximum throughput. OK to retry.