You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@pulsar.apache.org by Ruoruo Wong <wy...@gmail.com> on 2019/01/11 04:09:48 UTC
About explicitly choose partition topic
Hi Pulsar team
I am really pleasant that Pulsar system helps me to improve my business
performance.
And I have a problem about topic partition that I suppose the same hash
to be consumed by the same consumer, like Kafka.
After I check the document, only resolution is "use the
$TOPIC-partition-N as the topic name to subscribe to a specific subscription",
but this is not proper for elastic system.
Is there any other option could I choose?
Thanks
Re: About explicitly choose partition topic
Posted by Dave Fisher <da...@comcast.net>.
Adding the OP who I moderated onto the list.
(You subscribe by sending an email to dev-subscribe@pulsar.apache.org)
Sent from my iPhone
> On Jan 10, 2019, at 9:26 PM, Matteo Merli <mm...@apache.org> wrote:
>
> Hi Ruoruo,
>
> In order to consume messages in order on a partitioned topic, you should
> use the “Failover” subscription type.
>
> That will ensure that each partition will be asssigned to only 1 consumer,
> and you can add consumers to scale up your processsing. (And each consumer
> will get assigned multiple partitions).
>
> http://pulsar.apache.org/docs/en/standalone/#failover
>
>
>> On Thu, Jan 10, 2019 at 9:18 PM Ruoruo Wong <wy...@gmail.com> wrote:
>>
>> Hi Pulsar team
>> I am really pleasant that Pulsar system helps me to improve my business
>> performance.
>> And I have a problem about topic partition that I suppose the same hash
>> to be consumed by the same consumer, like Kafka.
>> After I check the document, only resolution is "use the
>> $TOPIC-partition-N as the topic name to subscribe to a specific
>> subscription",
>> but this is not proper for elastic system.
>> Is there any other option could I choose?
>>
>> Thanks
>>
> --
> Matteo Merli
> <mm...@apache.org>
Re: About explicitly choose partition topic
Posted by Matteo Merli <mm...@apache.org>.
Hi Ruoruo,
In order to consume messages in order on a partitioned topic, you should
use the “Failover” subscription type.
That will ensure that each partition will be asssigned to only 1 consumer,
and you can add consumers to scale up your processsing. (And each consumer
will get assigned multiple partitions).
http://pulsar.apache.org/docs/en/standalone/#failover
On Thu, Jan 10, 2019 at 9:18 PM Ruoruo Wong <wy...@gmail.com> wrote:
> Hi Pulsar team
> I am really pleasant that Pulsar system helps me to improve my business
> performance.
> And I have a problem about topic partition that I suppose the same hash
> to be consumed by the same consumer, like Kafka.
> After I check the document, only resolution is "use the
> $TOPIC-partition-N as the topic name to subscribe to a specific
> subscription",
> but this is not proper for elastic system.
> Is there any other option could I choose?
>
> Thanks
>
--
Matteo Merli
<mm...@apache.org>