Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Initialize: Minimum receiverQueueSize should be number of partitions in a partition consumer #146

Merged
merged 2 commits into from
Dec 15, 2016

Conversation

rdhabalia
Copy link
Contributor

Motivation

PartitionedConsumer with receiverQueueSize=1 initializes receiverQueue with type of ArrayBlockingQueue which can't consume messages from multiple partitions. Therefore, minimum size of partitioned-consumer's receiverQueue should be: Number of partitions in the topic.

Result

It can support partitioned-consumer with queue-size 1.

@yahoocla
Copy link

CLA is valid!

Copy link
Contributor

@merlimat merlimat left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

👍

@rdhabalia rdhabalia merged commit 525f1e3 into apache:branch-1.15 Dec 15, 2016
@rdhabalia rdhabalia deleted the 1.15.4 branch January 23, 2017 22:09
sijie pushed a commit to sijie/pulsar that referenced this pull request Mar 4, 2018
hrsakai pushed a commit to hrsakai/pulsar that referenced this pull request Dec 10, 2020
…ar proxy (apache#146)

if producer connect to broker through pulsar proxy, producer will get Short read when reading frame size error because pulsar proxy not pass commands to broker.
hangc0276 pushed a commit to hangc0276/pulsar that referenced this pull request May 26, 2021
Co-authored-by: weikang.yuan <yuanwk@inke.cn>
nicoloboschi pushed a commit to nicoloboschi/pulsar that referenced this pull request Oct 12, 2022
… from OODM (apache#146)

Modifications:
- limit the global number of pending reads to BookKeeper
- new configuration entry managedLedgerMaxPendingReadsBufferSizeInMB (0 = feature disabled)
- we estimate the entry size per-topic, using the size of the last read entry (new metric pulsar_ml_pending_reads_estimated_entry_size, per topic)
- new metric pulsar_ml_pending_reads_buffer_sizeto get the estimated size of in-flight read requests in bytes
- if the feature is disabled this changed does not add significant overhead

Result:
This prevents the broker from going to OutOfMemory (direct memory) in case of many concurrent reads from the bookie
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants