I'd like to do together to Integrate rocketMQ with Spring as GSoC mentee and partner.

2023-03-28 Thread 임승 
Dear Apache RocketMQ Team,


My name is Theo Lim and I am a backend developer in Korea.

I am writing to express my interest in the movement to integrate with
spring and participating in the GSOC Open Source Program.


As a developer, I have been working with Spring 5 to develop backend
systems for various projects for 2 years. I am also experienced in using
Kafka and Messaging Queue to facilitate communication between different
components of the system.


In the past, I have contributed to the OpenStack open source project and
gained valuable experience in working with a community of developers to
achieve a common goal.


In my current role, I use Spring extensively to integrate various
components of the system, and I am passionate about exploring new
possibilities with this technology. I believe that participating in the
GSOC program will not only give me the opportunity to contribute to an open
source project but also help me develop new skills and gain more experience
in the field.


I am particularly interested in projects related to Spring, and Messaging
Queue, especially RocketMQ that is a new gen tool with powerful
efficiency. I am open to exploring other areas as well. I am a dedicated
and hardworking developer, and I am confident that I can make a valuable
contribution to any project that I am assigned to.

Thank you for considering my application, and I look forward to hearing
from you soon.


From. Theo Lim

[GitHub] [rocketmq] socutes edited a discussion: proxy module monitoring indicators are improved

2023-03-28 Thread GitBox 


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

It is recommended to add the following indicators:
1. 【Node/Topic】Number of messages produced/consumed
2.  【Node/Topic】Production/consumption message size /
3.  【Node/Topic】Time spent on each interface request
4.  【Node/Topic】Statistics on error codes of each interface
5.  【Node】The number of calls to each interface
6. 【Node】TCP(GRPC/Remoting) connection count statistics
7. 【Node】Thread pool monitoring (total capacity, used capacity, free capacity 
of each thread pool) monitoring
8. 【Node】Process status: indicates that the current process is started or 
stopped

The following table describes the labels of the metrics that are related to the 
Message Queue for Apache RocketMQ Proxy.
cluster: RocketMQ cluster name.
node_type: the type of service node, whitch includes the 
following:proxy,broker,nameserver.
node_id:the ID of the service node.
topic: the topic of RocketMQ.
thread_type: The use of thread pools. eg: sendMessage、pullMessage
protocol_type: Type of protocol. eg: grpc, remoting
proxy_mode: cluster mode. eg: local, cluster

Indicators of node dimension:
Type | Name | Unit | Description | Label
-- | -- | -- | -- | --
counter | rocketmq_messages_in_total | count | The number of messages that are 
produced. | cluster,node_type,node_id,topic, protocol_type,proxy_mode
counter | rocketmq_messages_out_total | count | The number of messages that are 
consumed. | cluster,node_type,node_id,topic, protocol_type,proxy_mode
counter | rocketmq_throughput_in_total | byte | The write throughput that are 
produced. | cluster,node_type,node_id,topic, protocol_type,proxy_mode
counter | rocketmq_throughput_out_total | byte | The read throughput that are 
produced. | cluster,node_type,node_id,topic, protocol_type,proxy_mode
histogram | rocketmq_message_size | byte | The distribution of message sizes. 
This metric is counted only when messages are sent. The following shows the 
distribution ranges:le_1_kb: ≤ 1 KBle_4_kb: ≤ 4 KBle_512_kb: ≤ 512 KBle_1_mb: ≤ 
1 MBle_2_mb: ≤ 2 MBle_4_mb: ≤ 4 MBle_overflow: > 4 MB | 
cluster,node_type,node_id,topic, protocol_type,proxy_mode
histogram | rocketmq_rpc_latency | millisecond | The rpc call 
latency.ranges:le_1_msle_5_msle_10_msle_100_msle_1_msle_6_msle_overflow 
| cluster,node_typ,node_id, request_code, response_code,proxy_mode
counter | rocketmq_producer_connections | count | Number of connections for the 
producer | cluster,node_typ,node_id,proxy_mode
counter | rocketmq_consumer_connections | count | The number of consumer 
connections | cluster,node_typ,node_id,proxy_mode
guage | rocketmq_processor_watermark | count | High watermark information for 
the thread| cluster,node_typ,node_id,thread_type,proxy_mode
gauge | rocketmq_proxy_up | value | Process running status | 
cluster,node_typ,node_id,proxy_mode























GitHub link: https://github.com/apache/rocketmq/discussions/6405


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: proxy module monitoring indicators are improved

2023-03-28 Thread GitBox 


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

It is recommended to add the following indicators:
1. 【Node/Topic】Number of messages produced/consumed
2.  【Node/Topic】Production/consumption message size /
3.  【Node/Topic】Time spent on each interface request
4.  【Node/Topic】Statistics on error codes of each interface
5.  【Node】The number of calls to each interface
6. 【Node】TCP(GRPC/Remoting) connection count statistics
7. 【Node】Thread pool monitoring (total capacity, used capacity, free capacity 
of each thread pool) monitoring
8. 【Node】Process status: indicates that the current process is started or 
stopped

The following table describes the labels of the metrics that are related to the 
Message Queue for Apache RocketMQ Proxy.
cluster: RocketMQ cluster name.
node_type: the type of service node, whitch includes the 
following:proxy,broker,nameserver.
node_id:the ID of the service node.
topic: the topic of RocketMQ.
thread_type: The use of thread pools. eg: sendMessage、pullMessage
protocol_type: Type of protocol. eg: grpc, remoting
proxy_mode: cluster mode. eg: local, cluster

Indicators of node dimension:
Type | Name | Unit | Description | Label
-- | -- | -- | -- | --
counter | rocketmq_messages_in_total | count | The number of messages that are 
produced. | cluster,node_type,node_id,topic, protocol_type,proxy_mode
counter | rocketmq_messages_out_total | count | The number of messages that are 
consumed. | cluster,node_type,node_id,topic, protocol_type,proxy_mode
counter | rocketmq_throughput_in_total | byte | The write throughput that are 
produced. | cluster,node_type,node_id,topic, protocol_type,proxy_mode
counter | rocketmq_throughput_out_total | byte | The read throughput that are 
produced. | cluster,node_type,node_id,topic, protocol_type,proxy_mode
histogram | rocketmq_message_size | byte | The distribution of message sizes. 
This metric is counted only when messages are sent. The following shows the 
distribution ranges:le_1_kb: ≤ 1 KBle_4_kb: ≤ 4 KBle_512_kb: ≤ 512 KBle_1_mb: ≤ 
1 MBle_2_mb: ≤ 2 MBle_4_mb: ≤ 4 MBle_overflow: > 4 MB | 
cluster,node_type,node_id,topic, protocol_type,proxy_mode
histogram | rocketmq_rpc_latency | millisecond | The rpc call 
latency.ranges:le_1_msle_5_msle_10_msle_100_msle_1_msle_6_msle_overflow 
| cluster,node_typ,node_id, request_code,request_code, response_code,proxy_mode
counter | rocketmq_producer_connections | count | Number of connections for the 
producer | cluster,node_typ,node_id,proxy_mode
counter | rocketmq_consumer_connections | count | The number of consumer 
connections | cluster,node_typ,node_id,proxy_mode
guage | rocketmq_processor_watermark | count | High watermark information for 
the thread| cluster,node_typ,node_id,thread_type,proxy_mode
gauge | rocketmq_proxy_up | value | Process running status | 
cluster,node_typ,node_id,proxy_mode























GitHub link: https://github.com/apache/rocketmq/discussions/6405


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: proxy module monitoring indicators are improved

2023-03-28 Thread GitBox 


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

It is recommended to add the following indicators:
1. 【Node/Topic】Number of messages produced/consumed
2.  【Node/Topic】Production/consumption message size /
3.  【Node/Topic】Time spent on each interface request
4.  【Node/Topic】Statistics on error codes of each interface
5.  【Node】The number of calls to each interface
6. 【Node】TCP(GRPC/Remoting) connection count statistics
7. 【Node】Thread pool monitoring (total capacity, used capacity, free capacity 
of each thread pool) monitoring
8. 【Node】Process status: indicates that the current process is started or 
stopped

The following table describes the labels of the metrics that are related to the 
Message Queue for Apache RocketMQ Proxy.
cluster: RocketMQ cluster name.
node_type: the type of service node, whitch includes the 
following:proxy,broker,nameserver.
node_id:the ID of the service node.
topic: the topic of RocketMQ.
thread_type: The use of thread pools. eg: sendMessage、pullMessage
protocol_type: Type of protocol. eg: grpc, remoting
proxy_mode: cluster mode. eg: local, cluster

Indicators of node dimension:
Type | Name | Unit | Description | Label
-- | -- | -- | -- | --
counter | rocketmq_messages_in_total | count | The number of messages that are 
produced. | cluster,node_type,node_id,topic, protocol_type,proxy_mode
counter | rocketmq_messages_out_total | count | The number of messages that are 
consumed. | cluster,node_type,node_id,topic, protocol_type,proxy_mode
counter | rocketmq_throughput_in_total | byte | The write throughput that are 
produced. | cluster,node_type,node_id,topic, protocol_type,proxy_mode
counter | rocketmq_throughput_out_total | byte | The read throughput that are 
produced. | cluster,node_type,node_id,topic, protocol_type,proxy_mode
histogram | rocketmq_message_size | byte | The distribution of message sizes. 
This metric is counted only when messages are sent. The following shows the 
distribution ranges:le_1_kb: ≤ 1 KBle_4_kb: ≤ 4 KBle_512_kb: ≤ 512 KBle_1_mb: ≤ 
1 MBle_2_mb: ≤ 2 MBle_4_mb: ≤ 4 MBle_overflow: > 4 MB | 
cluster,node_type,node_id,topic, protocol_type,proxy_mode
histogram | rocketmq_rpc_latency | millisecond | The rpc call 
latency.ranges:le_1_msle_5_msle_10_msle_100_msle_1_msle_6_msle_overflow
| cluster,node_typ,node_id, request_code,request_code, response_code,proxy_mode
counter | rocketmq_producer_connections | count | Number of connections for the 
producer | cluster,node_typ,node_id,proxy_mode
counter | rocketmq_consumer_connections | count | The number of consumer 
connections | cluster,node_typ,node_id,proxy_mode
guage | rocketmq_processor_watermark | count | High watermark information for 
the thread| cluster,node_typ,node_id,thread_type,proxy_mode
gauge | rocketmq_proxy_up | value | Process running status | 
cluster,node_typ,node_id,proxy_mode























GitHub link: https://github.com/apache/rocketmq/discussions/6405


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: proxy module monitoring indicators are improved

2023-03-28 Thread GitBox 


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

It is recommended to add the following indicators:
1. 【Node/Topic】Number of messages produced/consumed
2.  【Node/Topic】Production/consumption message size /
3.  【Node/Topic】Time spent on each interface request
4.  【Node/Topic】Statistics on error codes of each interface
5.  【Node】The number of calls to each interface
6. 【Node】TCP(GRPC/Remoting) connection count statistics
7. 【Node】Thread pool monitoring (total capacity, used capacity, free capacity 
of each thread pool) monitoring
8. 【Node】Process status: indicates that the current process is started or 
stopped

The following table describes the labels of the metrics that are related to the 
Message Queue for Apache RocketMQ Proxy.
cluster: RocketMQ cluster name.
node_type: the type of service node, whitch includes the 
following:proxy,broker,nameserver.
node_id:the ID of the service node.
topic: the topic of RocketMQ.
thread_type: The use of thread pools. eg: sendMessage、pullMessage
protocol_type: Type of protocol. eg: grpc, remoting

Indicators of node dimension:
Type | Name | Unit | Description | Label
-- | -- | -- | -- | --
counter | rocketmq_messages_in_total | count | The number of messages that are 
produced. | cluster,node_type,node_id,topic, protocol_type
counter | rocketmq_messages_out_total | count | The number of messages that are 
consumed. | cluster,node_type,node_id,topic, protocol_type
counter | rocketmq_throughput_in_total | byte | The write throughput that are 
produced. | cluster,node_type,node_id,topic, protocol_type
counter | rocketmq_throughput_out_total | byte | The read throughput that are 
produced. | cluster,node_type,node_id,topic, protocol_type
histogram | rocketmq_message_size | byte | The distribution of message sizes. 
This metric is counted only when messages are sent. The following shows the 
distribution ranges:le_1_kb: ≤ 1 KBle_4_kb: ≤ 4 KBle_512_kb: ≤ 512 KBle_1_mb: ≤ 
1 MBle_2_mb: ≤ 2 MBle_4_mb: ≤ 4 MBle_overflow: > 4 MB | 
cluster,node_type,node_id,topic, protocol_type
histogram | rocketmq_rpc_latency | millisecond | The rpc call 
latency.ranges:le_1_msle_5_msle_10_msle_100_msle_1_msle_6_msle_overflow
| cluster,node_typ,node_id, request_code,request_code, response_code
counter | rocketmq_producer_connections | count | Number of connections for the 
producer | cluster,node_typ,node_id
counter | rocketmq_consumer_connections | count | The number of consumer 
connections | cluster,node_typ,node_id
guage | rocketmq_processor_watermark | count | High watermark information for 
the thread| cluster,node_typ,node_id,thread_type
gauge | rocketmq_proxy_up | value | Process running status | 
cluster,node_typ,node_id























GitHub link: https://github.com/apache/rocketmq/discussions/6405


This is an automatically sent email for dev@rocketmq.apache.org.
To unsubscribe, please send an email to: dev-unsubscr...@rocketmq.apache.org

[RESULT] [VOTE] Release gRPC Java Client for Apache RocketMQ 5.0.5 RC1

2023-03-28 Thread aaron ai 
Hello RocketMQ Community,

The Apache RocketMQ vote is now closed and has passed with 4 binding +1s, 1
non-binding +1s and no 0 or -1;

Binding votes +1s:

lollipop(lolli...@apache.org)
fuyou(fu...@apache.org)
jinrongtong(jinrongt...@apache.org)
Xinyu Zhou(yu...@apache.org)

The release will be published soon.

Thanks,
The Apache RocketMQ Team

Xinyu Zhou  于2023年3月27日周一 16:22写道：

> +1
>
> On Mon, Mar 27, 2023 at 4:12 PM jinrongtong 
> wrote:
>
> > +1， I checked [OK]  maven jar in nexus repo is right [OK] Hash
> > and Tag in GitHub repo is matching the current artifacts
> > At 2023-03-27 15:44:25, "fuyou"  wrote:
> > >+1
> > >
> > >aaron ai  于2023年3月27日周一 15:43写道：
> > >
> > >>
> > >>
> > >> -- Forwarded message -
> > >> 发件人： lollipop 
> > >> Date: 2023年3月22日周三 19:34
> > >> Subject: Re: [VOTE] Release gRPC Java Client for Apache RocketMQ 5.0.5
> > RC1
> > >> To: 
> > >>
> > >>
> > >> +1
> > >> I have checked all of the four items.
> > >>
> > >> On Wed, Mar 22, 2023 at 10:00 AM aaron ai  wrote:
> > >>
> > >> > Hello RocketMQ Community,
> > >> >
> > >> > This is the vote for 5.0.5 RC1 of Apache RocketMQ client for Java.
> > >> >
> > >> > Apache RocketMQ clients 5.x series follow the specs of rocketmq-apis
> > >> > , and are built on top of
> > >> > Protocol
> > >> > Buffer and gRPC.
> > >> >
> > >> > The artifact url:
> > >> >
> > >> >
> > >>
> >
> https://dist.apache.org/repos/dist/dev/rocketmq/rocketmq-clients/rocketmq-client-java/5.0.5-rc1/
> > >> >
> > >> > The staging repo for maven:
> > >> >
> > >>
> >
> https://repository.apache.org/content/repositories/orgapacherocketmq-1156/
> > >> >
> > >> > Git tag for the release:
> > >> > https://github.com/apache/rocketmq-clients/releases/tag/java-5.0.5
> > >> >
> > >> > Hash for the release tag:
> > >> > 997d322e71a5f6d8bc189b88eea6caad211105f8
> > >> >
> > >> > Release Notes:
> > >> > https://github.com/apache/rocketmq-clients/releases/tag/java-5.0.5
> > >> >
> > >> > The artifact have been signed with
> > >> > Key: 3A11FEBBD64C807A233BF1F27C46C79BD4D29011, which can be found in
> > the
> > >> > keys file: https://dist.apache.org/repos/dist/dev/rocketmq/KEYS
> > >> >
> > >> > Fill in the following:
> > >> >
> > >> > [+]  check LICENSE, should be Apache V2
> > >> > [+]  check NOTICE, should have a notice for third-party dependency
> if
> > >> > necessary
> > >> > [+]  extract the zip and check if the source version is correct
> > >> > [+]  verify the asc(PGP sign),SHA512
> > >> >
> > >> > The vote will be open for at least 72 hours or until the necessary
> > number
> > >> > of votes are reached.
> > >> > Please vote accordingly:
> > >> >
> > >> > [ ] +1 approve
> > >> > [ ] +0 no opinion
> > >> > [ ] -1 disapprove with the reason
> > >> >
> > >> > Thanks
> > >> > The Apache RocketMQ Team
> > >> >
> > >>
> > >
> > >
> > >--
> > >   =
> > >
> > >  fuyou001
> > >Best Regards
> >
>

[GitHub] [rocketmq-client-python] duament opened a new issue, #134: Thread "ConsumeTP" Segmentation fault at ffi_closure_unix64_inner

2023-03-28 Thread via GitHub 


duament opened a new issue, #134:
URL: https://github.com/apache/rocketmq-client-python/issues/134

   I'm using rocketmq-client-python in a django project and have a Segmentation 
fault issue.
   
   Here's my `apps.py`,where a ready() function is defined to start a consumer.
   ```python
   from django.apps import AppConfig
   
   class AppConfig(AppConfig):
   name = 'app'
   verbose_name = 'app'
   default_auto_field = 'django.db.models.BigAutoField'
   
   def ready(self):
   from rocketmq.client import PushConsumer, ConsumeStatus
   
   def consumer_callback(msg):
   print(555)
   return ConsumeStatus.CONSUME_SUCCESS
   
   consumer = PushConsumer('ocp5-consumer')
   consumer.set_name_server_address('10.0.0.1:9876')
   consumer.subscribe('OCP', consumer_callback)
   consumer.start()
   ```
   
   Then I got a Segmentation fault, the backtrace:
   ```
   Thread 79 "ConsumeTP" received signal SIGSEGV, Segmentation fault.
   [Switching to Thread 0x7ffeb17fa640 (LWP 62181)]
   0x7fffe8386460 in ffi_closure_unix64_inner () from 
/nix/store/m0fsvgc5hrn3yjwsl9fvj5m6pyjk2il2-libffi-3.4.4/lib/libffi.so.8
   (gdb) bt
   #0  0x7fffe8386460 in ffi_closure_unix64_inner () from 
/nix/store/m0fsvgc5hrn3yjwsl9fvj5m6pyjk2il2-libffi-3.4.4/lib/libffi.so.8
   #1  0x7fffe83869e0 in ffi_closure_unix64 () from 
/nix/store/m0fsvgc5hrn3yjwsl9fvj5m6pyjk2il2-libffi-3.4.4/lib/libffi.so.8
   #2  0x7fffe82b58db in 
MessageListenerInner::consumeMessage(std::vector > const&) ()
  from 
/nix/store/cabccf1jbls4619vj7frq6mlad3p70y9-rocketmq-client-cpp-2.2.0/lib/librocketmq.so
   #3  0x7fffe827d75f in 
rocketmq::ConsumeMessageConcurrentlyService::ConsumeRequest(boost::weak_ptr,
 std::vector >&) 
()
  from 
/nix/store/cabccf1jbls4619vj7frq6mlad3p70y9-rocketmq-client-cpp-2.2.0/lib/librocketmq.so
   #4  0x7fffe8280027 in 
boost::asio::detail::completion_handler, std::vector >&>, 
boost::_bi::list3,
 boost::_bi::value >, 
boost::_bi::value > > > > >::do_complete(void*, 
boost::asio::detail::scheduler_operation*, boost::system::error_code const&, 
unsigned long) () from 
/nix/store/cabccf1jbls4619vj7frq6mlad3p70y9-rocketmq-client-cpp-2.2.0/lib/librocketmq.so
   #5  0x7fffe827ec19 in 
boost::asio::detail::scheduler::run(boost::system::error_code&) () from 
/nix/store/cabccf1jbls4619vj7frq6mlad3p70y9-rocketmq-client-cpp-2.2.0/lib/librocketmq.so
   #6  0x7fffe827ee3b in boost::asio::io_context::run() () from 
/nix/store/cabccf1jbls4619vj7frq6mlad3p70y9-rocketmq-client-cpp-2.2.0/lib/librocketmq.so
   #7  0x7fffe802f882 in thread_proxy () from 
/nix/store/vkqkncgi656rs5ad9mvdnpg2fvkn3alf-boost-1.69.0/lib/libboost_thread.so.1.69.0
   #8  0x778f1e86 in start_thread () from 
/nix/store/76l4v99sk83ylfwkz8wmwrm4s8h73rhd-glibc-2.35-224/lib/libc.so.6
   #9  0x77977ee4 in clone () from 
/nix/store/76l4v99sk83ylfwkz8wmwrm4s8h73rhd-glibc-2.35-224/lib/libc.so.6
   ```
   
   (This crash happened on nixos. It is also reproducible on ubuntu 16)


-- 
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] socutes edited a discussion: proxy module monitoring indicators are improved

2023-03-28 Thread GitBox 


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

It is recommended to add the following indicators:
1. 【Node/Topic】Number of messages produced/consumed
2.  【Node/Topic】Production/consumption message size /
3.  【Node/Topic】Time spent on each interface request
4.  【Node/Topic】Statistics on error codes of each interface
5.  【Node】The number of calls to each interface
6. 【Node】TCP(GRPC/Remoting) connection count statistics
7. 【Node】Thread pool monitoring (total capacity, used capacity, free capacity 
of each thread pool) monitoring
8. 【Node】Process status: indicates that the current process is started or 
stopped

The following table describes the labels of the metrics that are related to the 
Message Queue for Apache RocketMQ Proxy.
cluster: RocketMQ cluster name.
node_type: the type of service node, whitch includes the 
following:proxy,broker,nameserver.
node_id:the ID of the service node.
topic: the topic of RocketMQ.
thread_type: The use of thread pools. eg: sendMessage、pullMessage

Indicators of node dimension:
Type | Name | Unit | Description | Label
-- | -- | -- | -- | --
counter | rocketmq_messages_in_total | count | The number of messages that are 
produced. | cluster,node_type,node_id,topic
counter | rocketmq_messages_out_total | count | The number of messages that are 
consumed. | cluster,node_type,node_id,topic
counter | rocketmq_throughput_in_total | byte | The write throughput that are 
produced. | cluster,node_type,node_id,topic
counter | rocketmq_throughput_out_total | byte | The read throughput that are 
produced. | cluster,node_type,node_id,topic
histogram | rocketmq_message_size | byte | The distribution of message sizes. 
This metric is counted only when messages are sent. The following shows the 
distribution ranges:le_1_kb: ≤ 1 KBle_4_kb: ≤ 4 KBle_512_kb: ≤ 512 KBle_1_mb: ≤ 
1 MBle_2_mb: ≤ 2 MBle_4_mb: ≤ 4 MBle_overflow: > 4 MB | 
cluster,node_type,node_id,topic
histogram | rocketmq_rpc_latency | millisecond | The rpc call 
latency.ranges:le_1_msle_5_msle_10_msle_100_msle_1_msle_6_msle_overflow
| cluster,node_typ,node_id, request_code,request_code, response_code
counter | rocketmq_producer_connections | count | Number of connections for the 
producer | cluster,node_typ,node_id
counter | rocketmq_consumer_connections | count | The number of consumer 
connections | cluster,node_typ,node_id
guage | rocketmq_processor_watermark | count | High watermark information for 
the thread| cluster,node_typ,node_id,thread_type
gauge | rocketmq_proxy_up | value | Process running status | 
cluster,node_typ,node_id























GitHub link: https://github.com/apache/rocketmq/discussions/6405


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: proxy module monitoring indicators are improved

2023-03-28 Thread GitBox 


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

It is recommended to add the following indicators:
1. 【Node/Topic】Number of messages produced/consumed
2.  【Node/Topic】Production/consumption message size /
3.  【Node/Topic】Time spent on each interface request
4.  【Node/Topic】Statistics on error codes of each interface
5.  【Node】The number of calls to each interface
6. 【Node】TCP(GRPC/Remoting) connection count statistics
7. 【Node】Thread pool monitoring (total capacity, used capacity, free capacity 
of each thread pool) monitoring
8. 【Node】Process status: indicates that the current process is started or 
stopped

The following table describes the labels of the metrics that are related to the 
Message Queue for Apache RocketMQ Proxy.
cluster: RocketMQ cluster name.
node_type: the type of service node, whitch includes the 
following:proxy,broker,nameserver.
node_id:the ID of the service node.
topic: the topic of RocketMQ.
thread_type: The use of thread pools. eg: sendMessage、pullMessage

Indicators of node dimension:
Type | Name | Unit | Description | Label
-- | -- | -- | -- | --
counter | rocketmq_messages_in_total | count | The number of messages that are 
produced. | cluster,node_type,node_id,topic
counter | rocketmq_messages_out_total | count | The number of messages that are 
consumed. | cluster,node_type,node_id,topic
counter | rocketmq_throughput_in_total | byte | The write throughput that are 
produced. | cluster,node_type,node_id,topic
counter | rocketmq_throughput_out_total | byte | The read throughput that are 
produced. | cluster,node_type,node_id,topic
histogram | rocketmq_message_size | byte | The distribution of message sizes. 
This metric is counted only when messages are sent. The following shows the 
distribution ranges:le_1_kb: ≤ 1 KBle_4_kb: ≤ 4 KBle_512_kb: ≤ 512 KBle_1_mb: ≤ 
1 MBle_2_mb: ≤ 2 MBle_4_mb: ≤ 4 MBle_overflow: > 4 MB | 
cluster,node_type,node_id,topic
histogram | rocketmq_rpc_latency | millisecond | The rpc call latency.ranges:
ranges:
le_1_ms
le_5_ms  
le_10_ms
le_100_ms
le_1_ms
le_6_ms
le_overflow
| cluster,node_typ,node_id, request_code,request_code, response_code
counter | rocketmq_producer_connections | count | Number of connections for the 
producer | cluster,node_typ,node_id
counter | rocketmq_consumer_connections | count | The number of consumer 
connections | cluster,node_typ,node_id
guage | rocketmq_processor_watermark | count | High watermark information for 
the thread| cluster,node_typ,node_id,thread_type
gauge | rocketmq_proxy_up | value | Process running status | 
cluster,node_typ,node_id























GitHub link: https://github.com/apache/rocketmq/discussions/6405


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: proxy module monitoring indicators are improved

2023-03-28 Thread GitBox 


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

It is recommended to add the following indicators:
1. 【Node/Topic】Number of messages produced/consumed
2.  【Node/Topic】Production/consumption message size /
3.  【Node/Topic】Time spent on each interface request
4.  【Node/Topic】Statistics on error codes of each interface
5.  【Node】The number of calls to each interface
6. 【Node】TCP(GRPC/Remoting) connection count statistics
7. 【Node】Thread pool monitoring (total capacity, used capacity, free capacity 
of each thread pool) monitoring
8. 【Node】Process status: indicates that the current process is started or 
stopped

The following table describes the labels of the metrics that are related to the 
Message Queue for Apache RocketMQ Proxy.
cluster: RocketMQ cluster name.
node_type: the type of service node, whitch includes the 
following:proxy,broker,nameserver.
node_id:the ID of the service node.
topic: the topic of RocketMQ.
thread_type: The use of thread pools. eg: sendMessage、pullMessage

Indicators of node dimension:
Type | Name | Unit | Description | Label
-- | -- | -- | -- | --
counter | rocketmq_messages_in_total | count | The number of messages that are 
produced. | cluster,node_type,node_id,topic
counter | rocketmq_messages_out_total | count | The number of messages that are 
consumed. | cluster,node_type,node_id,topic
counter | rocketmq_throughput_in_total | byte | The write throughput that are 
produced. | cluster,node_type,node_id,topic
counter | rocketmq_throughput_out_total | byte | The read throughput that are 
produced. | cluster,node_type,node_id,topic
histogram | rocketmq_message_size | byte | The distribution of message sizes. 
This metric is counted only when messages are sent. The following shows the 
distribution ranges:le_1_kb: ≤ 1 KBle_4_kb: ≤ 4 KBle_512_kb: ≤ 512 KBle_1_mb: ≤ 
1 MBle_2_mb: ≤ 2 MBle_4_mb: ≤ 4 MBle_overflow: > 4 MB | 
cluster,node_type,node_id,topic
histogram | rocketmq_rpc_latency | millisecond | The rpc call 
latency.ranges:le_1_msle_5_msle_10_msle_100_msle_1_msle_6_msle_overflow|
 cluster,node_typ,node_id, request_code,request_code, response_code
counter | rocketmq_producer_connections | count | Number of connections for the 
producer | cluster,node_typ,node_id
counter | rocketmq_consumer_connections | count | The number of consumer 
connections | cluster,node_typ,node_id
guage | rocketmq_processor_watermark | count | High watermark information for 
the thread| cluster,node_typ,node_id,thread_type
gauge | rocketmq_proxy_up | value | Process running status | 
cluster,node_typ,node_id























GitHub link: https://github.com/apache/rocketmq/discussions/6405


This is an automatically sent email for dev@rocketmq.apache.org.
To unsubscribe, please send an email to: dev-unsubscr...@rocketmq.apache.org

Re: [VOTE]Release Apache RocketMQ 4.9.5 RC1

2023-03-28 Thread aaron ai 
+1

奥利弗  于2023年3月28日周二 10:48写道：

> +1
>
> 1. asc, sha512 exists and checked.
> 2. LICENSE and NOTICE exist.
> 3. Build the package from source success.
> 4. Tags are correct.
>
> By the way, validation is easier if the sha512 file is in this format
> 5bfe9cdb4513faeb42a07a36da8c5f62b0d200dd1d636c2647e328dab0fb9b5c94dcdb3343b1ff3b9faf6cf7d69321e1279356c9658678a97c3d43a23616
> rocketmq-all-4.9.5-bin-release.zip
>
> > 2023年3月27日 21:33，fuyou  写道：
> >
> > +1
> >
> > jinrongtong 于2023年3月27日 周一18:51写道：
> >
> >> Hello RocketMQ Community,
> >>
> >> This is the vote for 4.9.5 of Apache RocketMQ.
> >>
> >> This release fixes some bugs and supports bname in protocol for 4.9.5
> >> client accessing proxy.
> >>
> >> The artifacts:
> >> https://dist.apache.org/repos/dist/dev/rocketmq/4.9.5-rc1/
> >>
> >> The staging repo:
> >>
> https://repository.apache.org/content/repositories/orgapacherocketmq-1172
> >>
> >> Git tag for the release:
> >> https://github.com/apache/rocketmq/tree/release-4.9.5
> >>
> >> Hash for the release tag:
> >> 66b7e6f5f1d383a68082a2d5a9609f5165532841
> >>
> >> Release Notes:
> >> https://rocketmq.apache.org/zh/release-notes/2023/03/26/4.9.5/
> >>
> >>
> >> The artifacts have been signed with Key :
> >> EC9F268B4C20590138B11FE701420E4292296EAE, which can be found in the keys
> >> file:
> >> https://dist.apache.org/repos/dist/dev/rocketmq/KEYS
> >>
> >> Checklist for reference,
> >> Note that this is not official policy but may help with checking
> releases.
> >> Fill in the following:
> >>
> >> []  Checksums and PGP signatures are valid for Source package.
> >> []  Checksums and PGP signatures are valid for Binary package.
> >> []  Source code artifacts have correct names matching the current
> release.
> >> []  Binary artifacts have correct names matching the current release.
> >> []  License and Notice are correct in source package.
> >> []  License and Notice are correct in binary package.
> >> []  All files have license headers in source package if necessary.
> >> []  No compiled archives bundled in source archive.
> >> []  Hash and Tag in GitHub repo is matching the current artifacts.
> >> []  The code can be built success in the source package.
> >> []  Start nameserver and broker according to the quick-start
> >> []  Run clusterList command to see if the version is correct
> >>
> >> And any other check point is welcomed and please feel free to reply to
> >> this email, we sincerely hope to your feedback.
> >>
> >> The vote will be open for at least 72 hours or until necessary number of
> >> votes are reached.
> >>
> >> Please vote accordingly:
> >>
> >> [ ] +1 approve
> >>
> >> [ ] +0 no opinion
> >>
> >> [ ] -1 disapprove with the reason
> >>
> >> Thanks,
> >> The Apache RocketMQ Team
> >>
> > --
> >   =
> >
> >  fuyou001
> > Best Regards
>
>