[GitHub] [rocketmq] drpmma added a comment to the discussion: Windows环境运行SDK收发示例失败
GitHub user drpmma added a comment to the discussion: Windows环境运行SDK收发示例失败 详见路径 ~/logs/rocketmqlogs/ 看看有没有相关信息，没有信息也很难帮助你 GitHub link: https://github.com/apache/rocketmq/discussions/6305#discussioncomment-5265351 This is an automatically sent email for dev@rocketmq.apache.org. To unsubscribe, please send an email to: dev-unsubscr...@rocketmq.apache.org
[GitHub] [rocketmq] socutes added a comment to the discussion: Is rocketmq considering supporting HTTP Restful protocols?
GitHub user socutes added a comment to the discussion: Is rocketmq considering supporting HTTP Restful protocols? Yes. kafka includes http restful support as a feature of a commercial release.The primary purpose of this requirement is to support more forms of access. So two questions to discuss: 1. Whether there is a need for support 2. Where to support GitHub link: https://github.com/apache/rocketmq/discussions/6304#discussioncomment-5263667 This is an automatically sent email for dev@rocketmq.apache.org. To unsubscribe, please send an email to: dev-unsubscr...@rocketmq.apache.org
[GitHub] [rocketmq] socutes added a comment to the discussion: Question about "Initial consumer offset"
GitHub user socutes added a comment to the discussion: Question about "Initial consumer offset" I think the earliest and the latest have their own disadvantages。 minimum offset: There will be lots of reconsumption. maximum offset：There will be old data that will not be consumed By default, neither is better than the other. GitHub link: https://github.com/apache/rocketmq/discussions/6309#discussioncomment-5263612 This is an automatically sent email for dev@rocketmq.apache.org. To unsubscribe, please send an email to: dev-unsubscr...@rocketmq.apache.org
[GitHub] [rocketmq] yuluo-yx edited a comment on the discussion: Windows环境运行SDK收发示例失败
GitHub user yuluo-yx edited a comment on the discussion: Windows环境运行SDK收发示例失败 > 可以查看下客户端日志，看是否有更多信息 并没有任何提示，idea控制台也没有任何信息 GitHub link: https://github.com/apache/rocketmq/discussions/6305#discussioncomment-5262985 This is an automatically sent email for dev@rocketmq.apache.org. To unsubscribe, please send an email to: dev-unsubscr...@rocketmq.apache.org
[GitHub] [rocketmq] yuluo-yx added a comment to the discussion: Windows环境运行SDK收发示例失败
GitHub user yuluo-yx added a comment to the discussion: Windows环境运行SDK收发示例失败 > 可以查看下客户端日志，看是否有更多信息 并没有任何提示 GitHub link: https://github.com/apache/rocketmq/discussions/6305#discussioncomment-5262985 This is an automatically sent email for dev@rocketmq.apache.org. To unsubscribe, please send an email to: dev-unsubscr...@rocketmq.apache.org
[GitHub] [rocketmq] RongtongJin edited a comment on the discussion: 关于过期文件删除问题
GitHub user RongtongJin edited a comment on the discussion: 关于过期文件删除问题 @echooymxq 设计的时候是考虑过类似解法的，但考虑系统自动清空commitlog和consumeQueue是高危操作，如果用户不想删除，但上线后MQ自动清空数据结果会很严重，所以最后决定这种场景就是需要人工介入的。 GitHub link: https://github.com/apache/rocketmq/discussions/6265#discussioncomment-5238800 This is an automatically sent email for dev@rocketmq.apache.org. To unsubscribe, please send an email to: dev-unsubscr...@rocketmq.apache.org
[GitHub] [rocketmq] drpmma added a comment to the discussion: Inquiry about enriching 5.0 Proxy features
GitHub user drpmma added a comment to the discussion: Inquiry about enriching 5.0 Proxy features The act of creating a topic is considered an internal cluster operation and can be fulfilled by the mqadmin tool. And the role of the proxy is more focused on exposing services And getting the client connection is indeed necessary for the proxy because the connection info is stored in the proxy. GitHub link: https://github.com/apache/rocketmq/discussions/6210#discussioncomment-5262343 This is an automatically sent email for dev@rocketmq.apache.org. To unsubscribe, please send an email to: dev-unsubscr...@rocketmq.apache.org
[GitHub] [rocketmq] drpmma added a comment to the discussion: Windows环境运行SDK收发示例失败
GitHub user drpmma added a comment to the discussion: Windows环境运行SDK收发示例失败 可以查看下客户端日志，看是否有更多信息 GitHub link: https://github.com/apache/rocketmq/discussions/6305#discussioncomment-5262265 This is an automatically sent email for dev@rocketmq.apache.org. To unsubscribe, please send an email to: dev-unsubscr...@rocketmq.apache.org
[GitHub] [rocketmq] aaron-ai added a comment to the discussion: Is rocketmq considering supporting HTTP Restful protocols?
GitHub user aaron-ai added a comment to the discussion: Is rocketmq considering supporting HTTP Restful protocols? AFAIK, Pulsar provides [WebSocket API](https://pulsar.apache.org/docs/2.10.x/client-libraries-websocket/) to access, and Kafka provides [kafka-rest](https://github.com/confluentinc/kafka-rest) to make it possible to access by RESTful API, but this project is not belong to ASF. Both of Pulsar and Kafka doesn't provide the official client, Maybe because of the RESTful API is out-of-box enough? So I think it is a nice proposal to provide various way to access RocketMQ service, but we should discuss the specified protocol we choose and what organization should the related project belongs to. GitHub link: https://github.com/apache/rocketmq/discussions/6304#discussioncomment-5261982 This is an automatically sent email for dev@rocketmq.apache.org. To unsubscribe, please send an email to: dev-unsubscr...@rocketmq.apache.org
[GitHub] [rocketmq] echooymxq edited a comment on the discussion: Is rocketmq considering supporting HTTP Restful protocols?
GitHub user echooymxq edited a comment on the discussion: Is rocketmq considering supporting HTTP Restful protocols? > Yes, It is not difficult to integrate POP consumption with HTTP protocol in > Proxy. But I want to know what are the use cases for using HTTP? If we only > consider the ease of use of the SDK, the gRPC client in version 5.0 seems to > be simpler. Here is a [RIP-17](https://github.com/apache/rocketmq/wiki/RIP-17-RocketMQ-HTTP-Proxy-Support). As far as I know, the community's demand for HTTP protocol is not high. GitHub link: https://github.com/apache/rocketmq/discussions/6304#discussioncomment-5261880 This is an automatically sent email for dev@rocketmq.apache.org. To unsubscribe, please send an email to: dev-unsubscr...@rocketmq.apache.org
[GitHub] [rocketmq] echooymxq added a comment to the discussion: Is rocketmq considering supporting HTTP Restful protocols?
GitHub user echooymxq added a comment to the discussion: Is rocketmq considering supporting HTTP Restful protocols? > Yes, It is not difficult to integrate POP consumption with HTTP protocol in > Proxy. But I want to know what are the use cases for using HTTP? If we only > consider the ease of use of the SDK, the gRPC client in version 5.0 seems to > be simpler. Here is a RIP-17. As far as I know, the community's demand for HTTP protocol is not high. GitHub link: https://github.com/apache/rocketmq/discussions/6304#discussioncomment-5261880 This is an automatically sent email for dev@rocketmq.apache.org. To unsubscribe, please send an email to: dev-unsubscr...@rocketmq.apache.org
[GitHub] [rocketmq] echooymxq added a comment to the discussion: Is rocketmq considering supporting HTTP Restful protocols?
GitHub user echooymxq added a comment to the discussion: Is rocketmq considering supporting HTTP Restful protocols? Yes, It is not difficult to integrate POP consumption with HTTP protocol in Proxy. But I want to know what are the use cases for using HTTP? If we only consider the ease of use of the SDK, the gRPC client in version 5.0 seems to be simpler. GitHub link: https://github.com/apache/rocketmq/discussions/6304#discussioncomment-5261851 This is an automatically sent email for dev@rocketmq.apache.org. To unsubscribe, please send an email to: dev-unsubscr...@rocketmq.apache.org
[GitHub] [rocketmq] yuluo-yx added a comment to the discussion: Windows环境运行SDK收发示例失败
GitHub user yuluo-yx added a comment to the discussion: Windows环境运行SDK收发示例失败 代码来自官网文档，复制粘贴：https://rocketmq.apache.org/zh/docs/quickStart/01quickstart GitHub link: https://github.com/apache/rocketmq/discussions/6305#discussioncomment-5261756 This is an automatically sent email for dev@rocketmq.apache.org. To unsubscribe, please send an email to: dev-unsubscr...@rocketmq.apache.org
[GitHub] [rocketmq] socutes added a comment to the discussion: Inquiry about enriching 5.0 Proxy features
GitHub user socutes added a comment to the discussion: Inquiry about enriching 5.0 Proxy features It seems very necessary. Is it already being done? GitHub link: https://github.com/apache/rocketmq/discussions/6210#discussioncomment-5261755 This is an automatically sent email for dev@rocketmq.apache.org. To unsubscribe, please send an email to: dev-unsubscr...@rocketmq.apache.org
[GitHub] [rocketmq] socutes edited a discussion: Is rocketmq considering supporting HTTP Restful protocols?
GitHub user socutes edited a discussion: Is rocketmq considering supporting HTTP Restful protocols? Rocketmq 5.0 has an independent proxy module and supports both grpc and pop protocols. Both kafka and pulsar support http restful production and consumption. Supporting http restful in Proxy seems feasible.Whether the community has this plan and whether it needs to be discussed. In my opinion, it is necessary in terms of ease of use and cost of development of the SDK. I'd like to hear from the experts. GitHub link: https://github.com/apache/rocketmq/discussions/6304 This is an automatically sent email for dev@rocketmq.apache.org. To unsubscribe, please send an email to: dev-unsubscr...@rocketmq.apache.org
[GitHub] [rocketmq] socutes added a comment to the discussion: Whether the ForwardRequestProcessors are being used？
GitHub user socutes added a comment to the discussion: Whether the ForwardRequestProcessors are being used？ ok GitHub link: https://github.com/apache/rocketmq/discussions/6274#discussioncomment-5241433 This is an automatically sent email for dev@rocketmq.apache.org. To unsubscribe, please send an email to: dev-unsubscr...@rocketmq.apache.org
[GitHub] [rocketmq] RongtongJin added a comment to the discussion: Whether the ForwardRequestProcessors are being used？
GitHub user RongtongJin added a comment to the discussion: Whether the ForwardRequestProcessors are being used？ Hi @socutes , I think this class is useless, you can subbmit a pull request to delete the class. GitHub link: https://github.com/apache/rocketmq/discussions/6274#discussioncomment-5238819 This is an automatically sent email for dev@rocketmq.apache.org. To unsubscribe, please send an email to: dev-unsubscr...@rocketmq.apache.org
[GitHub] [rocketmq] RongtongJin edited a comment on the discussion: 关于过期文件删除问题
GitHub user RongtongJin edited a comment on the discussion: 关于过期文件删除问题 > 对于长时间下线然后重新上线的Broker，因为CommitLog过期删除策略，始终会保存最后一个文件，如果当前Broker的phyOffset小于主节点的minOffset，这个时候会始终无法进行同步。通常解决办法是人工手动清理掉store文件再重启，我的疑问是能不能在Broker启动load的时候，先手动的检查一下CommitLog的最后一个文件，如果已经过期，那么就主动清空commitlog和consumeQueue。或者说是在主从同步时，发现主传过来的offset比从Broker当前的phyOffset要大，则主动设置同步位点为0(高危操作)。 @echooymxq 设计的时候是考虑过类似解法的，但考虑系统自动清空commitlog和consumeQueue是高危操作，如果用户不想删除，但上线后MQ自动清空数据结果会很严重，所以最后决定这种场景就是需要人工介入的。 GitHub link: https://github.com/apache/rocketmq/discussions/6265#discussioncomment-5238800 This is an automatically sent email for dev@rocketmq.apache.org. To unsubscribe, please send an email to: dev-unsubscr...@rocketmq.apache.org
[GitHub] [rocketmq] RongtongJin added a comment to the discussion: 关于过期文件删除问题
GitHub user RongtongJin added a comment to the discussion: 关于过期文件删除问题 > 对于长时间下线然后重新上线的Broker，因为CommitLog过期删除策略，始终会保存最后一个文件，如果当前Broker的phyOffset小于主节点的minOffset，这个时候会始终无法进行同步。通常解决办法是人工手动清理掉store文件再重启，我的疑问是能不能在Broker启动load的时候，先手动的检查一下CommitLog的最后一个文件，如果已经过期，那么就主动清空commitlog和consumeQueue。或者说是在主从同步时，发现主传过来的offset比从Broker当前的phyOffset要大，则主动设置同步位点为0(高危操作)。 @echooymxq 设计的时候是考虑过类似解法的，但考虑系统自动清空commitlog和consumeQueue是高危操作，如果用户不想删除，但上线后MQ自动清空数据结果会很严重，所以最后判断这种情况就是需要人工介入的。 GitHub link: https://github.com/apache/rocketmq/discussions/6265#discussioncomment-5238800 This is an automatically sent email for dev@rocketmq.apache.org. To unsubscribe, please send an email to: dev-unsubscr...@rocketmq.apache.org
[GitHub] [rocketmq] drpmma edited a comment on the discussion: Whether any time delay of 5.0.0 can be merged into the 4.9.x branch？
GitHub user drpmma edited a comment on the discussion: Whether any time delay of 5.0.0 can be merged into the 4.9.x branch？ Most of the new features added in RocketMQ 5.0 are implemented through new modules, such as proxy and ha, without affecting the existing functions. Additionally, RocketMQ 5.0 includes many optimizations and bug fixes. Even if the new functions such as proxy or ha are not needed, it is still possible to continue using RocketMQ 5.0 in the same way as RocketMQ 4.9 without any functional dependencies. GitHub link: https://github.com/apache/rocketmq/discussions/6277#discussioncomment-5238305 This is an automatically sent email for dev@rocketmq.apache.org. To unsubscribe, please send an email to: dev-unsubscr...@rocketmq.apache.org
[GitHub] [rocketmq] drpmma edited a comment on the discussion: Whether any time delay of 5.0.0 can be merged into the 4.9.x branch？
GitHub user drpmma edited a comment on the discussion: Whether any time delay of 5.0.0 can be merged into the 4.9.x branch？ Most of the new features added in RocketMQ 5.0 are implemented through new modules, such as proxy and ha, without affecting the existing functions. Additionally, RocketMQ 5.0 includes many optimizations, and bug fixes. Even if the new functions such as proxy or ha are not needed, it is still possible to continue using RocketMQ 5.0 in the same way as RocketMQ 4.9 without any functional dependencies. GitHub link: https://github.com/apache/rocketmq/discussions/6277#discussioncomment-5238305 This is an automatically sent email for dev@rocketmq.apache.org. To unsubscribe, please send an email to: dev-unsubscr...@rocketmq.apache.org
[GitHub] [rocketmq] drpmma added a comment to the discussion: Whether any time delay of 5.0.0 can be merged into the 4.9.x branch？
GitHub user drpmma added a comment to the discussion: Whether any time delay of 5.0.0 can be merged into the 4.9.x branch？ Most of the new features added in RocketMQ 5.0 are implemented through new modules, such as proxy and ha, without affecting the existing functions. Additionally, RocketMQ 5.0 includes many new features, optimizations, and bug fixes. Even if the new functions such as proxy or ha are not needed, it is still possible to continue using RocketMQ 5.0 in the same way as RocketMQ 4.9 without any functional dependencies. GitHub link: https://github.com/apache/rocketmq/discussions/6277#discussioncomment-5238305 This is an automatically sent email for dev@rocketmq.apache.org. To unsubscribe, please send an email to: dev-unsubscr...@rocketmq.apache.org
[GitHub] [rocketmq] drpmma added a comment to the discussion: Whether any time delay of 5.0.0 can be merged into the 4.9.x branch？
GitHub user drpmma added a comment to the discussion: Whether any time delay of 5.0.0 can be merged into the 4.9.x branch？ There is no timeline for now. GitHub link: https://github.com/apache/rocketmq/discussions/6277#discussioncomment-5238052 This is an automatically sent email for dev@rocketmq.apache.org. To unsubscribe, please send an email to: dev-unsubscr...@rocketmq.apache.org
[GitHub] [rocketmq] mz0113 added a comment to the discussion: v5.0.0 Pop消费模式下,很多消息显示重试次数达上千次
GitHub user mz0113 added a comment to the discussion: v5.0.0 Pop消费模式下,很多消息显示重试次数达上千次 已解决，消费能力tps较低；pop大量消息超时了 GitHub link: https://github.com/apache/rocketmq/discussions/6261#discussioncomment-5236868 This is an automatically sent email for dev@rocketmq.apache.org. To unsubscribe, please send an email to: dev-unsubscr...@rocketmq.apache.org
[GitHub] [rocketmq] wps12345 edited a comment on the discussion: Whether any time delay of 5.0.0 can be merged into the 4.9.x branch？
GitHub user wps12345 edited a comment on the discussion: Whether any time delay of 5.0.0 can be merged into the 4.9.x branch？ 因为我们一直使用的是4.9.x版本，考虑升级会带来一些风险，并且5.0.0刚迭代了两个版本，如果使用5.0.版本可能后期还需要更新小版本。目前我们只需要支持任意时长延迟，打算5.0再迭代几个小版本后再升上去 GitHub link: https://github.com/apache/rocketmq/discussions/6277#discussioncomment-5236073 This is an automatically sent email for dev@rocketmq.apache.org. To unsubscribe, please send an email to: dev-unsubscr...@rocketmq.apache.org
[GitHub] [rocketmq] wps12345 added a comment to the discussion: Whether any time delay of 5.0.0 can be merged into the 4.9.x branch？
GitHub user wps12345 added a comment to the discussion: Whether any time delay of 5.0.0 can be merged into the 4.9.x branch？ 因为我们一直使用的是4.9.x版本，考虑升级会带来一些风险，并且5.0.0刚迭代了两个版本，如果使用5.0.以上版本可能后期还需要更新小版本，目前我们需要支持任意时长延迟，打算5.0再迭代几个小版本后再生上去 GitHub link: https://github.com/apache/rocketmq/discussions/6277#discussioncomment-5236073 This is an automatically sent email for dev@rocketmq.apache.org. To unsubscribe, please send an email to: dev-unsubscr...@rocketmq.apache.org
[GitHub] [rocketmq] echooymxq added a comment to the discussion: Whether any time delay of 5.0.0 can be merged into the 4.9.x branch？
GitHub user echooymxq added a comment to the discussion: Whether any time delay of 5.0.0 can be merged into the 4.9.x branch？ 为什么不考虑直接升级到5.0呢？ GitHub link: https://github.com/apache/rocketmq/discussions/6277#discussioncomment-5236037 This is an automatically sent email for dev@rocketmq.apache.org. To unsubscribe, please send an email to: dev-unsubscr...@rocketmq.apache.org
[GitHub] [rocketmq] wps12345 added a comment to the discussion: Whether any time delay of 5.0.0 can be merged into the 4.9.x branch？
GitHub user wps12345 added a comment to the discussion: Whether any time delay of 5.0.0 can be merged into the 4.9.x branch？ 还有一个问题，如果代码合入了4.9.x版本，spring boot框架在发送消息时，是不是可以使用rocketmq-spring-boot-starter最新版本：2.2.3 GitHub link: https://github.com/apache/rocketmq/discussions/6277#discussioncomment-5235914 This is an automatically sent email for dev@rocketmq.apache.org. To unsubscribe, please send an email to: dev-unsubscr...@rocketmq.apache.org
[GitHub] [rocketmq] echooymxq added a comment to the discussion: 关于过期文件删除问题
GitHub user echooymxq added a comment to the discussion: 关于过期文件删除问题 > 部署哪个HA模式的版本 Controller模式的 GitHub link: https://github.com/apache/rocketmq/discussions/6265#discussioncomment-5230339 This is an automatically sent email for dev@rocketmq.apache.org. To unsubscribe, please send an email to: dev-unsubscr...@rocketmq.apache.org
[GitHub] [rocketmq] fuyou001 added a comment to the discussion: 关于过期文件删除问题
GitHub user fuyou001 added a comment to the discussion: 关于过期文件删除问题 部署哪个HA模式的版本 GitHub link: https://github.com/apache/rocketmq/discussions/6265#discussioncomment-5229943 This is an automatically sent email for dev@rocketmq.apache.org. To unsubscribe, please send an email to: dev-unsubscr...@rocketmq.apache.org
[GitHub] [rocketmq] mz0113 edited a discussion: v5.0.0 Pop消费模式下,很多消息显示重试次数达上千次
GitHub user mz0113 edited a discussion: v5.0.0 Pop消费模式下,很多消息显示重试次数达上千次 现象: consumer.getReconsumeTimes() 返回值几百到几千之间 , 如图 . 正常应该是默认的16次, 但是这个Topic就很奇怪 消费模式为并发消费,POP模式 。schedule queue-0队列因此堆积了几千万消息。revive队列也很大，但是实际上我消息量很小，tps也就几  GitHub link: https://github.com/apache/rocketmq/discussions/6261 This is an automatically sent email for dev@rocketmq.apache.org. To unsubscribe, please send an email to: dev-unsubscr...@rocketmq.apache.org
[GitHub] [rocketmq] mz0113 edited a discussion: v5.0.0 Pop消费模式下,很多消息显示重试次数达上千次
GitHub user mz0113 edited a discussion: v5.0.0 Pop消费模式下,很多消息显示重试次数达上千次 现象: consumer.getReconsumeTimes() 返回值几百到几千之间 , 如图 . 正常应该是默认的16次, 但是这个Topic就很奇怪 消费模式为并发消费,POP模式 。  GitHub link: https://github.com/apache/rocketmq/discussions/6261 This is an automatically sent email for dev@rocketmq.apache.org. To unsubscribe, please send an email to: dev-unsubscr...@rocketmq.apache.org
[GitHub] [rocketmq] RongtongJin added a comment to the discussion: [5.1.0]关于Dledger和controller疑问
GitHub user RongtongJin added a comment to the discussion: [5.1.0]关于Dledger和controller疑问 > let me try，thx。 **问题描述** 另外，可能我没有表述清楚，我其实想问的是DLedger+ controller主备切换 模式的部署文档。 > 因为我本地部署DLedger是能够成功了，但是DLedger升级到controller主备切换总是失败，所以想问问能不能直接基于DLedger部署controller主备切换。 > **部署步骤** > `参考官方文档，在Controller模式下，Broker配置必须设置enableControllerMode=true，并填写controllerAddr。` > 我在原有（3个节点的）DLedger集群基础上增加了enableControllerMode、controllerAddr两项配置，希望 > **实现3个nameserver（内嵌controller）+3个DLedger**。 > 但是通过getSyncStateSet命令只能看到1个member，导致kill master后切主失败。 > > **排查思路** 当然我也在排查是否是我部署的姿势不对，检查过配置目前没有看到问题。如果有相关讨论社区希望可以交流一下。 Thx。 是的。原本的dledger模式和controller是无法混用的。两者是互斥的 GitHub link: https://github.com/apache/rocketmq/discussions/6172#discussioncomment-5199178 This is an automatically sent email for dev@rocketmq.apache.org. To unsubscribe, please send an email to: dev-unsubscr...@rocketmq.apache.org
[GitHub] [rocketmq] 1270045840 added a comment to the discussion: 启动报错Expected the service PushConsumerImpl-0 [FAILED] to be RUNNING, but the service has FAILED
GitHub user 1270045840 added a comment to the discussion: 启动报错Expected the
service PushConsumerImpl-0 [FAILED] to be RUNNING, but the service has FAILED
public class PushConsumerExample {
private static final Logger logger =
LoggerFactory.getLogger(PushConsumerExample.class);
private PushConsumerExample() {
}
public static void main(String[] args) throws ClientException, IOException,
InterruptedException {
final ClientServiceProvider provider =
ClientServiceProvider.loadService();
// 接入点地址，需要设置成Proxy的地址和端口列表，一般是xxx:8081;xxx:8081。
String endpoints = "127.0.0.1:8081";
ClientConfiguration clientConfiguration =
ClientConfiguration.newBuilder()
.setEndpoints(endpoints)
.build();
// 订阅消息的过滤规则，表示订阅所有Tag的消息。
String tag = "*";
FilterExpression filterExpression = new FilterExpression(tag,
FilterExpressionType.TAG);
// 为消费者指定所属的消费者分组，Group需要提前创建。
String consumerGroup = "userLog";
// 指定需要订阅哪个目标Topic，Topic需要提前创建。
String topic = "userLog";
// 初始化PushConsumer，需要绑定消费者分组ConsumerGroup、通信参数以及订阅关系。
PushConsumer pushConsumer = provider.newPushConsumerBuilder()
.setClientConfiguration(clientConfiguration)
// 设置消费者分组。
.setConsumerGroup(consumerGroup)
// 设置预绑定的订阅关系。
.setSubscriptionExpressions(Collections.singletonMap(topic,
filterExpression))
// 设置消费监听器。
.setMessageListener(messageView -> {
// 处理消息并返回消费结果。
logger.info("Consume message successfully, messageId={}",
messageView.getMessageId());
return ConsumeResult.SUCCESS;
})
.build();
//Thread.sleep(Long.MAX_VALUE);
// 如果不需要再使用 PushConsumer，可关闭该实例。
// pushConsumer.close();
}
}
您好，我切换为8081之后，还是一样的错误
GitHub link:
https://github.com/apache/rocketmq/discussions/6238#discussioncomment-5189544
This is an automatically sent email for dev@rocketmq.apache.org.
To unsubscribe, please send an email to: dev-unsubscr...@rocketmq.apache.org
[GitHub] [rocketmq] zhouxinyu added a comment to the discussion: 启动报错Expected the service PushConsumerImpl-0 [FAILED] to be RUNNING, but the service has FAILED
GitHub user zhouxinyu added a comment to the discussion: 启动报错Expected the service PushConsumerImpl-0 [FAILED] to be RUNNING, but the service has FAILED The root cause is `Connection refused: /127.0.0.1:9876`. If the cluster is in proxy mode, try connecting to the 8081 port which is the default port of the proxy server. GitHub link: https://github.com/apache/rocketmq/discussions/6238#discussioncomment-5189381 This is an automatically sent email for dev@rocketmq.apache.org. To unsubscribe, please send an email to: dev-unsubscr...@rocketmq.apache.org
[GitHub] [rocketmq] weihubeats deleted a comment on the discussion: rocketmq grpc sdk
GitHub user weihubeats deleted a comment on the discussion: rocketmq grpc sdk I mean if I need to use grpc I need to introduce more dependencies manually, is there a sealed sdk that I can use to introduce only one dependency? GitHub link: https://github.com/apache/rocketmq/discussions/6225#discussioncomment-5175475 This is an automatically sent email for dev@rocketmq.apache.org. To unsubscribe, please send an email to: dev-unsubscr...@rocketmq.apache.org
[GitHub] [rocketmq] RongtongJin added a comment to the discussion: 从节点不工作，监控面板上没有消费消息
GitHub user RongtongJin added a comment to the discussion: 从节点不工作，监控面板上没有消费消息 @xcfuu 看日志master-slave并不是完全没有同步，但存在频繁断链的情况。如果主备间网络没有问题的话，我看你的版本4.2.0-incubating，在这之后还是修过不少bug的，建议进行升级。 GitHub link: https://github.com/apache/rocketmq/discussions/6218#discussioncomment-5178289 This is an automatically sent email for dev@rocketmq.apache.org. To unsubscribe, please send an email to: dev-unsubscr...@rocketmq.apache.org
[GitHub] [rocketmq] weihubeats added a comment to the discussion: rocketmq grpc sdk
GitHub user weihubeats added a comment to the discussion: rocketmq grpc sdk I mean if I need to use grpc I need to introduce more dependencies manually, is there a sealed sdk that I can use to introduce only one dependency? GitHub link: https://github.com/apache/rocketmq/discussions/6225#discussioncomment-5175475 This is an automatically sent email for dev@rocketmq.apache.org. To unsubscribe, please send an email to: dev-unsubscr...@rocketmq.apache.org
[GitHub] [rocketmq] ShadowySpirits added a comment to the discussion: rocketmq grpc sdk
GitHub user ShadowySpirits added a comment to the discussion: rocketmq grpc sdk I don't understand what you mean. If you want to have the benefit of grpc protocol, you need to set up a proxy node and introduce one of [rocketmq-clients](https://github.com/apache/rocketmq-clients) in your app, see [java examples](https://github.com/apache/rocketmq-clients/tree/master/java/client/src/main/java/org/apache/rocketmq/client/java/example) for more details. GitHub link: https://github.com/apache/rocketmq/discussions/6225#discussioncomment-5175231 This is an automatically sent email for dev@rocketmq.apache.org. To unsubscribe, please send an email to: dev-unsubscr...@rocketmq.apache.org
[GitHub] [rocketmq] mxsm added a comment to the discussion: 从节点不工作，监控面板上没有消费消息
GitHub user mxsm added a comment to the discussion: 从节点不工作，监控面板上没有消费消息
> @xcfuu 分别进入主、备节点，执行如下命令，对比下结果 `sh bin/mqadmin brokerstatus -b {your broker
> address} | grep msgGet`
他这用命令和界面应该是一样的
GitHub link:
https://github.com/apache/rocketmq/discussions/6218#discussioncomment-5174391
This is an automatically sent email for dev@rocketmq.apache.org.
To unsubscribe, please send an email to: dev-unsubscr...@rocketmq.apache.org
[GitHub] [rocketmq] xcfuu added a comment to the discussion: 从节点不工作，监控面板上没有消费消息
GitHub user xcfuu added a comment to the discussion: 从节点不工作，监控面板上没有消费消息 主 msgGetTotalTodayMorning : 19764858 msgGetTotalTodayNow : 19828834 msgGetTotalYesterdayMorning : 19621677 从 msgGetTotalTodayMorning : 0 msgGetTotalTodayNow : 0 msgGetTotalYesterdayMorning : 0 GitHub link: https://github.com/apache/rocketmq/discussions/6218#discussioncomment-5174331 This is an automatically sent email for dev@rocketmq.apache.org. To unsubscribe, please send an email to: dev-unsubscr...@rocketmq.apache.org
[GitHub] [rocketmq] xcfuu edited a comment on the discussion: 从节点不工作，监控面板上没有消费消息
GitHub user xcfuu edited a comment on the discussion: 从节点不工作，监控面板上没有消费消息  master日志 GitHub link: https://github.com/apache/rocketmq/discussions/6218#discussioncomment-5173990 This is an automatically sent email for dev@rocketmq.apache.org. To unsubscribe, please send an email to: dev-unsubscr...@rocketmq.apache.org
[GitHub] [rocketmq] xcfuu added a comment to the discussion: 从节点不工作，监控面板上没有消费消息
GitHub user xcfuu added a comment to the discussion: 从节点不工作，监控面板上没有消费消息  GitHub link: https://github.com/apache/rocketmq/discussions/6218#discussioncomment-5173990 This is an automatically sent email for dev@rocketmq.apache.org. To unsubscribe, please send an email to: dev-unsubscr...@rocketmq.apache.org
[GitHub] [rocketmq] RongtongJin added a comment to the discussion: 从节点不工作，监控面板上没有消费消息
GitHub user RongtongJin added a comment to the discussion: 从节点不工作，监控面板上没有消费消息 >  > 没啥报错日志 WARN的就是报错，看这个由于某些原因，Slave和Matser频繁断连。。看看Master的store日志吧 GitHub link: https://github.com/apache/rocketmq/discussions/6218#discussioncomment-5173845 This is an automatically sent email for dev@rocketmq.apache.org. To unsubscribe, please send an email to: dev-unsubscr...@rocketmq.apache.org
[GitHub] [rocketmq] caigy added a comment to the discussion: 从节点不工作，监控面板上没有消费消息
GitHub user caigy added a comment to the discussion: 从节点不工作，监控面板上没有消费消息
@xcfuu 分别进入主、备节点，执行如下命令，对比下结果
`sh bin/mqadmin brokerstatus -b {your broker address} | grep msgGet`
GitHub link:
https://github.com/apache/rocketmq/discussions/6218#discussioncomment-5173155
This is an automatically sent email for dev@rocketmq.apache.org.
To unsubscribe, please send an email to: dev-unsubscr...@rocketmq.apache.org
[GitHub] [rocketmq] xcfuu edited a discussion: 从节点不工作，监控面板上没有消费消息
GitHub user xcfuu edited a discussion: 从节点不工作，监控面板上没有消费消息   版本 rocketmq-broker-4.2.0-incubating-SNAPSHOT.jar 请问这种情况应该从什么方向去查问题？ GitHub link: https://github.com/apache/rocketmq/discussions/6218 This is an automatically sent email for dev@rocketmq.apache.org. To unsubscribe, please send an email to: dev-unsubscr...@rocketmq.apache.org
[GitHub] [rocketmq] xcfuu added a comment to the discussion: 从节点不工作，监控面板上没有消费消息
GitHub user xcfuu added a comment to the discussion: 从节点不工作，监控面板上没有消费消息 看着进度是一致的 GitHub link: https://github.com/apache/rocketmq/discussions/6218#discussioncomment-5173042 This is an automatically sent email for dev@rocketmq.apache.org. To unsubscribe, please send an email to: dev-unsubscr...@rocketmq.apache.org
[GitHub] [rocketmq] xcfuu added a comment to the discussion: 从节点不工作，监控面板上没有消费消息
GitHub user xcfuu added a comment to the discussion: 从节点不工作，监控面板上没有消费消息 主节点  从节点  GitHub link: https://github.com/apache/rocketmq/discussions/6218#discussioncomment-5173028 This is an automatically sent email for dev@rocketmq.apache.org. To unsubscribe, please send an email to: dev-unsubscr...@rocketmq.apache.org
[GitHub] [rocketmq] xcfuu added a comment to the discussion: 从节点不工作，监控面板上没有消费消息
GitHub user xcfuu added a comment to the discussion: 从节点不工作，监控面板上没有消费消息  没啥报错日志 GitHub link: https://github.com/apache/rocketmq/discussions/6218#discussioncomment-5172957 This is an automatically sent email for dev@rocketmq.apache.org. To unsubscribe, please send an email to: dev-unsubscr...@rocketmq.apache.org
[GitHub] [rocketmq] xcfuu added a comment to the discussion: 从节点不工作，监控面板上没有消费消息
GitHub user xcfuu added a comment to the discussion: 从节点不工作，监控面板上没有消费消息  基本都是这些日志 GitHub link: https://github.com/apache/rocketmq/discussions/6218#discussioncomment-5172940 This is an automatically sent email for dev@rocketmq.apache.org. To unsubscribe, please send an email to: dev-unsubscr...@rocketmq.apache.org
[GitHub] [rocketmq] mxsm added a comment to the discussion: 从节点不工作，监控面板上没有消费消息
GitHub user mxsm added a comment to the discussion: 从节点不工作，监控面板上没有消费消息 @xcfuu 你看一下Slave下面消费进度的json文件，是否和Master的一样。 GitHub link: https://github.com/apache/rocketmq/discussions/6218#discussioncomment-5172919 This is an automatically sent email for dev@rocketmq.apache.org. To unsubscribe, please send an email to: dev-unsubscr...@rocketmq.apache.org
[GitHub] [rocketmq] RongtongJin added a comment to the discussion: 从节点不工作，监控面板上没有消费消息
GitHub user RongtongJin added a comment to the discussion: 从节点不工作，监控面板上没有消费消息 @xcfuu HA相关日志在~/logs/rocketmqlogs/store.log，可以看下 GitHub link: https://github.com/apache/rocketmq/discussions/6218#discussioncomment-5172321 This is an automatically sent email for dev@rocketmq.apache.org. To unsubscribe, please send an email to: dev-unsubscr...@rocketmq.apache.org
[GitHub] [rocketmq] xcfuu edited a discussion: 从节点不工作，监控面板上没有消费消息
GitHub user xcfuu edited a discussion: 从节点不工作，监控面板上没有消费消息   请问这种情况应该从什么方向去查问题？ GitHub link: https://github.com/apache/rocketmq/discussions/6218 This is an automatically sent email for dev@rocketmq.apache.org. To unsubscribe, please send an email to: dev-unsubscr...@rocketmq.apache.org
[GitHub] [rocketmq] xcfuu edited a discussion: 从节点不工作，监控面板上没有消费消息
GitHub user xcfuu edited a discussion: 从节点不工作，监控面板上没有消费消息   No error found in the log GitHub link: https://github.com/apache/rocketmq/discussions/6218 This is an automatically sent email for dev@rocketmq.apache.org. To unsubscribe, please send an email to: dev-unsubscr...@rocketmq.apache.org
[GitHub] [rocketmq] ShadowySpirits added a comment to the discussion: Inquiry about enriching 5.0 Proxy features
GitHub user ShadowySpirits added a comment to the discussion: Inquiry about enriching 5.0 Proxy features The introduction of admin API to the proxy is indeed necessary. PTAL @drpmma @xdkxlk GitHub link: https://github.com/apache/rocketmq/discussions/6210#discussioncomment-5152988 This is an automatically sent email for dev@rocketmq.apache.org. To unsubscribe, please send an email to: dev-unsubscr...@rocketmq.apache.org
[GitHub] [rocketmq] ShadowySpirits added a comment to the discussion: rocketmq broker会占用多个端口？
GitHub user ShadowySpirits added a comment to the discussion: rocketmq broker会占用多个端口？ > 在broker配置了listenPort=30911，启动后发现30909和30912都被rocketmq占用了，这是正常的吗？ 30909 被占用是因为启动了 fastRemotingServer https://github.com/apache/rocketmq/blob/88000dac212a0c721a99ca167132920ce0f45f1b/broker/src/main/java/org/apache/rocketmq/broker/BrokerController.java#L429-L435 30912 被占用是供 HA 使用 https://github.com/apache/rocketmq/blob/88000dac212a0c721a99ca167132920ce0f45f1b/container/src/main/java/org/apache/rocketmq/container/BrokerContainerStartup.java#L140 > 另外想问下mqshutdown broker能指定broker吗？ 不能，mqshutdown 是通过 `ps` 来获取 broker pid 的 https://github.com/apache/rocketmq/blob/88000dac212a0c721a99ca167132920ce0f45f1b/distribution/bin/mqshutdown#L19-L30 GitHub link: https://github.com/apache/rocketmq/discussions/6208#discussioncomment-5152947 This is an automatically sent email for dev@rocketmq.apache.org. To unsubscribe, please send an email to: dev-unsubscr...@rocketmq.apache.org
[GitHub] [rocketmq] Hoxxx added a comment to the discussion: rocketmq broker会占用多个端口？
GitHub user Hoxxx added a comment to the discussion: rocketmq broker会占用多个端口？ 另外想问下mqshutdown broker能指定broker吗？ GitHub link: https://github.com/apache/rocketmq/discussions/6208#discussioncomment-5141498 This is an automatically sent email for dev@rocketmq.apache.org. To unsubscribe, please send an email to: dev-unsubscr...@rocketmq.apache.org
[GitHub] [rocketmq] Hoxxx added a comment to the discussion: rocketmq broker会占用多个端口？
GitHub user Hoxxx added a comment to the discussion: rocketmq broker会占用多个端口？ 这个问题估计是namesrv里metadata的问题，把namesrv的controllerStorePath全部删了重建貌似就好了 第一次提示地址被使用；第二次改了端口显示不出来；第三次把controllerStorePath全部干掉重建就显示出来了 GitHub link: https://github.com/apache/rocketmq/discussions/6208#discussioncomment-5140636 This is an automatically sent email for dev@rocketmq.apache.org. To unsubscribe, please send an email to: dev-unsubscr...@rocketmq.apache.org
[GitHub] [rocketmq] Hoxxx edited a comment on the discussion: rocketmq broker会占用多个端口？
GitHub user Hoxxx edited a comment on the discussion: rocketmq broker会占用多个端口？ 现在还有个新问题，broker group 2改了端口后（从30911改成了31911），mqadmin ClusterList 看不到broker group 2，想知道rocketMQ controller支持下面这种架构吗？  GitHub link: https://github.com/apache/rocketmq/discussions/6208#discussioncomment-5140215 This is an automatically sent email for dev@rocketmq.apache.org. To unsubscribe, please send an email to: dev-unsubscr...@rocketmq.apache.org
[GitHub] [rocketmq] Hoxxx added a comment to the discussion: rocketmq broker会占用多个端口？
GitHub user Hoxxx added a comment to the discussion: rocketmq broker会占用多个端口？ 现在还有个新问题，broker group 2改了端口后，mqadmin ClusterList 看不到broker group 2，想知道rocketMQ controller支持下面这种架构吗？  GitHub link: https://github.com/apache/rocketmq/discussions/6208#discussioncomment-5140215 This is an automatically sent email for dev@rocketmq.apache.org. To unsubscribe, please send an email to: dev-unsubscr...@rocketmq.apache.org
[GitHub] [rocketmq] Hoxxx edited a discussion: rocketmq broker会占用多个端口？
GitHub user Hoxxx edited a discussion: rocketmq broker会占用多个端口？ 在broker配置了listenPort=30911，启动后发现30909和30912都被rocketmq占用了，这是正常的吗？ GitHub link: https://github.com/apache/rocketmq/discussions/6208 This is an automatically sent email for dev@rocketmq.apache.org. To unsubscribe, please send an email to: dev-unsubscr...@rocketmq.apache.org
[GitHub] [rocketmq] mxsm edited a comment on the discussion: [5.1.0]关于Dledger和controller疑问
GitHub user mxsm edited a comment on the discussion: [5.1.0]关于Dledger和controller疑问 @SchopenhauerZhang 这种情况下你直接进行切换是不行的， 之前的DLedger主键是用来存储Broker的数据，而Controller模式将数据存储上移了。直接放到了Broker中。与此同时DLedger现在作用是单独作为一个选主组件。 在状态机里面存储的是Broker的一些元数据信息。当你DLedger加载数据的时候Controller实现的状态机是无法识别DLedger里面的数据的，所以你的错误应该是状态机对数据进行解析的时候报错对吗？你可以了解一下5.0版本Controller模块设计文档：https://github.com/apache/rocketmq/wiki/RIP-44-Support-DLedger-Controller 。 不知道这样说是不是能够解答你的问题。 GitHub link: https://github.com/apache/rocketmq/discussions/6172#discussioncomment-5119509 This is an automatically sent email for dev@rocketmq.apache.org. To unsubscribe, please send an email to: dev-unsubscr...@rocketmq.apache.org
[GitHub] [rocketmq] mxsm added a comment to the discussion: [5.1.0]关于Dledger和controller疑问
GitHub user mxsm added a comment to the discussion: [5.1.0]关于Dledger和controller疑问 @SchopenhauerZhang 这种情况下你直接进行切换是不行的， 之前的DLedger主键是用来存储Broker的数据，而Controller模式将数据存储上移了。直接放到了Broker中。与此同时DLedger现在作用是单独作为一个选主组件。 在状态机里面存储的是Broker的一些元数据信息。你可以了解一下5.0版本Controller模块设计文档：https://github.com/apache/rocketmq/wiki/RIP-44-Support-DLedger-Controller 。 不知道这样说是不是能够解答你的问题。 GitHub link: https://github.com/apache/rocketmq/discussions/6172#discussioncomment-5119509 This is an automatically sent email for dev@rocketmq.apache.org. To unsubscribe, please send an email to: dev-unsubscr...@rocketmq.apache.org
[GitHub] [rocketmq] Oliverwqcwrw added a comment to the discussion: com.alibaba.fastjson.JSONException: expect '[', but {, pos 1, line 1, column 2{"name":"Sam Spade"}
GitHub user Oliverwqcwrw added a comment to the discussion:
com.alibaba.fastjson.JSONException: expect '[', but {, pos 1, line 1, column
2{"name":"Sam Spade"}
Thank you for providing the demo. I noticed that you are using rocketmq
integrated by spring-cloud-alibaba. You can raise an issue in the
spring-cloud-alibaba community
[spring-cloud-alibaba](https://github.com/alibaba/spring-cloud-alibaba/issues)
GitHub link:
https://github.com/apache/rocketmq/discussions/6191#discussioncomment-5118914
This is an automatically sent email for dev@rocketmq.apache.org.
To unsubscribe, please send an email to: dev-unsubscr...@rocketmq.apache.org
[GitHub] [rocketmq] SchopenhauerZhang edited a comment on the discussion: [5.1.0]关于Dledger和controller疑问
GitHub user SchopenhauerZhang edited a comment on the discussion: [5.1.0]关于Dledger和controller疑问 let me try，thx。 **问题描述** 另外，可能我没有表述清楚，我其实想问的是DLedger+ controller主备切换 模式的部署文档。 因为我本地部署DLedger是能够成功了，但是DLedger升级到controller主备切换总是失败，所以想问问能不能直接基于DLedger部署controller主备切换。 **部署步骤** `参考官方文档，在Controller模式下，Broker配置必须设置enableControllerMode=true，并填写controllerAddr。` 我在原有（3个节点的）DLedger集群基础上增加了enableControllerMode、controllerAddr两项配置，希望 **实现3个nameserver（内嵌controller）+3个DLedger**。 但是通过getSyncStateSet命令只能看到1个member，导致kill master后切主失败。 **排查思路** 当然我也在排查是否是我部署的姿势不对，检查过配置目前没有看到问题。如果有相关讨论社区希望可以交流一下。 Thx。 GitHub link: https://github.com/apache/rocketmq/discussions/6172#discussioncomment-5117597 This is an automatically sent email for dev@rocketmq.apache.org. To unsubscribe, please send an email to: dev-unsubscr...@rocketmq.apache.org
[GitHub] [rocketmq] SchopenhauerZhang added a comment to the discussion: [5.1.0]关于Dledger和controller疑问
GitHub user SchopenhauerZhang added a comment to the discussion: [5.1.0]关于Dledger和controller疑问 let me try，thx。 GitHub link: https://github.com/apache/rocketmq/discussions/6172#discussioncomment-5117597 This is an automatically sent email for dev@rocketmq.apache.org. To unsubscribe, please send an email to: dev-unsubscr...@rocketmq.apache.org
[GitHub] [rocketmq] yuluo-yx added a comment to the discussion: com.alibaba.fastjson.JSONException: expect '[', but {, pos 1, line 1, column 2{"name":"Sam Spade"}
GitHub user yuluo-yx added a comment to the discussion:
com.alibaba.fastjson.JSONException: expect '[', but {, pos 1, line 1, column
2{"name":"Sam Spade"}
Any Idea?
GitHub link:
https://github.com/apache/rocketmq/discussions/6191#discussioncomment-5117253
This is an automatically sent email for dev@rocketmq.apache.org.
To unsubscribe, please send an email to: dev-unsubscr...@rocketmq.apache.org
[GitHub] [rocketmq] mxsm edited a comment on the discussion: [5.1.0]关于Dledger和controller疑问
GitHub user mxsm edited a comment on the discussion: [5.1.0]关于Dledger和controller疑问 @SchopenhauerZhang 1主2从（DLedger 模式）你只需要按照controller+一主一从的模式（2个broker）部署3个Broker就可以了。 通过Controller模式的选举出来1主剩下的2个Broker就是Slave. 这个就满足你的controller+1主2从。官方文档：https://rocketmq.apache.org/docs/deploymentOperations/03autofailover 这里只是一个例子。例如你想要1主2从： Broker1 ```properties brokerClusterName = DefaultCluster brokerName = broker-a brokerId = -1 brokerRole = SLAVE deleteWhen = 04 fileReservedTime = 48 enableControllerMode = true controllerAddr = 127.0.0.1:9878 namesrvAddr = 127.0.0.1:9876 allAckInSyncStateSet=true listenPort=30911 storePathRootDir=/tmp/rmqstore/node00 storePathCommitLog=/tmp/rmqstore/node00/commitlog ``` Broker2 ```properties brokerClusterName = DefaultCluster brokerName = broker-a brokerId = -1 brokerRole = SLAVE deleteWhen = 04 fileReservedTime = 48 enableControllerMode = true controllerAddr = 127.0.0.1:9878 namesrvAddr = 127.0.0.1:9876 allAckInSyncStateSet=true listenPort=30911 storePathRootDir=/tmp/rmqstore/node00 storePathCommitLog=/tmp/rmqstore/node00/commitlog ``` Broker3 ```properties brokerClusterName = DefaultCluster brokerName = broker-a brokerId = -1 brokerRole = SLAVE deleteWhen = 04 fileReservedTime = 48 enableControllerMode = true controllerAddr = 127.0.0.1:9878 namesrvAddr = 127.0.0.1:9876 allAckInSyncStateSet=true listenPort=30911 storePathRootDir=/tmp/rmqstore/node00 storePathCommitLog=/tmp/rmqstore/node00/commitlog ``` 只需要按照上述的配置文件部署就可以了。 （这里因为storePathRootDir和storePathCommitLog都是一样所以需要部署在不同的机器上面，如果想要部署在同一台机器只需要进行改变位置即可） GitHub link: https://github.com/apache/rocketmq/discussions/6172#discussioncomment-5113859 This is an automatically sent email for dev@rocketmq.apache.org. To unsubscribe, please send an email to: dev-unsubscr...@rocketmq.apache.org
[GitHub] [rocketmq] mxsm added a comment to the discussion: [5.1.0]关于Dledger和controller疑问
GitHub user mxsm added a comment to the discussion: [5.1.0]关于Dledger和controller疑问 @SchopenhauerZhang 1主2从（DLedger 模式）你只需要按照controller+一主一从的模式（2个broker）部署3个Broker就可以了。 通过Controller模式的选举出来1主剩下的2个Broker就是Slave. 这个就满足你的controller+1主2从。 GitHub link: https://github.com/apache/rocketmq/discussions/6172#discussioncomment-5113859 This is an automatically sent email for dev@rocketmq.apache.org. To unsubscribe, please send an email to: dev-unsubscr...@rocketmq.apache.org
[GitHub] [rocketmq] SchopenhauerZhang added a comment to the discussion: [5.1.0]关于Dledger和controller疑问
GitHub user SchopenhauerZhang added a comment to the discussion: [5.1.0]关于Dledger和controller疑问 mq 5.0 缺少Controller 主备自动切换的部署文档；尤其是DLedger模式升级到Controller 主备自动切换模式的文档； 仓库中这块相关的文档只有一下这段： ` （2）原DLedger模式升级到Controller切换架构 由于原DLedger模式消息数据格式与Master-Slave下数据格式存在区别，不提供带数据原地升级的路径。在部署多组Broker的情况下，可以禁写某一组Broker一段时间（只要确认存量消息被全部消费即可，比如根据消息的保存时间来决定），然后清空store目录下除config/topics.json、subscriptionGroup.json下（保留topic和订阅关系的元数据）的其他文件后，进行空盘升级。 ` 有时间可以补充下这块的详细文档吗？ quick start上也是controller+一主一从的模式（2个broker），并没有controller+1主2从（DLedger 模式）的quick start可供参考； 感谢。 GitHub link: https://github.com/apache/rocketmq/discussions/6172#discussioncomment-5113293 This is an automatically sent email for dev@rocketmq.apache.org. To unsubscribe, please send an email to: dev-unsubscr...@rocketmq.apache.org
[GitHub] [rocketmq] ShadowySpirits added a comment to the discussion: Different implements about suporting S3 backend for tiered storage
GitHub user ShadowySpirits added a comment to the discussion: Different implements about suporting S3 backend for tiered storage We should not add the pre-fetching mechanism in the backend service provider. Similar to the file system in OS, the underlying interface reads files according to the specified position and length, and the OS maintains the page cache, which is a read-ahead cache in tiered storage (see [TieredMessageFetcher](https://github.com/apache/rocketmq/blob/develop/tieredstore/src/main/java/org/apache/rocketmq/tieredstore/TieredMessageFetcher.java) for more details). If you want to batch upload, a shared upload buffer is okay. But when the messages are uploaded to s3, the data in the buffer should be cleaned immediately because we do not expect to access hot data from tiered storage. GitHub link: https://github.com/apache/rocketmq/discussions/6176#discussioncomment-5109325 This is an automatically sent email for dev@rocketmq.apache.org. To unsubscribe, please send an email to: dev-unsubscr...@rocketmq.apache.org
[GitHub] [rocketmq] mxsm edited a comment on the discussion: [5.1.0]关于Dledger和controller疑问
GitHub user mxsm edited a comment on the discussion: [5.1.0]关于Dledger和controller疑问 @Hoxxx 1. 副本越多性能会有所下降，这个是Raft算法导致。但是不一定是减半。这个需要具体进行测试 2. DLedger Controller可以内嵌NameServer也可以单独部署，Broker如果部署两个节点那就是一主一从，如果你想要实现高可用并且还能进行切换。建议部署至少2个Broker或者更多。 3. Broker你可以部署多个，当Master宕机下线会从剩下的Broker中重新选择一个Broker作为Master。Controller模式下Broker name相同的多个Broker，最后会选举出一个Broker作为Master. 之前是直接在配置文件中设置BrokerId=0的Broker作为Master 你可以了解一下5.0版本Controller模块设计文档：https://github.com/apache/rocketmq/wiki/RIP-44-Support-DLedger-Controller GitHub link: https://github.com/apache/rocketmq/discussions/6172#discussioncomment-5101420 This is an automatically sent email for dev@rocketmq.apache.org. To unsubscribe, please send an email to: dev-unsubscr...@rocketmq.apache.org
[GitHub] [rocketmq] mxsm added a comment to the discussion: [5.1.0]关于Dledger和controller疑问
GitHub user mxsm added a comment to the discussion: [5.1.0]关于Dledger和controller疑问 @Hoxxx 1. 副本越多性能会有所下降，这个是Raft算法导致。 2. DLedger Controller可以内嵌NameServer也可以单独部署，Broker如果部署两个节点那就是一主一从 3. Broker你可以部署多个，当Master宕机下线会从剩下的Broker中重新选择一个Broker作为Master。 你可以了解一下5.0版本Controller模块设计文档：https://github.com/apache/rocketmq/wiki/RIP-44-Support-DLedger-Controller GitHub link: https://github.com/apache/rocketmq/discussions/6172#discussioncomment-5101420 This is an automatically sent email for dev@rocketmq.apache.org. To unsubscribe, please send an email to: dev-unsubscr...@rocketmq.apache.org
[GitHub] [rocketmq] Hoxxx added a comment to the discussion: [5.1.0]关于Dledger和controller疑问
GitHub user Hoxxx added a comment to the discussion: [5.1.0]关于Dledger和controller疑问 @RongtongJin 大佬，能再麻烦解答下上面的几点疑问吗？ GitHub link: https://github.com/apache/rocketmq/discussions/6172#discussioncomment-5099584 This is an automatically sent email for dev@rocketmq.apache.org. To unsubscribe, please send an email to: dev-unsubscr...@rocketmq.apache.org
[GitHub] [rocketmq] Oliverwqcwrw added a comment to the discussion: Whether a retry is necessary if there is an ACL verification failure
GitHub user Oliverwqcwrw added a comment to the discussion: Whether a retry is necessary if there is an ACL verification failure I will polish it GitHub link: https://github.com/apache/rocketmq/discussions/6168#discussioncomment-5098313 This is an automatically sent email for dev@rocketmq.apache.org. To unsubscribe, please send an email to: dev-unsubscr...@rocketmq.apache.org
[GitHub] [rocketmq] drpmma added a comment to the discussion: Whether a retry is necessary if there is an ACL verification failure
GitHub user drpmma added a comment to the discussion: Whether a retry is necessary if there is an ACL verification failure A new response code is required to denote the unsuccessful authentication. GitHub link: https://github.com/apache/rocketmq/discussions/6168#discussioncomment-5097988 This is an automatically sent email for dev@rocketmq.apache.org. To unsubscribe, please send an email to: dev-unsubscr...@rocketmq.apache.org
[GitHub] [rocketmq] xdkxlk added a comment to the discussion: Whether a retry is necessary if there is an ACL verification failure
GitHub user xdkxlk added a comment to the discussion: Whether a retry is necessary if there is an ACL verification failure It is unnecessary in my opinion GitHub link: https://github.com/apache/rocketmq/discussions/6168#discussioncomment-5097895 This is an automatically sent email for dev@rocketmq.apache.org. To unsubscribe, please send an email to: dev-unsubscr...@rocketmq.apache.org
[GitHub] [rocketmq] xdkxlk added a comment to the discussion: Whether a retry is necessary if there is an ACL verification failure
GitHub user xdkxlk added a comment to the discussion: Whether a retry is necessary if there is an ACL verification failure The AuthenticationInterceptor is only used by Grpc client GitHub link: https://github.com/apache/rocketmq/discussions/6168#discussioncomment-5097880 This is an automatically sent email for dev@rocketmq.apache.org. To unsubscribe, please send an email to: dev-unsubscr...@rocketmq.apache.org
[GitHub] [rocketmq] Hoxxx added a comment to the discussion: [5.1.0]关于Dledger和controller疑问
GitHub user Hoxxx added a comment to the discussion: [5.1.0]关于Dledger和controller疑问 1、我的理解的DLedger，除了功能缺失，性能上在3副本下减半？ 2、如果在nameserver中部署了DLedger Controller，底层的broker是不是只需要部署主从两个节点就OK了？ 3、broker支持1主2从吗？ GitHub link: https://github.com/apache/rocketmq/discussions/6172#discussioncomment-5096822 This is an automatically sent email for dev@rocketmq.apache.org. To unsubscribe, please send an email to: dev-unsubscr...@rocketmq.apache.org
[GitHub] [rocketmq] RongtongJin added a comment to the discussion: [5.1.0]关于Dledger和controller疑问
GitHub user RongtongJin added a comment to the discussion: [5.1.0]关于Dledger和controller疑问 DLedger相关的高可用有两种模式 1. RocketMQ 4.5 之后 DLedger模式被引入 RocketMQ  该架构主要是利用OpenMessaging中名为DLedger的Raft存储库来实现，DLedger存储层是仿照RocketMQ写的简化版本，传输层也用的RocketMQ Remoting，这样的切换架构依靠Raft自选举能力，仍然没有任何外部组件依赖。如图所示，最主要的区别是利用Raft CommitLog代替了原来CommitLog，使CommitLog拥有了选举复制的能力，然后通过角色透传的方式，把Raft的角色透传给外部Broker的角色，Leader对应原来Master的角色，Follower和Candidate对应原来的Slave角色，而Broker与其他外部组件如NameServer，客户端的交互仍然以Master/Slave的形式进行。现在，如果一个Master挂了，依靠Raft自动选主的能力，会重新选出一个Leader，然后通过角色透传变成新的Master对外服务。此外，Raft的算法也保证了数据的一致性，不会出现消息的丢失。 2.RocketMQ 5.0 后的Controller模式 1 中 DLedger 存在以下问题 - Broker组内的副本数必须是3副本及以上才有切换能力，因此成本是有上升的。 - Raft多数派限制导致三副本副本必须两副本响应才能返回，五副本需要三副本才能返回，因此ACK是不够灵活的，这也导致发送延迟和副本冗余间没有一个很好的可协商的方案。 - 由于存储复制链路用的是OpenMessaging DLedger库，导致RocketMQ原生的一些存储能力没办法利用，包括像TransientPool、零拷贝的能力，如果要在Raft模式下使用的话，就需要移植一遍到DLedger库，开发特性以及bug修复也需要做两次，这样的维护和开发成本是非常高的。  因此在RocketMQ 5.0 版本后，DLedger（Raft）能力从原本的复制链路上移到controller，将选主切换能力上移，单独作为一个选主组件。RIP-44提出增加一个DLedgerControlller的选主组件，它是可选部署的，在无切换架构的基础上，部署后经过配置就可以拥有切换的能力，它可以内嵌在Nameserver中，也可以独立部署。如果内嵌在NameServer中，NameServer本身的能力还是无状态的，比如有三个NameServer都内嵌部署了DLedger Controller，如果宕机两个节点，NameServer仍然存在一个可以提供路由服务，DLedger Controller宕机两个节点后由于达不到Raft多数派的要求无法再协助Broker切换，但是消息集群本身正常的收发服务不会受到影响。 如果新建集群，建议使用5.0的controller模式，可以参考相关文档 https://github.com/apache/rocketmq/tree/develop/docs/cn/controller GitHub link: https://github.com/apache/rocketmq/discussions/6172#discussioncomment-5096589 This is an automatically sent email for dev@rocketmq.apache.org. To unsubscribe, please send an email to: dev-unsubscr...@rocketmq.apache.org
[GitHub] [rocketmq] ShadowySpirits added a comment to the discussion: Whether a retry is necessary if there is an ACL verification failure
GitHub user ShadowySpirits added a comment to the discussion: Whether a retry is necessary if there is an ACL verification failure When the request can not pass validation, it seems like returning a broker exception to the client. https://github.com/apache/rocketmq/blob/7cfffe7f48e1db9e9db3641e8ba6aed3e465281c/proxy/src/main/java/org/apache/rocketmq/proxy/grpc/interceptor/AuthenticationInterceptor.java#L67-L71 @drpmma Please take a look. GitHub link: https://github.com/apache/rocketmq/discussions/6168#discussioncomment-5096088 This is an automatically sent email for dev@rocketmq.apache.org. To unsubscribe, please send an email to: dev-unsubscr...@rocketmq.apache.org
[GitHub] [rocketmq-docker] wokwong opened a new issue, #68: Add the list of supported RocketMQ versions
wokwong opened a new issue, #68: URL: https://github.com/apache/rocketmq-docker/issues/68 **FEATURE REQUEST** Add the list of supported RocketMQ versions. -- 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: dev-unsubscr...@rocketmq.apache.org.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [rocketmq-externals] caigy commented on issue #900: Why not find rocketmq-console?
caigy commented on issue #900: URL: https://github.com/apache/rocketmq-externals/issues/900#issuecomment-1384876348 `rocketmq-console` has been graduated and renamed as `rocketmq-dashboard` with new repository: https://github.com/apache/rocketmq-dashboard -- 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: dev-unsubscr...@rocketmq.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [rocketmq-externals] caigy closed issue #900: Why not find rocketmq-console?
caigy closed issue #900: Why not find rocketmq-console? URL: https://github.com/apache/rocketmq-externals/issues/900 -- 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: dev-unsubscr...@rocketmq.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [rocketmq-docker] cryptoya opened a new pull request, #67: [ISSUE #66] Add rocketmq5.x helm chart
cryptoya opened a new pull request, #67: URL: https://github.com/apache/rocketmq-docker/pull/67 Add rocketmq5.x helm chart -- 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: dev-unsubscr...@rocketmq.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [rocketmq-externals] xbronze commented on issue #900: Why not find rocketmq-console?
xbronze commented on issue #900: URL: https://github.com/apache/rocketmq-externals/issues/900#issuecomment-1379907593 > rocketmq-console I guess you are in the master branch, please switch to the dev branch -- 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: dev-unsubscr...@rocketmq.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [rocketmq-externals] xbronze commented on issue #900: Why not find rocketmq-console?
xbronze commented on issue #900: URL: https://github.com/apache/rocketmq-externals/issues/900#issuecomment-1379907376 I guess you are in the master branch, please switch to the develop branch. -- 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: dev-unsubscr...@rocketmq.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [rocketmq-client-python] messense commented on issue #131: Domain name resolution failed causes core dumped
messense commented on issue #131: URL: https://github.com/apache/rocketmq-client-python/issues/131#issuecomment-1378234005 Sorry, it's unlikely there will be updates since rocketmq clients development has moved to https://github.com/apache/rocketmq-clients. -- 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: dev-unsubscr...@rocketmq.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [rocketmq-client-python] spaceack opened a new issue, #131: Domain name resolution failed causes core dumped
spaceack opened a new issue, #131:
URL: https://github.com/apache/rocketmq-client-python/issues/131
## Description
When there are unresolvable domain names, there will be occasional core
dumped.
## env
rocketmq-4.9.2
rocketmq-client-python-1.2.0
rocketmq-client-cpp-2.1.0
## error info
```bash
[root@localhost tmp]# /opt/env/miniconda3/bin/python3 test_mq.py
start consume message
Traceback (most recent call last):
File "test_mq.py", line 20, in
start_consume_message()
File "test_mq.py", line 13, in start_consume_message
consumer.start()
File "/opt/env/miniconda3/lib/python3.7/site-packages/rocketmq/client.py",
line 370, in start
ffi_check(dll.StartPushConsumer(self._handle))
File
"/opt/env/miniconda3/lib/python3.7/site-packages/rocketmq/exceptions.py", line
44, in ffi_check
raise exc_cls(msg)
rocketmq.exceptions.PushConsumerStartFailed: Failed to resolve host
name(testmq1.mq): nodename nor servname provided, or not known,error:-1,in file
line:103
terminate called after throwing an instance of 'rocketmq::MQClientException'
what(): msg: Failed to resolve host name(testmq1.mq): nodename nor
servname provided, or not known,error:-1,in file
line:103
Aborted (core dumped)
```
## code
```python
from rocketmq.client import PushConsumer, ConsumeStatus
import time
def callback(msg):
print(msg.id, msg.body, msg.get_property('property'))
return ConsumeStatus.CONSUME_SUCCESS
def start_consume_message():
consumer = PushConsumer('consumer_group')
consumer.set_name_server_address('testmq1.mq:9876')
consumer.subscribe('TopicTest', callback)
print ('start consume message')
consumer.start()
while True:
time.sleep(3600)
if __name__ == '__main__':
start_consume_message()
```
## gdb info
```gdb
(gdb) bt
#0 0x7f45b42086eb in raise () from /lib64/libc.so.6
#1 0x7f45b4209a11 in abort () from /lib64/libc.so.6
#2 0x7f45a676e84a in __gnu_cxx::__verbose_terminate_handler ()
at
/home/nwani/m3/conda-bld/compilers_linux-64_1560109574129/work/.build/x86_64-conda_cos6-linux-gnu/src/gcc/libstdc++-v3/libsupc++/vterminate.cc:95
#3 0x7f45a676cf47 in __cxxabiv1::__terminate (handler=)
at
/home/nwani/m3/conda-bld/compilers_linux-64_1560109574129/work/.build/x86_64-conda_cos6-linux-gnu/src/gcc/libstdc++-v3/libsupc++/eh_terminate.cc:47
#4 0x7f45a676cf7d in std::terminate () at
/home/nwani/m3/conda-bld/compilers_linux-64_1560109574129/work/.build/x86_64-conda_cos6-linux-gnu/src/gcc/libstdc++-v3/libsupc++/eh_terminate.cc:57
#5 0x7f45a676d15a in __cxxabiv1::__cxa_throw (obj=0x7f457c0044a0,
tinfo=0x7f45a6b6fdd8 ,
dest=0x7f45a696e1f0 )
at
/home/nwani/m3/conda-bld/compilers_linux-64_1560109574129/work/.build/x86_64-conda_cos6-linux-gnu/src/gcc/libstdc++-v3/libsupc++/eh_throw.cc:95
#6 0x7f45a6a3e817 in
rocketmq::TcpTransport::getInetAddr(std::__cxx11::basic_string, std::allocator >&) () from
/opt/env/miniconda3/lib/librocketmq.so
#7 0x7f45a6a3f4c3 in
rocketmq::TcpTransport::connect(std::__cxx11::basic_string, std::allocator > const&, int) () from
/opt/env/miniconda3/lib/librocketmq.so
#8 0x7f45a6a38f5d in
rocketmq::TcpRemotingClient::CreateTransport(std::__cxx11::basic_string, std::allocator > const&, bool) ()
from /opt/env/miniconda3/lib/librocketmq.so
#9 0x7f45a6a39399 in
rocketmq::TcpRemotingClient::CreateNameServerTransport(bool) () from
/opt/env/miniconda3/lib/librocketmq.so
#10 0x7f45a6a3959b in
rocketmq::TcpRemotingClient::GetTransport(std::__cxx11::basic_string, std::allocator > const&, bool) ()
from /opt/env/miniconda3/lib/librocketmq.so
#11 0x7f45a6a3b764 in
rocketmq::TcpRemotingClient::invokeSync(std::__cxx11::basic_string, std::allocator > const&,
rocketmq::RemotingCommand&, int) ()
from /opt/env/miniconda3/lib/librocketmq.so
#12 0x7f45a696cf8b in
rocketmq::MQClientAPIImpl::getTopicRouteInfoFromNameServer(std::__cxx11::basic_string, std::allocator > const&, int,
rocketmq::SessionCredentials const&) () from
/opt/env/miniconda3/lib/librocketmq.so
#13 0x7f45a697bcb5 in
rocketmq::MQClientFactory::updateTopicRouteInfoFromNameServer(std::__cxx11::basic_string, std::allocator > const&,
rocketmq::SessionCredentials const&, bool) () from
/opt/env/miniconda3/lib/librocketmq.so
#14 0x7f45a697f3f9 in
rocketmq::MQClientFactory::updateTopicRouteInfo(boost::system::error_code&,
boost::shared_ptr,
boost::asio::deadline_timer_service > > >) () from
/opt/env/miniconda3/lib/librocketmq.so
#15 0x7f45a6980ba9 in
boost::asio::detail::wait_handler,
boost::asio::deadline_timer_service > > > >,
boost::_bi::list3,
boost::_bi::value,
boost::_bi::value,
boost::asio::deadline_timer_service > > > > > >
[GitHub] [rocketmq-schema-registry] codecov-commenter commented on pull request #76: [ISSUE #49] Support cache for SchemaRegistryClient
codecov-commenter commented on PR #76: URL: https://github.com/apache/rocketmq-schema-registry/pull/76#issuecomment-1374720223 # [Codecov](https://codecov.io/gh/apache/rocketmq-schema-registry/pull/76?src=pr=h1_medium=referral_source=github_content=comment_campaign=pr+comments_term=The+Apache+Software+Foundation) Report > Merging [#76](https://codecov.io/gh/apache/rocketmq-schema-registry/pull/76?src=pr=desc_medium=referral_source=github_content=comment_campaign=pr+comments_term=The+Apache+Software+Foundation) (1d90dde) into [main](https://codecov.io/gh/apache/rocketmq-schema-registry/commit/3115e5a07d808ed23ad2ae5277970f53d1fa5d4c?el=desc_medium=referral_source=github_content=comment_campaign=pr+comments_term=The+Apache+Software+Foundation) (3115e5a) will **decrease** coverage by `3.21%`. > The diff coverage is `0.00%`. ```diff @@ Coverage Diff @@ ## main #76 +/- ## - Coverage 19.54% 16.33% -3.22% Complexity 67 67 Files45 46 +1 Lines 977 1169 +192 Branches 52 87 +35 Hits191 191 - Misses 768 960 +192 Partials 18 18 ``` | [Impacted Files](https://codecov.io/gh/apache/rocketmq-schema-registry/pull/76?src=pr=tree_medium=referral_source=github_content=comment_campaign=pr+comments_term=The+Apache+Software+Foundation) | Coverage Δ | | |---|---|---| | [...ma/registry/client/CachedSchemaRegistryClient.java](https://codecov.io/gh/apache/rocketmq-schema-registry/pull/76?src=pr=tree_medium=referral_source=github_content=comment_campaign=pr+comments_term=The+Apache+Software+Foundation#diff-Y2xpZW50L3NyYy9tYWluL2phdmEvb3JnL2FwYWNoZS9yb2NrZXRtcS9zY2hlbWEvcmVnaXN0cnkvY2xpZW50L0NhY2hlZFNjaGVtYVJlZ2lzdHJ5Q2xpZW50LmphdmE=) | `0.00% <0.00%> (ø)` | | | [...a/registry/client/SchemaRegistryClientFactory.java](https://codecov.io/gh/apache/rocketmq-schema-registry/pull/76?src=pr=tree_medium=referral_source=github_content=comment_campaign=pr+comments_term=The+Apache+Software+Foundation#diff-Y2xpZW50L3NyYy9tYWluL2phdmEvb3JnL2FwYWNoZS9yb2NrZXRtcS9zY2hlbWEvcmVnaXN0cnkvY2xpZW50L1NjaGVtYVJlZ2lzdHJ5Q2xpZW50RmFjdG9yeS5qYXZh) | `0.00% <0.00%> (ø)` | | :mega: We’re building smart automated test selection to slash your CI/CD build times. [Learn more](https://about.codecov.io/iterative-testing/?utm_medium=referral_source=github_content=comment_campaign=pr+comments_term=The+Apache+Software+Foundation) -- 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: dev-unsubscr...@rocketmq.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [rocketmq-schema-registry] joeCarf commented on pull request #76: [ISSUE #49] Support cache for SchemaRegistryClient
joeCarf commented on PR #76: URL: https://github.com/apache/rocketmq-schema-registry/pull/76#issuecomment-1374715825 @MatrixHB PTAL -- 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: dev-unsubscr...@rocketmq.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [rocketmq-schema-registry] joeCarf opened a new pull request, #76: [ISSUE #49] Support cache for SchemaRegistryClient
joeCarf opened a new pull request, #76: URL: https://github.com/apache/rocketmq-schema-registry/pull/76 Support cache for SchemaRegistryClient -- 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: dev-unsubscr...@rocketmq.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [rocketmq-client-rust] dependabot[bot] opened a new pull request, #4: Bump tokio from 1.17.0 to 1.18.4
dependabot[bot] opened a new pull request, #4: URL: https://github.com/apache/rocketmq-client-rust/pull/4 Bumps [tokio](https://github.com/tokio-rs/tokio) from 1.17.0 to 1.18.4. Release notes Sourced from https://github.com/tokio-rs/tokio/releases;>tokio's releases. Tokio v1.18.3 1.18.3 (September 27, 2022) This release removes the dependency on the once_cell crate to restore the MSRV of the 1.18.x LTS release. (https://github-redirect.dependabot.com/tokio-rs/tokio/issues/5048;>#5048) https://github-redirect.dependabot.com/tokio-rs/tokio/issues/5048;>#5048: https://github-redirect.dependabot.com/tokio-rs/tokio/pull/5048;>tokio-rs/tokio#5048 Tokio v1.18.2 1.18.2 (May 5, 2022) Add missing features for the winapi dependency. (https://github-redirect.dependabot.com/tokio-rs/tokio/issues/4663;>#4663) https://github-redirect.dependabot.com/tokio-rs/tokio/issues/4663;>#4663: https://github-redirect.dependabot.com/tokio-rs/tokio/pull/4663;>tokio-rs/tokio#4663 Tokio v1.18.1 1.18.1 (May 2, 2022) The 1.18.0 release broke the build for targets without 64-bit atomics when building with tokio_unstable. This release fixes that. (https://github-redirect.dependabot.com/tokio-rs/tokio/issues/4649;>#4649) https://github-redirect.dependabot.com/tokio-rs/tokio/issues/4649;>#4649: https://github-redirect.dependabot.com/tokio-rs/tokio/pull/4649;>tokio-rs/tokio#4649 Tokio v1.18.0 1.18.0 (April 27, 2022) This release adds a number of new APIs in tokio::net, tokio::signal, and tokio::sync. In addition, it adds new unstable APIs to tokio::task (Ids for uniquely identifying a task, and AbortHandle for remotely cancelling a task), as well as a number of bugfixes. Fixed blocking: add missing #[track_caller] for spawn_blocking (https://github-redirect.dependabot.com/tokio-rs/tokio/issues/4616;>#4616) macros: fix select macro to process 64 branches (https://github-redirect.dependabot.com/tokio-rs/tokio/issues/4519;>#4519) net: fix try_io methods not calling Mio's try_io internally (https://github-redirect.dependabot.com/tokio-rs/tokio/issues/4582;>#4582) runtime: recover when OS fails to spawn a new thread (https://github-redirect.dependabot.com/tokio-rs/tokio/issues/4485;>#4485) Added net: add UdpSocket::peer_addr (https://github-redirect.dependabot.com/tokio-rs/tokio/issues/4611;>#4611) net: add try_read_buf method for named pipes (https://github-redirect.dependabot.com/tokio-rs/tokio/issues/4626;>#4626) signal: add SignalKind Hash/Eq impls and c_int conversion (https://github-redirect.dependabot.com/tokio-rs/tokio/issues/4540;>#4540) signal: add support for signals up to SIGRTMAX (https://github-redirect.dependabot.com/tokio-rs/tokio/issues/4555;>#4555) sync: add watch::Sender::send_modify method (https://github-redirect.dependabot.com/tokio-rs/tokio/issues/4310;>#4310) sync: add broadcast::Receiver::len method (https://github-redirect.dependabot.com/tokio-rs/tokio/issues/4542;>#4542) sync: add watch::Receiver::same_channel method (https://github-redirect.dependabot.com/tokio-rs/tokio/issues/4581;>#4581) sync: implement Clone for RecvError types (https://github-redirect.dependabot.com/tokio-rs/tokio/issues/4560;>#4560) Changed ... (truncated) Commits https://github.com/tokio-rs/tokio/commit/9241c3eddf4a6a218681b088d71f7191513e2376;>9241c3e chore: prepare Tokio v1.18.4 release https://github.com/tokio-rs/tokio/commit/699573d550fabf4bfb45d82505d6709faaae9037;>699573d net: fix named pipes server configuration builder https://github.com/tokio-rs/tokio/commit/5c76d070e28bd9153ec72f13d0ebe24935b9dea0;>5c76d07 chore: prepare Tokio v1.18.3 (https://github-redirect.dependabot.com/tokio-rs/tokio/issues/5051;>#5051) https://github.com/tokio-rs/tokio/commit/05e661490b87a3d60a8342535bdc9d213048519c;>05e6614 chore: don't use once_cell for 1.18.x LTS release (https://github-redirect.dependabot.com/tokio-rs/tokio/issues/5048;>#5048) https://github.com/tokio-rs/tokio/commit/7aa1566cde7e04cebe60711ed6ce2f8b277158e9;>7aa1566 chore: prepare Tokio v1.18.2 https://github.com/tokio-rs/tokio/commit/7c8e552f290a7cbae21f6d3343c2ee26c418d2fb;>7c8e552 windows: add features for winapi (https://github-redirect.dependabot.com/tokio-rs/tokio/issues/4663;>#4663) https://github.com/tokio-rs/tokio/commit/148bea82ee15974e64d8fc9292c2066a7278cebc;>148bea8 tokio: prepare Tokio v1.18.1 (https://github-redirect.dependabot.com/tokio-rs/tokio/issues/4650;>#4650) https://github.com/tokio-rs/tokio/commit/dc54aec1c785e334c23a0c8f249e71a8241f0d1d;>dc54aec metrics: use mocked AtomicU64 in IO metrics driver (https://github-redirect.dependabot.com/tokio-rs/tokio/issues/4649;>#4649) https://github.com/tokio-rs/tokio/commit/fa665b91a8f7bbf0ab234f60f28ef25e5afac10b;>fa665b9 macros: always emit return statement
[GitHub] [rocketmq-docker] cryptoya opened a new issue, #66: Add rocketmq5.x helm chart
cryptoya opened a new issue, #66: URL: https://github.com/apache/rocketmq-docker/issues/66 add helm chart and dockerfile for CI -- 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: dev-unsubscr...@rocketmq.apache.org.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [rocketmq-schema-registry] joeCarf commented on issue #49: Support cache for SchemaRegistryClient
joeCarf commented on issue #49: URL: https://github.com/apache/rocketmq-schema-registry/issues/49#issuecomment-1370587302 > The client obtains the schema through `schemaRegistryClient`. It is necessary to consider adding schema cache on the client side, to avoid too much remote requests for serialization or deserialization. > > Cache needs to be designed with reasonable key-value struct and expiration mechanism. hi, @MatrixHB 我最近在设计客户端缓存，同时也参考了kafka schema registry的实现，但在过程中遇到了一点问题想和您讨论一下 ： 1. 在使用过程中哪些函数的使用频率更高，还是说对于client中的所有函数都需要进行缓存呢 2. 我理解缓存主要应用于getschema的各个函数中，但由于查询的入参组合种类很多，我可能不得不对于每种组合都进行缓存。例如对于getSchemaByRecordId函数，缓存的key需要设置为SubjectAndId；而在getSchemaBySubjectAndVersion中，缓存的key则需要为SubjectAndVersion，因此就需要两个map来进行分别存储。这种方法的缺点在于会存在一些重复的value，占用的空间更多，因此想和您讨论一下是否有更好的解决方法。 3. 由于客户端中的getschema方法需要的返回值都是GetSchemaResponse类型，因此我的缓存value也保存这个类型的值。这样的优点在于能够直接返回缓存中的value，但是缺点在于占用更多的空间，并且在register的过程中可能无法更新缓存（因为数据无法拼接成一个GetSchemaResponse）。我暂时没有想到更好的办法 -- 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: dev-unsubscr...@rocketmq.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [rocketmq-externals] coder-PengWenHao opened a new issue, #900: Why not find rocketmq-console?
coder-PengWenHao opened a new issue, #900: URL: https://github.com/apache/rocketmq-externals/issues/900 rocketmq-console -- 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: dev-unsubscr...@rocketmq.apache.org.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [rocketmq-schema-registry] sunxiaojian commented on pull request #75: [ISSUE #73]Remove validation when updating schema
sunxiaojian commented on PR #75: URL: https://github.com/apache/rocketmq-schema-registry/pull/75#issuecomment-1367917355 > compatibility check is specially for updating schema, why remove?? Currently, JSON schema compatibility check unsupported -- 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: dev-unsubscr...@rocketmq.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [rocketmq-schema-registry] joeCarf commented on issue #49: Support cache for SchemaRegistryClient
joeCarf commented on issue #49: URL: https://github.com/apache/rocketmq-schema-registry/issues/49#issuecomment-1367910298 hi, plz assign this to me -- 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: dev-unsubscr...@rocketmq.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [rocketmq-schema-registry] MatrixHB commented on pull request #75: [ISSUE #73]Remove validation when updating schema
MatrixHB commented on PR #75: URL: https://github.com/apache/rocketmq-schema-registry/pull/75#issuecomment-1367856078 compatibility check is specially for updating schema, why remove?? -- 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: dev-unsubscr...@rocketmq.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [rocketmq-schema-registry] sunxiaojian opened a new pull request, #75: [ISSUE #73]Remove validation when updating schema
sunxiaojian opened a new pull request, #75: URL: https://github.com/apache/rocketmq-schema-registry/pull/75 Remove validation when updating schema -- 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: dev-unsubscr...@rocketmq.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
