apache/rocketmq
Watch
1
0
Fork
You've already forked rocketmq
 0
mirror of https://github.com/apache/rocketmq.git synced 2026-11-07 14:07:35 +00:00
Code Issues Projects Releases Packages Wiki Activity
Page: RIP 54 Backporting of Remoting based Client
Pages
FAQ Home How to Configure TLS RIP 1 MQTT Bridge RIP 10 RocketMQ Unit Test RIP 11 Evolution of The Next Decade Architecture for RocketMQ RIP 12 Message Connector RIP 13 RocketMQ Console Project RIP 14 RocketMQ Community Operation Conventions RIP 15 RocketMQ IPv6 Support Project RIP 16 RocketMQ RPC(Request Response model) Support RIP 17 RocketMQ HTTP Proxy Support RIP 18 Metadata Management Architecture Upgrade RIP 2 RocketMQ Spring RIP 20 Streaming Tiered Storage Optimize RIP 21 logical queue abstraction for static topic and fast scale out RIP 26 Improve Batch Message Processing Throughput RIP 27 Auto batching in producer RIP 28 Light message queue (LMQ) RIP 29 Optimize RocketMQ NameServer RIP 3 RocketMQ Python Client RIP 30 Support Compaction topic RIP 31 Support RocketMQ BrokerContainer RIP 32 Slave Acting Master Mode RIP 33 RocketMQ MQTT RIP 34 Support quorum write and adaptive degradation in master slave architecture RIP 4 RocketMQ Go Client RIP 41 RocketMQ E2E Test RIP 42 Support Schema Registry RIP 44 Support DLedger Controller RIP 45 RocketMQ Replicator 2.0 RIP 45 Support Graceful Shutdown RIP 46 Observability Improvement for RocketMQ RIP 47 Data Layout V2 RIP 48 Enhance server side offset management ability RIP 49 RocketMQ remoting module improvement RIP 5 RocketMQ ACL RIP 50 RocketMQ Transaction Message Improvement RIP 51 Pop orderly improvement RIP 52 Optimize Building ConsumeQueue RIP 54 Backporting of Remoting based Client RIP 55 Support remoting protocol in rocketmq proxy module RIP 56 Replace Logging Module with Shaded Logback RIP 57 Tiered storage for RocketMQ RIP 6 Message Trace RIP 63 Queue selection strategy optimization RIP 65 Tiered Storage Optimization RIP 66 Support KV(Rocksdb) Storage RIP 7 Multiple Directories Storage Support RIP 8 Consumer RACK Support RIP 9 RocketMQ Developer Guide RIP‐67 jRaft‐Controller Implemention RIP‐80 Priority Message RIP‐82 Implement Timer message, transaction message, and index based on RocksDB RIP‐82 Implement Timer transaction message and index based on RocksDB RIP‐83 Lite Topic: A New Message Model Release and Lifetime Support Policy RocketMQ Improvement Proposal SoC [RIP 19] Server side rebalance, lightweight consumer client support [RIP 58] RocketMQ Streams improvement [RIP‐70] Optimizing Lock Mechanisms [RIP‐73] Pop Consumption Improvement Based on RocksDB [RIP‐74] Flink‐Connector‐RocketMQ Dynamic Load Balancing [RIP‐77] Deprecate and Remove ACL 1.0
2 RIP 54 Backporting of Remoting based Client
Aaron Ai edited this page 2022-10-21 10:30:06 +08:00
Table of contents

Status

Background & Motivation

What do we need to do

  • Will we add a new module? -- No.
  • Will we add new APIs? -- No.
  • Will we add a new feature? -- No.

Why should we do that

Are there any problems with our current project?

Since gRPC/protobuf-based client has been released, more features will prefer to be developed on gRPC/protobuf-based client rather than the remoting-base client, but there are still many developers using the remoting-based client, which could not be ignored.

Alibaba Group has made many changes and optimizations to the client in its long-term production practices. Unfortunately, not all changes are merged into the upstream repository in time due to different release paces and strategies.

In order to unify the code, while improving the stability of the client, backporting is essential.

What can we benefit from proposed changes?

More stable, unified remoting-based RocketMQ client.

Goals

What problem is this proposal designed to solve?

Improve the stability of the remoting-based client mainly.

Non-Goals

What problem is this proposal NOT designed to solve?

This RIP does not introduce new features to the remoting-based client.

Changes

Architecture

We will divide this RIP into multiple pull requests, which will:

  • Fix an exponential duplication of message issue when messages were backed out to brokers on application process failure for future retry;
  • Justify an offset management flaw;
  • Fix several exceptions catch missing;
  • Refactor XXX to follow single responsibility principle; ...

Interface Design/Change

No interface changes involved.

Compatibility, Deprecation, and Migration Plan

This RIP doesn't introduce any compatibility issues.

Implementation Outline

This RIP is miscellaneous so that maybe it is not possible to include all specific topics in the proposal, you can see more details from pull requests soon.

Rejected Alternatives

No other cadicate alternatives.

Copyright © 2016~2022 The Apache Software Foundation.