In Quarkus(Smallrye messaging), is the worker pool size of a @Blocking consumer tied to the consumer group/partition count of a Kafka topic?
If we have a Kafka topic setup with 8 partitions and we have a @Blocking(value="my-pool", order="false) consumer, provided the system has the resources can we set the worker pool to 16 for example. Will that create group of 16 consumers of which only half will be used or the workers/threads in the pool are completely unrelated to the consumer group thus we can have more worker processing as fast as the consumer grou; can give it to the workers?
Does Quarkus create multiple consumer instances on muti partiton topics when consumer is anotated as @Blocking?
Runing on Quarkus 2.9.0.Final