Details
-
Task
-
Resolution: Unresolved
-
Major
-
7.6.0
-
0
-
March-June 24
Description
That is the old dcp_consumer_process_buffered_messages_yield_limit, renamed as part of MB-31869.
Since Trinity, the DCP Consumer doesn't buffer messages and the DcpConsumerTask is only responsible for processing unacked bytes.
That is a fast operation, so probably we don't need any yielding anymore.
Attachments
Issue Links
- is triggered by
-
MB-31869 Remove DCPConsumer internal buffer
- Closed