f1amingo opened a new issue, #11466: URL: https://github.com/apache/rocketmq/issues/11466
### Before Creating the Enhancement Request - [x] I have confirmed this should be classified as an enhancement. ### Summary RocketMQ enforces a fixed 120-character subscription group limit to keep generated retry topics within 255 characters. Some broker integrations already guarantee that invariant but need longer group names, so otherwise valid groups cannot be created. ### Motivation Allow broker operators to support longer subscription group names without changing the default behavior or relaxing client and gRPC validation globally. ### Describe the Solution You'd Like Add a broker configuration for the subscription group name limit. Keep the default at 120, cap the effective value at 255, and apply it only to broker-side group creation paths. Callers that raise the limit remain responsible for keeping generated retry topics within 255 characters. ### Describe Alternatives You've Considered Environment variables and JVM system properties have JVM-wide scope, require restart, and are not visible through broker configuration management. Raising the global default would weaken the existing retry-topic safeguard for all users. ### Additional Context This is a follow-up improvement to #9563. Group names over 122 characters cannot use `%DLQ%<group>` because broker writes reject topics over 127 bytes; this proposal does not change that existing storage constraint. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
