You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Dec 16, 2025. It is now read-only.
When I set up a static shard distribution for more than 1 instances by specifying both instanceIndex and instanceCount for a kinesis with a on-deman model enabled, when resharding happened in that kinese, the rebalacing does not happen at KinesisMessageDrivenChannelAdapter, but got stoped. And for those new created shards, no instances consume messages from them.
Configuration as below -
For Server1 -
spring:
cloud:
stream:
instanceCount: 2
instanceIndex: 0
For Server2 -
spring:
cloud:
stream:
instanceCount: 2
instanceIndex: 1
Logs -
2023-10-17 10:30:18,570 INFO [-kinesis-dispatcher-1] o.s.c.l.LogAccessor:Stopping the [ShardConsumer{shardOffset=KinesisShardOffset{iteratorType=LATEST,
sequenceNumber='null', timestamp=null, stream='test-kinesis', shard='shardId-000000000000', reset=false}, state=STOP}] on the checkpoint [9223372036854775807] because the shard has been CLOSED and exhausted.
When I set up a static shard distribution for more than 1 instances by specifying both instanceIndex and instanceCount for a kinesis with a on-deman model enabled, when resharding happened in that kinese, the rebalacing does not happen at KinesisMessageDrivenChannelAdapter, but got stoped. And for those new created shards, no instances consume messages from them.
Configuration as below -
For Server1 -
spring:
cloud:
stream:
instanceCount: 2
instanceIndex: 0
For Server2 -
spring:
cloud:
stream:
instanceCount: 2
instanceIndex: 1
Logs -
2023-10-17 10:30:18,570 INFO [-kinesis-dispatcher-1] o.s.c.l.LogAccessor:Stopping the [ShardConsumer{shardOffset=KinesisShardOffset{iteratorType=LATEST,
sequenceNumber='null', timestamp=null, stream='test-kinesis', shard='shardId-000000000000', reset=false}, state=STOP}] on the checkpoint [9223372036854775807] because the shard has been CLOSED and exhausted.