[jira] [Updated] (ROCKETMQ-66) Manage the %DLQ% Queue
[ https://issues.apache.org/jira/browse/ROCKETMQ-66?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] dongeforever updated ROCKETMQ-66: - Fix Version/s: 4.2.0-incubating > Manage the %DLQ% Queue > -- > > Key: ROCKETMQ-66 > URL: https://issues.apache.org/jira/browse/ROCKETMQ-66 > Project: Apache RocketMQ > Issue Type: Wish > Components: rocketmq-broker >Reporter: Jie.Tang >Assignee: yukon >Priority: Minor > Fix For: 4.2.0-incubating > > > I have a problem whether we need to change the %DLQ% Queue perm or not(from 2 > to 6.) > In 3.5.8 the %DLQ% Queue perm is 2,only writable,but I want to read it > because I want to know how many message is in the %DLQ% queue, which message > has problem and why it can't be consume . > I want to query the problem message(%DLQ% Queue Message) in > rocketMq-console,but because of the perm,I can't. > I need to change the perm from 2 to 6 before I query it. > Could you help me to solvle this? Thank you. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (ROCKETMQ-66) Manage the %DLQ% Queue
[ https://issues.apache.org/jira/browse/ROCKETMQ-66?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] yukon updated ROCKETMQ-66: -- Fix Version/s: 4.1.0-incubating > Manage the %DLQ% Queue > -- > > Key: ROCKETMQ-66 > URL: https://issues.apache.org/jira/browse/ROCKETMQ-66 > Project: Apache RocketMQ > Issue Type: Wish > Components: rocketmq-broker >Reporter: Jie.Tang >Assignee: yukon >Priority: Minor > Fix For: 4.1.0-incubating > > > I have a problem whether we need to change the %DLQ% Queue perm or not(from 2 > to 6.) > In 3.5.8 the %DLQ% Queue perm is 2,only writable,but I want to read it > because I want to know how many message is in the %DLQ% queue, which message > has problem and why it can't be consume . > I want to query the problem message(%DLQ% Queue Message) in > rocketMq-console,but because of the perm,I can't. > I need to change the perm from 2 to 6 before I query it. > Could you help me to solvle this? Thank you. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
