Each ConsumeMessageThread should have different thread name

FEATURE REQUEST

1. Please describe the feature you are requesting. I am looking for a feature of ConsumeMessageThread for different Consumer has different ThreadName.

2. Provide any additional detail on your proposed use case for this feature. For example, when two PushConsumer started in the same process, the client will create two ThreadPool for message consumption. But Threads in the two pools share the same thread names, thus cause confusion and increase the complexity of resolving problems.

3. Indicate the importance of this issue to you (blocker, must-have, should-have, nice-to-have). Are you currently using any workarounds to address this issue? Nice to have. Not any workarounds.

[ahuazhu]

@duhenglucky Thanks for your reply. In some scenarios, it’s necessary to create multi consumers. For example, suppose we have messages in two topics. One contains fewer messages, but each one takes a long consumption time, and the other is the opposite. In such a situation, subscribing these topics in one consumer maybe not a good choice. Because the few but heavy messages may block all ConsumeThreads, which leads to the another topic consumption latency. Here we need two isolated thread pools (consumer) for these two topics. For your second question, I think ConsumerGroup as a part of ConsumeThread name is more intuitive than instance.

[ahuazhu]

What about if modifying the code in ConsumeMessageConcurrentlyService.java from

            this.consumeExecutor = new ThreadPoolExecutor(
            this.defaultMQPushConsumer.getConsumeThreadMin(),
            this.defaultMQPushConsumer.getConsumeThreadMax(),
            1000 * 60,
            TimeUnit.MILLISECONDS,
            this.consumeRequestQueue,
            new ThreadFactoryImpl("ConsumeMessageThread_"));

        this.scheduledExecutorService = Executors.newSingleThreadScheduledExecutor(new ThreadFactoryImpl("ConsumeMessageScheduledThread_"));
        this.cleanExpireMsgExecutors = Executors.newSingleThreadScheduledExecutor(new ThreadFactoryImpl("CleanExpireMsgScheduledThread_"));

to

            this.consumeExecutor = new ThreadPoolExecutor(
            this.defaultMQPushConsumer.getConsumeThreadMin(),
            this.defaultMQPushConsumer.getConsumeThreadMax(),
            1000 * 60,
            TimeUnit.MILLISECONDS,
            this.consumeRequestQueue,
            new ThreadFactoryImpl("ConsumeMessageThread_" + this.consumerGroup + "_"));

        this.scheduledExecutorService = Executors.newSingleThreadScheduledExecutor(new ThreadFactoryImpl("ConsumeMessageScheduledThread_" + this.consumerGroup + "_"));
        this.cleanExpireMsgExecutors = Executors.newSingleThreadScheduledExecutor(new ThreadFactoryImpl("CleanExpireMsgScheduledThread_" + this.consumerGroup + "_"));