… because of an exception while reading the messages (e.g. lock contention prevented reading) This will cause the TimesPartitionedShardReaderPolicy to keep the shard in the work queue in these cases even if the time bucket for the card is no longer current, thus preventing the shard from going idle until the time bucket loops back.
… because of an exception while reading the messages (e.g. lock contention prevented reading) This will cause the TimesPartitionedShardReaderPolicy to keep the shard in the work queue in these cases even if the time bucket for the card is no longer current, thus preventing the shard from going idle until the time bucket loops back.