[Bug] Incorrect filter appender name in broker logging configuration

Open Beginner friendly

#11,176 opened on Sep 17, 2026 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty: 1/5
Estimated time: Under an hour
Newbie friendliness: 88/100

Issue type: Bug
Clarity: Clearly specified
Activity status: Active
Tech stack: java
Domain: observability

Research direction

Open rmq.broker.logback.xml and inspect the filter and rebalance-lock appender names and routing rules. Start a broker with this configuration and exercise an orderly consumer as described, then verify that rebalance lock messages appear in lock.log rather than filter.log.

Written by the indexing model from the issue text.

Description

Before Creating the Bug Report

I found a bug, not just asking a question, which should be created in GitHub Discussions.
I have searched the GitHub Issues and GitHub Discussions of this repository and believe that this is not a duplicate.
I have confirmed that this bug belongs to the current repository, not other repositories of RocketMQ.

Runtime platform environment

All

RocketMQ version

develop

JDK Version

All

Describe the Bug

In rmq.broker.logback.xml, the filter appender is mistakenly named RocketmqRebalanceLockSiftingAppender, causing filter and rebalance lock logs to be routed incorrectly.

Steps to Reproduce

Start a broker using rmq.broker.logback.xml. Start a clustering DefaultMQPushConsumer with MessageListenerOrderly and a new consumer group, then check the queue lock logs.

What Did You Expect to See?

Rebalance lock logs in lock.log.

What Did You See Instead?

Rebalance lock logs appear in filter.log.

Additional Context

No response

Dominant language: Java
Stars: 22.6k
Forks: 12k
Avg merge: 3d 12h
Merged PRs (30d): 24

Contributor guide

Open the contributing guide

First steps

Read the whole issue, then the project's contributing guide.
Comment on the issue to say you are picking it up — it saves two people doing the same work.
Fork the repository and make your change on a branch.
Open a pull request that references the issue number.

Similar issues

[Bug] [Connector-V2] [Http] A streaming Http source never completes a checkpoint: poll_interval_millis is waited out holding the checkpoint lock Open

Difficulty 2/5 1-3 hours Newbie friendliness 78/100

apache/seatunnel#12411 · Opened Sep 20, 2026
wafv2: TagResource/UntagResource don't enforce the 50-tag limit or key/value length limits Open

Difficulty 2/5 1-3 hours Newbie friendliness 76/100

floci-io/floci#4035 · Opened Sep 20, 2026
[Bug]: 26.3 Missing directional_particles in ConsumeEffect Open

bug needs triage

Difficulty 2/5 1-3 hours Newbie friendliness 76/100

Minestom/Minestom#3375 · Opened Sep 20, 2026
The `grepIn` javadoc example never matches real XMIR, so a user who copies it silently gets no optimization Open

Difficulty 1/5 Under an hour Newbie friendliness 94/100

objectionary/hone-maven-plugin#1061 · Opened Sep 20, 2026
Store the original domain event in the Namastack outbox Open

Difficulty 2/5 1-3 hours Newbie friendliness 76/100

spring-projects/spring-modulith#1895 · Opened Sep 20, 2026

More Java issues