Closed scattym closed 5 years ago
Just encountered it myself yesterday, no idea so far. First, I'm going to implement fall-back to AT_TIMESTAMP, so it won't be a critical error and after that find out why it happens in the first place. Thanks for reporting.
Fixed in 0.2.11 The reason was following - sequence number is being split in two parts to avoid string comparison in DynamoDB. In cases when second part should have contained leading zero, that leading zero was missing. Now I store complete sequence number in DynamoDB for recovering.
Awesome, nice work. Thanks for the quick response :)
Hi,
I've been doing some failure testing around checkpointing and somehow I have got into a state where by dynamodb has a sequence number recorded that kinesis doesn't know about.
I was getting this with 0.2.10 and just upgraded to the latest git release but I am still getting the same error. Note: I didn't clear the error after upgrading. I just upgraded to see if this is an error condition your latest changes address.
Any thoughts as to what is going on?