Re: [I] [Bug] 分层存储激活时,当向新创建的 Topic 中生产消息,能否正常转储取决于任一批消息生产的时间点是否正确 [rocketmq]

2024-04-26 Thread via GitHub
bxfjb commented on issue #8065: URL: https://github.com/apache/rocketmq/issues/8065#issuecomment-2078832939 > 分析的很具体,依次回复几个问题: > > 1. 对于冷存储中的 CommitLog 可以从 0 开始,而 cq 必须与本地位点对齐,只能在 dispatch 时才能确定初始化的位点,因此不会在 factory 中初始化指定,这一点也是为了保证与旧存储格式的兼容。 > 2. fileSegment.getMaxTimestamp() !=

[GH] (rocketmq): Workflow run "Build and Run Tests by Maven" failed!

2024-04-26 Thread GitBox
The GitHub Actions job "Build and Run Tests by Maven" on rocketmq.git has failed. Run started by GitHub user hanmz (triggered by lizhimins). Head commit for run: 9cf519e1beaa6f22c50164f294faa6ca907c5714 / hanmz Fix some typos in DefaultLitePullConsumer and LitePullConsumer Report URL:

Re: [I] [Bug] consumerManagerThreadPoolQueueCapacity has settings but is not used [rocketmq]

2024-04-26 Thread via GitHub
frinda commented on issue #8057: URL: https://github.com/apache/rocketmq/issues/8057#issuecomment-2078825296 I haven't had a problem because of this. but this may cause OOM -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and

[I] [Enhancement] ServiceThread类中hasNotified是不是不需要volatile了? [rocketmq]

2024-04-26 Thread via GitHub
KimZhangJinMing opened a new issue, #8069: URL: https://github.com/apache/rocketmq/issues/8069 ### Before Creating the Enhancement Request - [X] I have confirmed that this should be classified as an enhancement rather than a bug/feature. ### Summary In class

[GH] (rocketmq): Workflow run "Coverage" failed!

2024-04-26 Thread GitBox
The GitHub Actions job "Coverage" on rocketmq.git has failed. Run started by GitHub user bxfjb (triggered by lizhimins). Head commit for run: 324e8a06be985bae9f491b5b6337592f857c48f3 / zhaoyuhan fix tiered store delete empty topic NPE Report URL:

[GH] (rocketmq): Workflow run "Coverage" failed!

2024-04-26 Thread GitBox
The GitHub Actions job "Coverage" on rocketmq.git has failed. Run started by GitHub user hanmz (triggered by lizhimins). Head commit for run: 9cf519e1beaa6f22c50164f294faa6ca907c5714 / hanmz Fix some typos in DefaultLitePullConsumer and LitePullConsumer Report URL:

[GH] (rocketmq): Workflow run "Build and Run Tests by Maven" failed!

2024-04-26 Thread GitBox
The GitHub Actions job "Build and Run Tests by Maven" on rocketmq.git has failed. Run started by GitHub user fujian-zfj (triggered by caigy). Head commit for run: b987b66f3ea44ffba3ee543052150fea70927c96 / zfj fix npe Report URL: https://github.com/apache/rocketmq/actions/runs/8816909913

[GH] (rocketmq): Workflow run "Build and Run Tests by Maven" failed!

2024-04-26 Thread GitBox
The GitHub Actions job "Build and Run Tests by Maven" on rocketmq.git has failed. Run started by GitHub user bxfjb (triggered by lizhimins). Head commit for run: 324e8a06be985bae9f491b5b6337592f857c48f3 / zhaoyuhan fix tiered store delete empty topic NPE Report URL:

Re: [I] [Enhancement] Support tiered storage run in primary/backup mode [rocketmq]

2024-04-26 Thread via GitHub
bxfjb commented on issue #8066: URL: https://github.com/apache/rocketmq/issues/8066#issuecomment-2078791081 > 当前分级存储对主备模式和 DLedger 的支持不够完善,非常欢迎你把他作为新的特性来贡献。从设计方案上来说,并不只是 schedule 任务判断一下即可,metadata store 中元数据的同步,以及 broker container 模式下的截断等问题都是需要考虑和讨论的,从目前的 pr 来看考虑不够完善。 是的,这个 pr

Re: [I] [Bug] 当分层存储运行在对象存储上时,从节点不应向冷存中写入数据 [rocketmq]

2024-04-26 Thread via GitHub
lizhimins commented on issue #8066: URL: https://github.com/apache/rocketmq/issues/8066#issuecomment-2078700660 当前分级存储对主备模式和 DLedger 的支持不够完善,非常欢迎你把他作为新的特性来贡献。并不只是 schedule 任务判断一下即可,metadata store 中元数据的同步,以及 broker container 模式下的截断等问题都是需要考虑和讨论的。从目前的 pr 来看考虑不够完善。 -- This is an automated

[GH] (rocketmq): Workflow run "Build and Run Tests by Maven" failed!

2024-04-26 Thread GitBox
The GitHub Actions job "Build and Run Tests by Maven" on rocketmq.git has failed. Run started by GitHub user HScarb (triggered by HScarb). Head commit for run: 941d3071fee5812ba808f3148f03ebbc5eaf0704 / Scarb build: fix coverage workflow Report URL:

Re: [I] 程序启动了两个Producer,程序退出时,关闭第二个Producer时 coredump [rocketmq-client-cpp]

2024-04-26 Thread via GitHub
HUHANK commented on issue #468: URL: https://github.com/apache/rocketmq-client-cpp/issues/468#issuecomment-2078743260 @ifplusor 确实如您所说,设置不同的instance name之后程序停止就不会崩溃了,正常了,非常感谢!  -- This is an automated message from the Apache Git Service. To respond to the message, please log on to

Re: [I] [Bug] 分层存储激活时,当向新创建的 Topic 中生产消息,能否正常转储取决于任一批消息生产的时间点是否正确 [rocketmq]

2024-04-26 Thread via GitHub
lizhimins commented on issue #8065: URL: https://github.com/apache/rocketmq/issues/8065#issuecomment-2078745606 分析的很具体,依次回复几个问题: 1. 对于冷存储中的 CommitLog 可以从 0 开始,而 cq 必须与本地位点对齐,只能在 dispatch 时才能确定初始化的位点,因此不会在 factory 中初始化指定,这一点也是为了保证与旧存储格式的兼容。 2. fileSegment.getMaxTimestamp() !=

[GH] (rocketmq): Workflow run "Build and Run Tests by Maven" failed!

2024-04-26 Thread GitBox
The GitHub Actions job "Build and Run Tests by Maven" on rocketmq.git has failed. Run started by GitHub user HScarb (triggered by HScarb). Head commit for run: fca41c23da1592da1be7e3e06a4c781f2ec627db / Scarb build: fix coverage workflow Report URL:

Re: [I] JDK17 + Springboot3 +rocketmq-spring-boot-starter2.2.3启动报错 [rocketmq-spring]

2024-04-26 Thread via GitHub
yanglaiyi commented on issue #603: URL: https://github.com/apache/rocketmq-spring/issues/603#issuecomment-2078690419 好的,十分感谢您的建议。 -- 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

[GH] (rocketmq): Workflow run "E2E test for pull request" failed!

2024-04-26 Thread GitBox
The GitHub Actions job "E2E test for pull request" on rocketmq.git has failed. Run started by GitHub user HScarb (triggered by HScarb). Head commit for run: b37d283793f4d77ec787a7e6292838783db54a8b / mxsm [ISSUE #8044]Add Override annotation for AllocateMappedFileService#run (#8045) Report

Re: [I] 程序启动了两个Producer,程序退出时,关闭第二个Producer时 coredump [rocketmq-client-cpp]

2024-04-26 Thread via GitHub
HUHANK closed issue #468: 程序启动了两个Producer,程序退出时,关闭第二个Producer时 coredump URL: https://github.com/apache/rocketmq-client-cpp/issues/468 -- 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

[I] [Bug] rocketmq::Producer对象析构crash [rocketmq-clients]

2024-04-26 Thread via GitHub
bluevideo opened a new issue, #738: URL: https://github.com/apache/rocketmq-clients/issues/738 ### Before Creating the Bug Report - [X] I found a bug, not just asking a question, which should be created in [GitHub Discussions](https://github.com/apache/rocketmq-clients/discussions).

[GH] (rocketmq): Workflow run "E2E test for pull request" failed!

2024-04-26 Thread GitBox
The GitHub Actions job "E2E test for pull request" on rocketmq.git has failed. Run started by GitHub user HScarb (triggered by HScarb). Head commit for run: b37d283793f4d77ec787a7e6292838783db54a8b / mxsm [ISSUE #8044]Add Override annotation for AllocateMappedFileService#run (#8045) Report

Re: [PR] [#ISSUE 8066] Fix tiered storage skip dispatch and destroy when broker role is Slave [rocketmq]

2024-04-26 Thread via GitHub
bxfjb closed pull request #8067: [#ISSUE 8066] Fix tiered storage skip dispatch and destroy when broker role is Slave URL: https://github.com/apache/rocketmq/pull/8067 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the

Re: [PR] [ISSUE #8070] Optimize the submitConsumeRequest and remove unnecessary exception catching [rocketmq]

2024-04-26 Thread via GitHub
biningo commented on PR #8071: URL: https://github.com/apache/rocketmq/pull/8071#issuecomment-2079358580 If the number of messages or the consumeBatchSize is 0, it will work fine. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to

Re: [PR] [ISSUE #8070] Optimize the submitConsumeRequest and remove unnecessary exception catching [rocketmq]

2024-04-26 Thread via GitHub
biningo commented on PR #8071: URL: https://github.com/apache/rocketmq/pull/8071#issuecomment-2079365193 In submitConsumeRequest submitConsumeRequestLater is unnecessary. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and

Re: [PR] [ISSUE #8053] Return SYSTEM_BUSY if PutMessageStatus is OS_PAGE_CACHE_BUSY [rocketmq]

2024-04-26 Thread via GitHub
biningo commented on PR #8054: URL: https://github.com/apache/rocketmq/pull/8054#issuecomment-2079381218 > It is correct to change the response code, but we need more discussion on whether client should retry on this scenario. Personally I think the client should retry by default to avoid

Re: [I] Use MixAll.isPropertyValid() in Validators.checkBrokerConfig() [rocketmq]

2024-04-26 Thread via GitHub
github-actions[bot] closed issue #6550: Use MixAll.isPropertyValid() in Validators.checkBrokerConfig() URL: https://github.com/apache/rocketmq/issues/6550 -- 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

Re: [I] mqbroker: 48: [[: not found [rocketmq]

2024-04-26 Thread via GitHub
github-actions[bot] closed issue #6006: mqbroker: 48: [[: not found URL: https://github.com/apache/rocketmq/issues/6006 -- 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

Re: [I] mqbroker: 48: [[: not found [rocketmq]

2024-04-26 Thread via GitHub
github-actions[bot] commented on issue #6006: URL: https://github.com/apache/rocketmq/issues/6006#issuecomment-2080250986 This issue was closed because it has been inactive for 3 days since being marked as stale. -- This is an automated message from the Apache Git Service. To respond to

Re: [PR] Use MixAll.isPropertyValid() in Validators.checkBrokerConfig() [rocketmq]

2024-04-26 Thread via GitHub
github-actions[bot] commented on PR #6551: URL: https://github.com/apache/rocketmq/pull/6551#issuecomment-2080250957 This PR was closed because it has been inactive for 3 days since being marked as stale. -- This is an automated message from the Apache Git Service. To respond to the

Re: [I] Broker dynamically perceives the expansion and contraction of nameserver [rocketmq]

2024-04-26 Thread via GitHub
github-actions[bot] commented on issue #6599: URL: https://github.com/apache/rocketmq/issues/6599#issuecomment-2080250902 This issue is stale because it has been open for 365 days with no activity. It will be closed in 3 days if no further activity occurs. -- This is an automated message

Re: [I] Pop consume cause out of memory when not writeable. [rocketmq]

2024-04-26 Thread via GitHub
github-actions[bot] closed issue #6598: Pop consume cause out of memory when not writeable. URL: https://github.com/apache/rocketmq/issues/6598 -- 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

Re: [I] Pop consume cause out of memory when not writeable. [rocketmq]

2024-04-26 Thread via GitHub
github-actions[bot] commented on issue #6598: URL: https://github.com/apache/rocketmq/issues/6598#issuecomment-2080250928 This issue was closed because it has been inactive for 3 days since being marked as stale. -- This is an automated message from the Apache Git Service. To respond to

Re: [PR] Use MixAll.isPropertyValid() in Validators.checkBrokerConfig() [rocketmq]

2024-04-26 Thread via GitHub
github-actions[bot] closed pull request #6551: Use MixAll.isPropertyValid() in Validators.checkBrokerConfig() URL: https://github.com/apache/rocketmq/pull/6551 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL

Re: [I] Use MixAll.isPropertyValid() in Validators.checkBrokerConfig() [rocketmq]

2024-04-26 Thread via GitHub
github-actions[bot] commented on issue #6550: URL: https://github.com/apache/rocketmq/issues/6550#issuecomment-2080250973 This issue was closed because it has been inactive for 3 days since being marked as stale. -- This is an automated message from the Apache Git Service. To respond to