Sync relationship hung with error Got uncaught exception NoSuchKey the specific
Applies to
- NetApp Cloud Sync
- AWS S3
Issue
- Data broker sync shows "sync in progress" and gets hung there.
- Error seen during sync:
[2023-03-14T22:42:39.343] [ERROR] [TRANSFERRER] [6] [6604] Got uncaught exception NoSuchKey: The specified key does not exist.
at Request.extractError (/opt/netapp/databroker/node_modules/aws-sdk/lib/services/s3.js:711:35)
at Request.callListeners (/opt/netapp/databroker/node_modules/aws-sdk/lib/sequential_executor.js:106:20)
at Request.emit (/opt/netapp/databroker/node_modules/aws-sdk/lib/sequential_executor.js:78:10)
at Request.emit (/opt/netapp/databroker/node_modules/aws-sdk/lib/request.js:686:14)
at Request.transition (/opt/netapp/databroker/node_modules/aws-sdk/lib/request.js:22:10)
at AcceptorStateMachine.runTo (/opt/netapp/databroker/node_modules/aws-sdk/lib/state_machine.js:14:12)
at /opt/netapp/databroker/node_modules/aws-sdk/lib/state_machine.js:26:10
at Request.<anonymous> (/opt/netapp/databroker/node_modules/aws-sdk/lib/request.js:38:9)
at Request.<anonymous> (/opt/netapp/databroker/node_modules/aws-sdk/lib/request.js:688:12)
at Request.callListeners (/opt/netapp/databroker/node_modules/aws-sdk/lib/sequential_executor.js:116:18)
at Request.emit (/opt/netapp/databroker/node_modules/aws-sdk/lib/sequential_executor.js:78:10)
at Request.emit (/opt/netapp/databroker/node_modules/aws-sdk/lib/request.js:686:14)
at Request.transition (/opt/netapp/databroker/node_modules/aws-sdk/lib/request.js:22:10)
at AcceptorStateMachine.runTo (/opt/netapp/databroker/node_modules/aws-sdk/lib/state_machine.js:14:12)
at /opt/netapp/databroker/node_modules/aws-sdk/lib/state_machine.js:26:10
at Request.<anonymous> (/opt/netapp/databroker/node_modules/aws-sdk/lib/request.js:38:9) {
code: 'NoSuchKey',
region: null,
time: '2023-03-15T05:42:39.343Z',
requestId: 'WF1NZGQE1H04NF4B',
extendedRequestId: 'v4kRVzRioFuRg302XTmXPLeorYOoT0kJ83l2xUT0jsmTym0baVYZhGVaxPzjIb/FZtOYZgg8/mE=',
cfId: undefined,
statusCode: 404,
retryable: false,
retryDelay: 55.539524198683885
}
....
- After the above message sync goes into a hung state