Kinesis spring binder after upgrade to 2.1.0 number of writes to SpringIntegrationLockRegistry tripled, why?

302 views Asked by At

Recently updated the spring kinesis binder from 2.0.1.RELEASE to 2.1.0 and started to see the DynamoDB table number of writes against the table SpringIntegrationLockRegistry tripled. Wondering if anyone knows what has been changed in this lib that is doing it now.

Thanks.

1

There are 1 answers

7
Artem Bilan On BEST ANSWER

I think this commit did a respective change: https://github.com/spring-projects/spring-integration-aws/commit/ac74dfd2368c5c4b74793c259312313ad21ed5f8.

So, we renew a lock every time when we are ready to consume. If it is not locked at runtime, we are not lock holders therefore don't consume.