[
https://issues.apache.org/jira/browse/FLINK-28870?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
xie updated FLINK-28870:
------------------------
Description:
When using Pulsar Source to consume data, if the data rate is small, e.g. 2
msg/s, there will be long periods of time when no messages are consumed. This
is caused by the default PulsarSourceOptions.PULSAR_MAX_FETCH_TIME and
PulsarSourceOptions.PULSAR_MAX_FETCH_RECORDS. Pulsar Source will try to pull
messages until any one of the condition exceed.
was:
when we use the pulsar-connector as source and consume messages,I feel that the
consumption rate is a bit low. It was later found out that it was caused by
two default parameters:
PulsarSourceOptions.PULSAR_MAX_FETCH_TIME, default 10s;
PulsarSourceOptions.PULSAR_MAX_FETCH_RECORDS, default 100;
We are small business volume, hope we can improve the consumption speed.
Priority: Major (was: Minor)
Summary: Pulsar Source hangs on the small incoming message rates (was:
Modify the pulsar default consumption rate)
> Pulsar Source hangs on the small incoming message rates
> -------------------------------------------------------
>
> Key: FLINK-28870
> URL: https://issues.apache.org/jira/browse/FLINK-28870
> Project: Flink
> Issue Type: Improvement
> Components: Connectors / Pulsar
> Reporter: xie
> Priority: Major
>
> When using Pulsar Source to consume data, if the data rate is small, e.g. 2
> msg/s, there will be long periods of time when no messages are consumed. This
> is caused by the default PulsarSourceOptions.PULSAR_MAX_FETCH_TIME and
> PulsarSourceOptions.PULSAR_MAX_FETCH_RECORDS. Pulsar Source will try to pull
> messages until any one of the condition exceed.
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
