๐Ÿ“š Demo of several message sending methods of Rocket MQ

1, Basic sample Knowledge foreshadowing The steps of message sending are briefly listed as follows: Create a message producer and specify the producer group name Contact the Broker manager nameserver first. You need to specify the nameserver address Start producer. Create a message object and specify the Topic, Tag and message body send messag ...

Added by compound_eye on Thu, 03 Feb 2022 20:17:58 +0200

RocketMQ learning IX - Broker analysis

1, Data cached by BrokerBroker mainly caches routing information, including producer table, consumer table, consumerGroup table and topic table. This information is managed in producer manager, ConsumerManager, SubscriptionGroupManager and TopicConfigManager.ProducerManager //producer list HashMap<String /* group name */, HashMap<Channel, ...

Added by sandrob57 on Thu, 03 Feb 2022 16:31:58 +0200

Rocketmq source code analysis - message retry and delay fault-tolerant logic in the Producer part

Problem point 1. What if the message fails to be sent (due to the network, the broker hangs up)? How does the sender achieve high availability? 2. How to select the message queue, that is, which message queue does the producer send messages to? 3. Why design a broker failure delay mechanism separately? Producer message retry When the produce ...

Added by dmcdivitt on Thu, 03 Feb 2022 03:28:38 +0200

[learning notes] learning notes of RabbitMQ tutorial of teachers with poor programming

This article is the main "bad programming person" of station B RabbitMQ tutorial According to my study notes, up uses CentOS, while I usually use Ubuntu more, so this article is based on Ubuntu. In addition, it seems that RabbitMQ needs root permission, so all the following RabbitMQ related commands should preferably have sudo, otherw ...

Added by raymedia on Wed, 02 Feb 2022 10:51:22 +0200

RocketMQ learning VII - Application of Netty

1, Remoting communication mechanism in RocketMQRocketMQ message queue cluster mainly includes NameServe, Broker(Master/Slave), Producer and consumer. The basic communication process is as follows:Register yourself with NameServer after the Broker is started; Then regularly report Topic routing information to NameServer every 30s;When sending a ...

Added by axnoran on Mon, 31 Jan 2022 17:16:10 +0200

Message Oriented Middleware -- message rejection

In the previous section, I learned how consumers get messages So when consumers get the message and find that the message should not be solved by themselves, or an exception occurs during processing, how should they deal with it This is the message rejection in this section 1, Message reject There are also two ways to Reject messages: Rejec ...

Added by Lauj on Mon, 31 Jan 2022 02:18:59 +0200

Source code analysis of Offset management module OffsetManager of Kafka

Inside Kafka, there is a__ consumer_ The topic of offsets. This topic mainly saves the offset of each consumption group to the consumption of the partition under the topic, that is, to which offset it is consumed. In order to realize the function of offset management of consumption group, when a consumer obtains a message, it is necessary for t ...

Added by Braveheart on Sun, 30 Jan 2022 20:57:22 +0200

ActiveMQ: security mechanism, message persistence

1, Security mechanism 1.1. Modify ActiveMQ XML file Configure the < plugins > tag under the < broker > < / broker > tag. <beans xmlns="http://www.springframework.org/schema/beans" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://www.springframework.org/schema/beans http://www.spr ...

Added by erth on Sun, 30 Jan 2022 11:25:04 +0200

RocketMQ Part IV Rocket cluster configuration

In actual development, docker is generally used to install rocketmq. Docker installs rocketmq as follows: docker installation configuration rocketmq docker installing rocketmq docker pull foxiswho/rocketmq:server-4.3.2 docker pull foxiswho/rocketmq:broker-4.3.2 Create container docker create -p 9876:9876 --name rmqserver \ -e JAVA_OPT_EXT = ...

Added by daok on Sun, 30 Jan 2022 02:38:15 +0200

RocketMQ learning IV - message sending high availability design

We know that RocketMQ's NameServer is not strongly consistent, but ultimately consistent, that is, the client periodically obtains Broker information. If the Broker fails for a period of time, the client can't immediately sense it. How can RocketMQ achieve high availability of message sending? It can be expanded from the following three aspects ...

Added by optiplex on Sun, 30 Jan 2022 01:38:53 +0200