기계 번역으로 제공되는 번역입니다. 제공된 번역과 원본 영어의 내용이 상충하는 경우에는 영어 버전이 우선합니다.
그래프 엔진 오류 메시지 및 코드
Amazon Neptune 엔드포인트는 Gremlin 및 SPARQL에 대한 표준 오류가 발생하면 해당 오류를 반환합니다.
Neptune 관련 오류도 동일한 엔드포인트에서 반환될 수 있습니다. 이 섹션에는 Neptune 오류 메시지, 코드 및 권장 작업에 대한 설명이 나와 있습니다.
참고
이 오류는 Neptune DB 클러스터 엔드포인트에만 해당됩니다. AWS SDK 및 AWS CLI로 Neptune 리소스를 생성하고 수정하기 위한 API에 서로 다른 일련의 공통 오류가 있습니다. 이러한 오류에 대한 자세한 내용은 DB Cluster Management 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. |
FailureByQueryException |
500 | Yes | Calling fail() caused request processing to fail. |
InternalFailureException |
500 | Yes | The request processing has failed. |
InvalidNumericDataException |
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. |
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 AWS 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 SignedHeader, 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 AWS 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. |
