Skip to content

putRecords failures

Chris Chang edited this page May 5, 2017 · 3 revisions

Kinesis will reject writes all the time. You can listen on the kinesis.putRecords listener and look for these.

The response will generally look like:

{FailedRecordCount: 3, Records: [
  {ErrorCode: InternalFailure, ErrorMessage: Internal service failure.},
  {ErrorCode: InternalFailure, ErrorMessage: Internal service failure.},
  {ErrorCode: InternalFailure, ErrorMessage: Internal service failure.}
]}

Or you may get a partial failure like:

{FailedRecordCount: 4, Records: [
  {SequenceNumber: 49570154343577991434159135485979649237735405726566711298, ShardId: shardId-000000000000},
  {SequenceNumber: 49570154343577991434159135485984484941013864243265536002, ShardId: shardId-000000000000},
  {SequenceNumber: 49570154343577991434159135485985693866833478872440242178, ShardId: shardId-000000000000},
  {ErrorCode: ProvisionedThroughputExceededException, ErrorMessage: Rate exceeded for shard shardId-000000000000 in stream demo under account 1683282299.},
  {ErrorCode: ProvisionedThroughputExceededException, ErrorMessage: Rate exceeded for shard shardId-000000000000 in stream demo under account 1683282299.},
  {ErrorCode: ProvisionedThroughputExceededException, ErrorMessage: Rate exceeded for shard shardId-000000000000 in stream demo under account 1683282299.}, 
  {ErrorCode: ProvisionedThroughputExceededException, ErrorMessage: Rate exceeded for shard shardId-000000000000 in stream demo under account 1683282299.}
]}

A complete error can also occur, and a standard error event will be emitted.

Clone this wiki locally