Details
-
Improvement
-
Status: Resolved
-
Major
-
Resolution: Fixed
-
None
-
None
-
None
Description
Replication sends messages faster than the network/receiver can consume. This results in many messages being queued by GRPC/Netty and the amount allocated memory surges and results in OOME.
Attachments
Issue Links
- causes
-
HDDS-9134 GRPC based replication can get stuck forever if the receiver is not available
- Resolved
- is related to
-
RATIS-1868 Handling Netty back pressure when streaming ratis log
- Resolved
-
RATIS-2189 Use ByteBufAllocator#ioBuffer in NettyDataStreamUtils
- Resolved
- links to