GetShardIterator... invalid because it did not come from this stream about amazon-kinesis-connectors

[corby]

To clear this properly, find the DynamoDB table with that appName and delete all records.
This will clear the checkpoints from the system so that it won't try to start at an invalid sequence id.

[harlow]

Found the issue. Because the app names are duplicated across sample applications:

https://github.com/awslabs/amazon-kinesis-connectors/blob/master/src/main/samples/redshiftmanifest/S3ManifestSample.properties#L2

https://github.com/awslabs/amazon-kinesis-connectors/blob/master/src/main/samples/s3/S3Sample.properties#L2

They try to use the same DynamoDB table for lookup points in the Kinesis stream. Once I renamed the app it created a new DB table and everything began working as expected.

[kevinmeredith]

I faced a similar issue with the redshiftbasic sample. Using @harlow's advice, re-naming the appName value within RedShiftBasicSample.properties resolved my issue too.

Thanks.

[darkcrawler01]

@harlow recommended to use local instance of dynamo db and kinesis for developing.

http://docs.aws.amazon.com/amazondynamodb/latest/developerguide/Tools.DynamoDBLocal.html
https://github.com/mhart/kinesalite

[landonvg]

@corby I deleted the record from DynamoDB as you suggested, now I'm getting NPE:

java.lang.NullPointerException: null
	at com.amazonaws.services.kinesis.clientlibrary.lib.worker.KinesisClientLibLeaseCoordinator.getCheckpointObject(KinesisClientLibLeaseCoordinator.java:265)
	at com.amazonaws.services.kinesis.clientlibrary.lib.worker.InitializeTask.call(InitializeTask.java:82)
	at com.amazonaws.services.kinesis.clientlibrary.lib.worker.MetricsCollectingTaskDecorator.call(MetricsCollectingTaskDecorator.java:49)
	at com.amazonaws.services.kinesis.clientlibrary.lib.worker.MetricsCollectingTaskDecorator.call(MetricsCollectingTaskDecorator.java:24)
	at java.util.concurrent.FutureTask.run(FutureTask.java:266)
	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
	at java.lang.Thread.run(Thread.java:748)

[usmanovbf]

@landonvg same exception