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
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
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,
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
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
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
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
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
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
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
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
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
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
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
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
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,
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:
GitHub user RongtongJin edited a comment on the discussion: 关于过期文件删除问题
>
GitHub user RongtongJin added a comment to the discussion: 关于过期文件删除问题
>
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,
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,
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,
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
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,
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:
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:
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
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:
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
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:
GitHub user mz0113 edited a discussion: v5.0.0 Pop消费模式下,很多消息显示重试次数达上千次
现象:
consumer.getReconsumeTimes() 返回值几百到几千之间 , 如图 . 正常应该是默认的16次, 但是这个Topic就很奇怪
消费模式为并发消费,POP模式 。schedule queue-0队列因此堆积了几千万消息。revive队列也很大,但是实际上我消息量很小,tps也就几
GitHub user mz0113 edited a discussion: v5.0.0 Pop消费模式下,很多消息显示重试次数达上千次
现象:
consumer.getReconsumeTimes() 返回值几百到几千之间 , 如图 . 正常应该是默认的16次, 但是这个Topic就很奇怪
消费模式为并发消费,POP模式 。
![image](https://user-images.githubusercontent.com/42512469/223314667-609cb3b0-b33d-4588-aae4-bab50ae5cdc6.png)
GitHub link:
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主备切换。
> **部署步骤**
>
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
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
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:
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
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:
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,
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
GitHub user xcfuu added a comment to the discussion: 从节点不工作,监控面板上没有消费消息
主
msgGetTotalTodayMorning : 19764858
msgGetTotalTodayNow : 19828834
msgGetTotalYesterdayMorning : 19621677
从
msgGetTotalTodayMorning : 0
msgGetTotalTodayNow : 0
GitHub user xcfuu edited a comment on the discussion: 从节点不工作,监控面板上没有消费消息
![image](https://user-images.githubusercontent.com/29519964/222317286-8d7967c4-0aaf-48a0-8e88-c448a957074d.png)
master日志
GitHub link:
https://github.com/apache/rocketmq/discussions/6218#discussioncomment-5173990
GitHub user xcfuu added a comment to the discussion: 从节点不工作,监控面板上没有消费消息
![image](https://user-images.githubusercontent.com/29519964/222317286-8d7967c4-0aaf-48a0-8e88-c448a957074d.png)
GitHub link:
https://github.com/apache/rocketmq/discussions/6218#discussioncomment-5173990
This is an
GitHub user RongtongJin added a comment to the discussion: 从节点不工作,监控面板上没有消费消息
> ![image](https://user-images.githubusercontent.com/29519964/222305932-c58abb3d-3f5e-4db5-8c1f-7a3ab06b7a6d.png)
> 没啥报错日志
WARN的就是报错,看这个由于某些原因,Slave和Matser频繁断连。。看看Master的store日志吧
GitHub link:
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
GitHub user xcfuu edited a discussion: 从节点不工作,监控面板上没有消费消息
![image](https://user-images.githubusercontent.com/29519964/222093620-cf94fea9-f80d-490f-b4de-7b6375b2f35c.png)
![image](https://user-images.githubusercontent.com/29519964/222093795-899a08c4-1e07-4f42-81db-61acdefa8355.png)
版本
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:
GitHub user xcfuu added a comment to the discussion: 从节点不工作,监控面板上没有消费消息
主节点
![image](https://user-images.githubusercontent.com/29519964/222307552-e332f5ab-3b29-4828-ac37-1909e0d1f55c.png)
从节点
GitHub user xcfuu added a comment to the discussion: 从节点不工作,监控面板上没有消费消息
![image](https://user-images.githubusercontent.com/29519964/222305932-c58abb3d-3f5e-4db5-8c1f-7a3ab06b7a6d.png)
没啥报错日志
GitHub link:
https://github.com/apache/rocketmq/discussions/6218#discussioncomment-5172957
This
GitHub user xcfuu added a comment to the discussion: 从节点不工作,监控面板上没有消费消息
![image](https://user-images.githubusercontent.com/29519964/222305501-8492bd3c-5c02-4777-867d-eb97ef9e8fe6.png)
基本都是这些日志
GitHub link:
https://github.com/apache/rocketmq/discussions/6218#discussioncomment-5172940
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,
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
GitHub user xcfuu edited a discussion: 从节点不工作,监控面板上没有消费消息
![image](https://user-images.githubusercontent.com/29519964/222093620-cf94fea9-f80d-490f-b4de-7b6375b2f35c.png)
![image](https://user-images.githubusercontent.com/29519964/222093795-899a08c4-1e07-4f42-81db-61acdefa8355.png)
GitHub user xcfuu edited a discussion: 从节点不工作,监控面板上没有消费消息
![image](https://user-images.githubusercontent.com/29519964/222093620-cf94fea9-f80d-490f-b4de-7b6375b2f35c.png)
![image](https://user-images.githubusercontent.com/29519964/222093795-899a08c4-1e07-4f42-81db-61acdefa8355.png)
No error
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
GitHub user ShadowySpirits added a comment to the discussion: rocketmq
broker会占用多个端口?
> 在broker配置了listenPort=30911,启动后发现30909和30912都被rocketmq占用了,这是正常的吗?
30909 被占用是因为启动了 fastRemotingServer
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,
GitHub user Hoxxx added a comment to the discussion: rocketmq broker会占用多个端口?
这个问题估计是namesrv里metadata的问题,把namesrv的controllerStorePath全部删了重建貌似就好了
第一次提示地址被使用;第二次改了端口显示不出来;第三次把controllerStorePath全部干掉重建就显示出来了
GitHub link:
GitHub user Hoxxx edited a comment on the discussion: rocketmq broker会占用多个端口?
现在还有个新问题,broker group 2改了端口后(从30911改成了31911),mqadmin ClusterList 看不到broker
group 2,想知道rocketMQ controller支持下面这种架构吗?
GitHub user Hoxxx added a comment to the discussion: rocketmq broker会占用多个端口?
现在还有个新问题,broker group 2改了端口后,mqadmin ClusterList 看不到broker group 2,想知道rocketMQ
controller支持下面这种架构吗?
![image](https://user-images.githubusercontent.com/2639432/221792956-7dce187f-0e1f-482e-8cd9-2c9c088cbce2.png)
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
GitHub user mxsm edited a comment on the discussion:
[5.1.0]关于Dledger和controller疑问
@SchopenhauerZhang 这种情况下你直接进行切换是不行的,
之前的DLedger主键是用来存储Broker的数据,而Controller模式将数据存储上移了。直接放到了Broker中。与此同时DLedger现在作用是单独作为一个选主组件。
GitHub user mxsm added a comment to the discussion:
[5.1.0]关于Dledger和controller疑问
@SchopenhauerZhang 这种情况下你直接进行切换是不行的,
之前的DLedger主键是用来存储Broker的数据,而Controller模式将数据存储上移了。直接放到了Broker中。与此同时DLedger现在作用是单独作为一个选主组件。
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
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主备切换。
**部署步骤**
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,
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
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.
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:
GitHub user SchopenhauerZhang added a comment to the discussion:
[5.1.0]关于Dledger和controller疑问
mq 5.0 缺少Controller 主备自动切换的部署文档;尤其是DLedger模式升级到Controller 主备自动切换模式的文档;
仓库中这块相关的文档只有一下这段:
`
(2)原DLedger模式升级到Controller切换架构
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
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.
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。
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
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
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
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
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
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
GitHub user RongtongJin added a comment to the discussion:
[5.1.0]关于Dledger和controller疑问
DLedger相关的高可用有两种模式
1. RocketMQ 4.5 之后 DLedger模式被引入 RocketMQ
![image](https://user-images.githubusercontent.com/21963954/221104220-6a713f4f-7963-4ef2-9d1d-73fe10d74641.png)
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.
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
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
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
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.
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
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
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
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
codecov-commenter commented on PR #76:
URL:
https://github.com/apache/rocketmq-schema-registry/pull/76#issuecomment-1374720223
#
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
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
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
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
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
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.
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
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
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
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
201 - 300 of 43000 matches
Mail list logo