I have a java consumer (KCL implementation) to consume messages from 1 Kinesis stream with 2 shards.
The KCL creates 2 RecordProcessors correlates to each shard.
Then I put my machine to sleep, so JVM suspended. When wake up, the KCL library creates 2 extra RecordProcessors in addition to the original 2 RecordProcessors. So for each shard, there are 2 processors which causes confliction.
The expected behavior is not to spawn 2 new RecordProcessors while the original RecordProcessors are still in place. Where is the code in KCL that deals with the logic of spawning new RecordProcessors?