GitHub user ShadowySpirits added a comment to the discussion: proxy module
monitoring indicators are improved
It's good for me. Looking forward to your pr.
GitHub link:
https://github.com/apache/rocketmq/discussions/6405#discussioncomment-5429936
This is an automatically sent email for
GitHub user RongtongJin added a comment to the discussion: MessageStore
writeable when HA switch
在角色切换时禁止写入这个方案之前也一直有考虑。当前没有这么做有以下几点
1.备切主ChangeToMaster
- 先完成转换，最后再设置成主
- 备正常情况下不会有消息写入（先与master断开恢复完topicQueueTable，再变成主向nameserver注册对外提供服务）
- 备不存在内部二级消息的转换
GitHub user echooymxq edited a discussion: MessageStore writeable when HA switch
我刚看到这个PR，https://github.com/apache/rocketmq/pull/6345.
我想我们是否有必要在changeMaster前设置messageStore的RunningFlag是不可写的，这样这个PR是不是没必要了，同时也避免内部延时消息的写入。
/cc @RongtongJin
GitHub link:
GitHub user echooymxq edited a discussion: MessageStore writeable when HA swicth
我刚看到这个PR，https://github.com/apache/rocketmq/pull/6345.
我想我们是否有必要在changeMaster前设置messageStore的RunningFlag是不可写的，这样这个PR是不是没必要了，同时也避免内部延时消息的写入。
/cc @RongtongJin
GitHub link:
GitHub user socutes edited a comment on the discussion: proxy module monitoring
indicators are improved
I understand. It has been adjusted. Thank you very much. I will develop based
on the tweaked content.What do you think?
GitHub link:
GitHub user socutes edited a discussion: proxy module monitoring indicators are
improved
Current proxy module monitoring indicators are not perfect, need to improve the
monitoring indicators for connection, time, thread several dimensions.add
metrics for both the node and Topic dimensions
GitHub user socutes added a comment to the discussion: proxy module monitoring
indicators are improved
I understand. It has been adjusted. Thank you very much. I will develop based
on the tweaked content.
GitHub link:
GitHub user ShadowySpirits added a comment to the discussion: proxy module
monitoring indicators are improved
The histogram metrics rocketmq_rpc_latency will be split into three separate
metrics internally:
- rocketmq_rpc_latency_count
- rocketmq_rpc_latency_sum
- rocketmq_rpc_latency_bucket
GitHub user quattro-abc added a comment to the discussion: CODE: 2 DESC:
[REJECTREQUEST]system busy, start flow control for a while BROKER
Thank you very much.
GitHub link:
https://github.com/apache/rocketmq/discussions/6432#discussioncomment-5400045
This is an automatically sent
GitHub user socutes added a comment to the discussion: Discuss the handling of
unused function arguments
> Agree. Do it!
Yes, I will submit this change if the community thinks it can be done
GitHub link:
https://github.com/apache/rocketmq/discussions/6444#discussioncomment-5399502
GitHub user echooymxq added a comment to the discussion: Discuss the handling
of unused function arguments
Agree. Do it!
GitHub link:
https://github.com/apache/rocketmq/discussions/6444#discussioncomment-5399440
This is an automatically sent email for dev@rocketmq.apache.org.
To
GitHub user socutes edited a discussion: Discuss the handling of unused
function arguments
There are many functions in the current code that need to pass arguments, but
the arguments are not used. The current discovery is mainly in the
DefaultRequestProcessor in nameserver. It's a similar
GitHub user socutes edited a discussion: proxy module monitoring indicators are
improved
Current proxy module monitoring indicators are not perfect, need to improve the
monitoring indicators for connection, time, thread several dimensions.add
metrics for both the node and Topic dimensions
GitHub user socutes edited a discussion: proxy module monitoring indicators are
improved
Current proxy module monitoring indicators are not perfect, need to improve the
monitoring indicators for connection, time, thread several dimensions.add
metrics for both the node and Topic dimensions
GitHub user socutes edited a comment on the discussion: proxy module monitoring
indicators are improved
@ShadowySpirits Thank you very much for your advice
rocketmq_response_code_total： The number of times each return code is counted
rocketmq_request_total：Indicates the number of requests for
GitHub user socutes deleted a comment on the discussion: proxy module
monitoring indicators are improved
rocketmq_response_code_total： The number of times each return code is counted
rocketmq_request_total：Indicates the number of requests for each interface
These two metrics are different from
GitHub user socutes added a comment to the discussion: proxy module monitoring
indicators are improved
rocketmq_response_code_total： The number of times each return code is counted
rocketmq_request_total：Indicates the number of requests for each interface
These two metrics are different from
GitHub user socutes edited a discussion: proxy module monitoring indicators are
improved
Current proxy module monitoring indicators are not perfect, need to improve the
monitoring indicators for connection, time, thread several dimensions.add
metrics for both the node and Topic dimensions
GitHub user socutes added a comment to the discussion: proxy module monitoring
indicators are improved
@ShadowySpirits Thank you very much for your advice
1 and 2 will follow your suggestions. I originally thought that these
indicators in the second point might be used in troubleshooting
GitHub user ShadowySpirits added a comment to the discussion: CODE: 2 DESC:
[REJECTREQUEST]system busy, start flow control for a while BROKER
I noticed that you are getting an exception while trying to send messages. This
could be due to high disk pressure. See the following code for more
GitHub user ShadowySpirits added a comment to the discussion: proxy module
monitoring indicators are improved
I'd like to give some suggestions for you.
1. keep the metrics name and label as same as that of the broker
- rocketmq_response_code_total, rocketmq_request_total ->
GitHub user socutes added a comment to the discussion: proxy module monitoring
indicators are improved
@ShadowySpirits @drpmma Take a look
GitHub link:
https://github.com/apache/rocketmq/discussions/6405#discussioncomment-5381625
This is an automatically sent email for
GitHub user socutes edited a discussion: proxy module monitoring indicators are
improved
Current proxy module monitoring indicators are not perfect, need to improve the
monitoring indicators for connection, time, thread several dimensions.add
metrics for both the node and Topic dimensions
GitHub user socutes edited a discussion: proxy module monitoring indicators are
improved
Current proxy module monitoring indicators are not perfect, need to improve the
monitoring indicators for connection, time, thread several dimensions.add
metrics for both the node and Topic dimensions
GitHub user socutes edited a discussion: proxy module monitoring indicators are
improved
Current proxy module monitoring indicators are not perfect, need to improve the
monitoring indicators for connection, time, thread several dimensions.
It is recommended to add the following indicators:
1.
GitHub user socutes edited a discussion: proxy module monitoring indicators are
improved
Current proxy module monitoring indicators are not perfect, need to improve the
monitoring indicators for connection, time, thread several dimensions.
It is recommended to add the following indicators:
1.
GitHub user orchidFang added a comment to the discussion: updateSubGroup
command set retryPolicy raise JSON Exception
thanks,it's work.
GitHub link:
https://github.com/apache/rocketmq/discussions/6425#discussioncomment-5378108
This is an automatically sent email for
GitHub user drpmma added a comment to the discussion: Create subscriptionGroup
through the command line and set the maximum number of retries for
retryMaxTimes, which does not take effect：RocketMQ4.9.4
The gRPC client uses the `retryMaxTimes` in `SubscriptionGroupConfig`.
See
GitHub user socutes edited a discussion: proxy module monitoring indicators are
improved
Current proxy module monitoring indicators are not perfect, need to improve the
monitoring indicators for connection, time, thread several dimensions.
It is recommended to add the following indicators:
1.
GitHub user socutes edited a discussion: proxy module monitoring indicators are
improved
Current proxy module monitoring indicators are not perfect, need to improve the
monitoring indicators for connection, time, thread several dimensions.
It is recommended to add the following indicators:
1.
GitHub user ShadowySpirits added a comment to the discussion: updateSubGroup
command set retryPolicy raise JSON Exception
Please add quotation marks around your JSON string and include the `-c` option.
```bash
./mqadmin updateSubGroup -n localhost:9876 -g system -p
GitHub user orchidFang edited a discussion: updateSubGroup command set
retryPolicy raise JSON Exception
使用updateSubGroup设置重试策略时，经检查json配置没有问题，但报json解析错误。
COMMAND:
./mqadmin updateSubGroup -n localhost:9876 -g system -p
GitHub user orchidFang edited a discussion: updateSubGroup command set
retryPolicy can raise JSON Exception
使用updateSubGroup设置重试策略时，经检查json配置没有问题，但报json解析错误。
COMMAND:
./mqadmin updateSubGroup -n localhost:9876 -g system -p
GitHub user RongtongJin added a comment to the discussion: Prepare to release
Apache RocketMQ 4.9.5
Which issue or pr are you talking about？
GitHub link:
https://github.com/apache/rocketmq/discussions/6388#discussioncomment-5376200
This is an automatically sent email for
GitHub user yiduwangkai added a comment to the discussion: Prepare to release
Apache RocketMQ 4.9.5
Whether the client - side flow control can also come in?
GitHub link:
https://github.com/apache/rocketmq/discussions/6388#discussioncomment-5376150
This is an automatically sent email
GitHub user ShadowySpirits added a comment to the discussion: proxy module
monitoring indicators are improved
@socutes For your reference, here's some previous work in #5350. I'd suggest
you briefly outline your metrics specification and implementation approach.
This will help the community
GitHub user drpmma added a comment to the discussion: proxy module monitoring
indicators are improved
Could you please write a specification about metric as listed in the
GitHub user socutes added a comment to the discussion: proxy module monitoring
indicators are improved
@xdkxlk @drpmma Take a look
GitHub link:
https://github.com/apache/rocketmq/discussions/6405#discussioncomment-5364253
This is an automatically sent email for dev@rocketmq.apache.org.
GitHub user RongtongJin edited a discussion: Prepare to release Apache RocketMQ
4.9.5
Hello RocketMQ Community,
This is the discussion for the release of Apache RocketMQ 4.9.5 Release.
If there are any important pull requests that need to be merged into the 4.9.x
LTS branch, please let me
GitHub user RongtongJin edited a discussion: Prepare to release Apache RocketMQ
4.9.5
Hello RocketMQ Community,
This is the discussion for the release of Apache RocketMQ 4.9.5 Release.
If there are any pull requests that need to be merged into the 4.9.x LTS
branch, please let me know.
GitHub user ShadowySpirits added a comment to the discussion: Create
subscriptionGroup through the command line and set the maximum number of
retries for retryMaxTimes, which does not take effect：RocketMQ4.9.4
@aaron-ai What do you think? And is maxReconsumeTimes in the grpc client using
the
GitHub user ShadowySpirits added a comment to the discussion: Create
subscriptionGroup through the command line and set the maximum number of
retries for retryMaxTimes, which does not take effect：RocketMQ4.9.4
According to the java doc of `DefaultMQPushConsumer#maxReconsumeTimes`,
GitHub user xdkxlk added a comment to the discussion: Optimize how
MQClientAPIExt is obtained in the MQClientAPIFactory
> Its advantage is that when there are many clients, the traffic can be
> guaranteed to be balanced. @xdkxlk What do you think?
I think using random should be enough. The
GitHub user onejimmyboy added a comment to the discussion: Create
subscriptionGroup through the command line and set the maximum number of
retries for retryMaxTimes, which does not take effect：RocketMQ4.9.4
GitHub user ShadowySpirits added a comment to the discussion: Create
subscriptionGroup through the command line and set the maximum number of
retries for retryMaxTimes, which does not take effect：RocketMQ4.9.4
The option `r` was added in UpdateSubGroupSubCommand since a very early
version,
GitHub user onejimmyboy added a comment to the discussion: Create
subscriptionGroup through the command line and set the maximum number of
retries for retryMaxTimes, which does not take effect：RocketMQ4.9.4
用户在消费的时候，如果设置了这个maxReconsumeTimes
GitHub user ShadowySpirits added a comment to the discussion: Create
subscriptionGroup through the command line and set the maximum number of
retries for retryMaxTimes, which does not take effect：RocketMQ4.9.4
maxReconsumeTimesœ specified by the client takes precedence.
GitHub user onejimmyboy added a comment to the discussion:
RocketMQ4.9升级到rocketmq5.0后，线上业务怎么平滑升级啊，有方案吗？
> @onejimmyboy 升级到rocketmq5.0后如果你还是想用以前4.x的方式还是和之前的一样，但是如你想要用[RocketMQ
> Clients](https://github.com/apache/rocketmq-clients): gRPC/protobuf-based
> RocketMQ clients. 就需要部署proxy. RocketMQ
GitHub user mxsm edited a comment on the discussion:
RocketMQ4.9升级到rocketmq5.0后，线上业务怎么平滑升级啊，有方案吗？
@onejimmyboy 升级到rocketmq5.0后如果你还是想用以前4.x的方式还是和之前的一样，但是如你想要用[RocketMQ
Clients](https://github.com/apache/rocketmq-clients): gRPC/protobuf-based
RocketMQ clients. 就需要部署proxy. RocketMQ
GitHub user mxsm edited a comment on the discussion:
RocketMQ4.9升级到rocketmq5.0后，线上业务怎么平滑升级啊，有方案吗？
@onejimmyboy 升级到rocketmq5.0后如果你还是想用以前4.x的方式还是和之前的一样，但是如你想要用[RocketMQ
Clients](https://github.com/apache/rocketmq-clients): gRPC/protobuf-based
RocketMQ clients. 就需要部署proxy. RocketMQ
GitHub user mxsm added a comment to the discussion:
RocketMQ4.9升级到rocketmq5.0后，线上业务怎么平滑升级啊，有方案吗？
@onejimmyboy 升级到rocketmq5.0后如果你还是想用以前4.x的方式还是和之前的一样，但是如你想要用[RocketMQ
Clients](https://github.com/apache/rocketmq-clients): gRPC/protobuf-based
RocketMQ clients. 就需要部署proxy. RocketMQ
GitHub user socutes added a comment to the discussion: Optimize how
MQClientAPIExt is obtained in the MQClientAPIFactory
Its advantage is that when there are many clients, the traffic can be
guaranteed to be balanced. @xdkxlk What do you think?
GitHub link:
GitHub user RongtongJin added a comment to the discussion: POP消费的性能
压测是否开启了enablePopBufferMerge ，开启该参数可以使得broker中Buffer Merge的策略生效，ck和ack尽量在内存中抵消。
理论上，相同consumer数量下，POP性能可能要略低于PULL，POP消费链路更加复杂，内存中无法merge还会走落盘的消息链路。Pull只是单纯的拉队列中的消息而已。但POP负载均衡是消息粒度而非队列粒度，POP消费其实可以无限扩展消费端增加消费能力。
GitHub link:
GitHub user drpmma added a comment to the discussion:
RocketMQ4.9升级到rocketmq5.0后，线上业务怎么平滑升级啊，有方案吗？
是的，该repo的客户端基于gRPC协议实现，因此要链接proxy；同时proxy也分为local模式和cluster模式，可以认为local模式是原先broker
namesrv架构的升级版。
GitHub link:
https://github.com/apache/rocketmq/discussions/6325#discussioncomment-5328804
GitHub user weihubeats added a comment to the discussion: 自动主从切换部署不能选出master
应该是我本地又起来一个broker，然后本地下线，服务器上的两个broker由于落后于本地broker，所以他们都当选不了主
GitHub link:
https://github.com/apache/rocketmq/discussions/6354#discussioncomment-5328584
This is an automatically sent email for
GitHub user Stevenzall edited a comment on the discussion: POP消费的性能
我目前想到的影响的点有：
1. 共享队列，涉及到加解锁
2. 服务端ACK，网络延迟增加了耗时链路
社区有POP和Pull的性能压测结果分享？
GitHub link:
https://github.com/apache/rocketmq/discussions/6360#discussioncomment-5328572
This is an automatically sent email for
GitHub user weihubeats added a comment to the discussion: 自动主从切换部署不能选出master
好的，非常感觉，我好像明白了，因为为了查看原因又在本地启了一个broker，导致本地的broker的数据文件是最新的，所以服务器上的两个broker都当不了master
GitHub link:
https://github.com/apache/rocketmq/discussions/6354#discussioncomment-5328573
This is an automatically sent
GitHub user Stevenzall added a comment to the discussion: POP消费的性能
我目前想到的影响的点有：
1. 共享队列，涉及到加解锁
2. 服务端ACK，网络延迟增加了耗时链路
GitHub link:
https://github.com/apache/rocketmq/discussions/6360#discussioncomment-5328572
This is an automatically sent email for dev@rocketmq.apache.org.
To
GitHub user weihubeats added a comment to the discussion: 自动主从切换部署不能选出master
没有使用wsl和容器部署，所以机器ip应该是不会变的
GitHub link:
https://github.com/apache/rocketmq/discussions/6354#discussioncomment-5328555
This is an automatically sent email for dev@rocketmq.apache.org.
To unsubscribe, please send
GitHub user RongtongJin edited a comment on the discussion: 自动主从切换部署不能选出master
@weihubeats
GitHub user RongtongJin edited a comment on the discussion: 自动主从切换部署不能选出master
@weihubeats
GitHub user RongtongJin edited a comment on the discussion: 自动主从切换部署不能选出master
@weihubeats
从你图中可以看到，当前SyncStateSet中只有一个同步副本（InSyncReplica为同步副本，NotInSyncReplica为非同步副本），因此该情况下为了保证不丢消息，只有等InSyncReplica的副本上线，才会被选为Master（除非unclean选举）。就像@TheR1sing3un所说，是否由于ip变化导致上线的两个broker均非InSyncReplica，导致无法选主，如果
GitHub user RongtongJin edited a comment on the discussion: 自动主从切换部署不能选出master
@weihubeats
从你图中可以看到，当前SyncStateSet中只有一个同步副本（InSyncReplica为同步副本，NotInSyncReplica为非同步副本），因此该情况下为了保证不丢消息，只有等InSyncReplica的副本上线，才会被选为Master（除非unclean选举）。就像@TheR1sing3un所说，是否由于ip变化导致上线的两个broker均非InSyncReplica，导致无法选主，如果
GitHub user RongtongJin edited a comment on the discussion: 自动主从切换部署不能选出master
@weihubeats
从你图中可以看到，当前SyncStateSet中只有一个同步副本（InSyncReplica为同步副本，NotInSyncReplica为非同步副本），因此该情况下为了保证不丢消息，只有等InSyncReplica的副本上线，才会被选为Master（除非unclean选举）。就像@TheR1sing3un所说，是否由于ip变化导致上线的两个broker均非InSyncReplica，导致无法选主。
GitHub user RongtongJin edited a comment on the discussion: 自动主从切换部署不能选出master
@weihubeats
当前SyncStateSet中只有一个同步副本（InSyncReplica为同步副本，NotInSyncReplica为非同步副本），因此该情况下为了保证不丢消息，只有等InSyncReplica的副本上线，才会被选为Master（除非unclean选举）。就像@TheR1sing3un所说，是否由于ip变化导致上线的两个broker均非InSyncReplica，导致无法选主。
GitHub user RongtongJin added a comment to the discussion: 自动主从切换部署不能选出master
@weihubeats
当前SyncStateSet中只有一个同步副本（InSyncReplica为同步副本，NotInSyncReplica为非同步副本），因此该情况下为了保证不丢消息，只有等InSyncReplica的副本上线，才会被选为Master（除非unclean选举）。就像@TheR1sing3un所说，是否由于ip变化导致上线的两个broker均非InSyncReplica，导致无法选主。
GitHub user TheR1sing3un added a comment to the discussion: 自动主从切换部署不能选出master
是否在重启的过程中发生ip的变化(用wsl或者容器部署会发生变化，可参考https://github.com/apache/rocketmq/issues/5745)
，因为我看这个副本组中syncStateSet中只有一个broker
GitHub user TheR1sing3un deleted a comment on the discussion: 自动主从切换部署不能选出master
> 添加参数 enableElectUncleanMaster =
> true,可以选出新的master节点。但是不明白为什么就这两个节点什么都没干回出现两个节点选不出master的情况
是否在重启的过程中发生ip的变化(用wsl或者容器部署会发生变化，可参考https://github.com/apache/rocketmq/issues/5745)
GitHub user TheR1sing3un added a comment to the discussion: 自动主从切换部署不能选出master
> 添加参数 enableElectUncleanMaster =
> true,可以选出新的master节点。但是不明白为什么就这两个节点什么都没干回出现两个节点选不出master的情况
是否在重启的过程中发生ip的变化(用wsl或者容器部署会发生变化，可参考https://github.com/apache/rocketmq/issues/5745)
，因为我看这个副本组中syncStateSet中只有一个broker
GitHub user weihubeats added a comment to the discussion: 自动主从切换部署不能选出master
添加参数 enableElectUncleanMaster =
true,可以选出新的master节点。但是不明白为什么就这两个节点什么都没干回出现两个节点选不出master的情况
GitHub link:
https://github.com/apache/rocketmq/discussions/6354#discussioncomment-5320281
This is an automatically
GitHub user weihubeats edited a discussion: 自动主从切换部署不能选出master
- rocketmq版本: 5.1.0
- nameserve: 2个节点
- broker: 2个节点
重启broker、nameserve依旧报这个错
执行
```shell
sh bin/mqadmin
GitHub user weihubeats edited a discussion: 自动主从切换部署不能选出master
- rocketmq版本: 5.1.0
nameserve: 2个节点
broker: 2个节点
执行
```shell
sh bin/mqadmin getBrokerEpoch -n localhost:9876 -b
GitHub user weihubeats edited a discussion: 自动主从切换部署不能选出master
nameserve: 2个节点
broker: 2个节点
执行
```shell
sh bin/mqadmin getBrokerEpoch -n localhost:9876 -b broker-a
```
没反应
错误log
GitHub user weihubeats edited a discussion: 自动主从切换部署不能选出master
nameserve: 2个节点
broker: 2个节点
错误log
```java
2023-03-15 16:59:04 INFO ReplicasManager_ScheduledService_1 - Update
GitHub user ShadowySpirits edited a comment on the discussion: Inquiry about
enriching 5.0 Proxy features
> It seems very necessary. Is it already being done?
I notice someone has added GET_CONSUMER_CONNECTION_LIST request code support
for proxy in #6296.
GitHub link:
GitHub user echooymxq added a comment to the discussion: Optimize how
MQClientAPIExt is obtained in the MQClientAPIFactory
用轮询应该需要一个并发计数器了，性能并不一定好.
GitHub link:
https://github.com/apache/rocketmq/discussions/6330#discussioncomment-5293398
This is an automatically sent email for
GitHub user socutes edited a discussion: Optimize how MQClientAPIExt is
obtained in the MQClientAPIFactory
To discuss whether this problem needs to be optimized:
The getClient method in the current MQClientAPIFactory. The MQClientAPIExt is
obtained by random seeds.In extreme cases, load
GitHub user onejimmyboy added a comment to the discussion:
RocketMQ4.9升级到rocketmq5.0后，线上业务怎么平滑升级啊，有方案吗？
你指的是用这个clients连接的时候需要连接proxy？https://github.com/apache/rocketmq-clients
GitHub link:
https://github.com/apache/rocketmq/discussions/6325#discussioncomment-5287362
This is an
GitHub user FantasyChen-DH added a comment to the discussion:
关于RemotingClient异步请求后钩子函数的执行问题
OK I would like to fix it
GitHub link:
https://github.com/apache/rocketmq/discussions/6323#discussioncomment-5286660
This is an automatically sent email for dev@rocketmq.apache.org.
To
GitHub user aaron-ai added a comment to the discussion:
关于RemotingClient异步请求后钩子函数的执行问题
@FantasyChen-DH I think it is a bug rather than a feature, the execution of
hook should not depend on the sync/async way of the invocation. It will be
great if you could fix it.
GitHub link:
GitHub user zhouxinyu added a comment to the discussion:
RocketMQ4.9升级到rocketmq5.0后，线上业务怎么平滑升级啊，有方案吗？
Proxy模块是可选的。不过使用5.0 gRPC协议SDK的话需要连接Proxy。
GitHub link:
https://github.com/apache/rocketmq/discussions/6325#discussioncomment-5286554
This is an automatically sent email for
GitHub user FantasyChen-DH added a comment to the discussion:
关于RemotingClient异步请求后钩子函数的执行问题
看样子是的 但是并没有回应 是异步请求不需要做钩子函数的After操作吗
GitHub link:
https://github.com/apache/rocketmq/discussions/6323#discussioncomment-5281962
This is an automatically sent email for dev@rocketmq.apache.org.
GitHub user echooymxq added a comment to the discussion:
关于RemotingClient异步请求后钩子函数的执行问题
这里好像有一个相关issue https://github.com/apache/rocketmq/issues/1709, /cc @aaron-ai
GitHub link:
https://github.com/apache/rocketmq/discussions/6323#discussioncomment-5280823
This is an automatically sent
GitHub user yuluo-yx added a comment to the discussion: Windows环境运行SDK收发示例失败
> > > 你应该查看客户端日志而不是服务端日志
> >
> >
> > 客户端日志路径是那儿？
>
> 请查看相关文档，对于 Java gRPC 客户端可以默认在 `$HOME/logs/rocketmq`，详见文档 [Logging
> System](https://github.com/apache/rocketmq-clients/tree/master/java#logging-system)
> 一节
GitHub user yuluo-yx added a comment to the discussion: Windows环境运行SDK收发示例失败
> > > 你应该查看客户端日志而不是服务端日志
> >
> >
> > 客户端日志路径是那儿？
>
> 请查看相关文档，对于 Java gRPC 客户端可以默认在 `$HOME/logs/rocketmq`，详见文档 [Logging
> System](https://github.com/apache/rocketmq-clients/tree/master/java#logging-system)
> 一节
GitHub user ShadowySpirits added a comment to the discussion: Inquiry about
enriching 5.0 Proxy features
> It seems very necessary. Is it already being done?
I notice someone has added GET_CONSUMER_CONNECTION_LIST request code support
for proxy in #6269.
GitHub link:
GitHub user ShadowySpirits added a comment to the discussion:
Windows环境运行SDK收发示例失败
> > 你应该查看客户端日志而不是服务端日志
>
> 客户端日志路径是那儿？
请查看相关文档，对于 Java gRPC 客户端可以默认在 `$HOME/logs/rocketmq`，详见文档 [Logging
System](https://github.com/apache/rocketmq-clients/tree/master/java#logging-system)
一节
GitHub link:
GitHub user yehaifeng deleted a comment on the discussion: Question about
"Initial consumer offset"
`ComsumerOffset` maybe is the other select.
GitHub link:
https://github.com/apache/rocketmq/discussions/6309#discussioncomment-5278949
This is an automatically sent email for
GitHub user yehaifeng added a comment to the discussion: Question about
"Initial consumer offset"
`ComsumerOffset` maybe is the other select.
GitHub link:
https://github.com/apache/rocketmq/discussions/6309#discussioncomment-5278949
This is an automatically sent email for
GitHub user RongtongJin added a comment to the discussion: What is the `flag`
field in `Message` use for?
This is a reserved field, which can complete some extensibility design
GitHub link:
https://github.com/apache/rocketmq/discussions/6298#discussioncomment-5275711
This is an
GitHub user yuluo-yx added a comment to the discussion: Windows环境运行SDK收发示例失败
> 你应该查看客户端日志而不是服务端日志
客户端日志路径是那儿？
GitHub link:
https://github.com/apache/rocketmq/discussions/6305#discussioncomment-5274711
This is an automatically sent email for dev@rocketmq.apache.org.
To unsubscribe,
GitHub user ShadowySpirits added a comment to the discussion:
Windows环境运行SDK收发示例失败
你应该查看客户端日志而不是服务端日志
GitHub link:
https://github.com/apache/rocketmq/discussions/6305#discussioncomment-5273588
This is an automatically sent email for dev@rocketmq.apache.org.
To unsubscribe, please send
GitHub user yuluo-yx added a comment to the discussion: Windows环境运行SDK收发示例失败
> 怎么个失败法？
>
> > 如图所示，控制台并没有任何输出。
>
> 没有输出不表示失败，断点调试一下？
断点捕捉不到，并没有什么异常出现
GitHub link:
https://github.com/apache/rocketmq/discussions/6305#discussioncomment-5267174
This is an automatically sent email for
GitHub user echooymxq edited a comment on the discussion: Is rocketmq
considering supporting HTTP Restful protocols?
In fact, i recently need to implement the HTTP protocol on the proxy. But just
to be able more simply use the aliyun http sdk to connect rocketmq.
GitHub link:
GitHub user echooymxq added a comment to the discussion: Is rocketmq
considering supporting HTTP Restful protocols?
In fact, i recently need to implement the HTTP protocol on the proxy. But just
to be able to more simply use the aliyun http sdk to connect rocketmq.
GitHub link:
GitHub user echooymxq edited a comment on the discussion: Windows环境运行SDK收发示例失败
怎么个失败法？
> 如图所示，控制台并没有任何输出。
没有输出不表示失败，断点调试一下？
GitHub link:
https://github.com/apache/rocketmq/discussions/6305#discussioncomment-5266212
This is an automatically sent email for dev@rocketmq.apache.org.
To
GitHub user echooymxq added a comment to the discussion: Windows环境运行SDK收发示例失败
怎么个失败法？
> 如图所示，控制台并没有任何输出。
没有输出不表示失败，断点调试一下？
GitHub link:
https://github.com/apache/rocketmq/discussions/6305#discussioncomment-5266212
This is an automatically sent email for dev@rocketmq.apache.org.
To
GitHub user yuluo-yx added a comment to the discussion: Windows环境运行SDK收发示例失败
> 详见路径 ~/logs/rocketmqlogs/ 看看有没有相关信息，没有信息也很难帮助你
日志里面好像也没有报什么异常堆栈信息
GitHub link:
https://github.com/apache/rocketmq/discussions/6305#discussioncomment-5266055
This is an automatically sent email for
GitHub user yuluo-yx added a comment to the discussion: Windows环境运行SDK收发示例失败
> > 可以查看下客户端日志，看是否有更多信息
>
> 并没有任何提示，idea控制台也没有任何信息
namesrv.log
```
2023-03-10 12:21:44 WARN NettyServerCodecThread_1 - NETTY SERVER PIPELINE: IDLE
exception [172.25.16.1:54391]
2023-03-10 12:21:44 WARN
GitHub user aaron-ai edited a comment on 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
101 - 200 of 43000 matches
Mail list logo
