> We need to determine the overall plan, not the implementation
> at this moment.
Great point, I agree.
> Looks like we need an option in the
> `CommandCloseProducer` to avoid the replication producer
> reconnecting again.
This is an important point. One of the primary requirements for
geo-repli
+1
Thanks,
Haiting
On 2022/02/26 02:53:23 Aloys Zhang wrote:
> Hi Pulsar Community,
>
> I would like to start a VOTE on "Support split bundle by specified
> boundaries."(PIP-143)
>
> Here is the design detail https://github.com/apache/pulsar/issues/13761
>
> and the discussion thread
> https:
Hi Pulsar Community,
I would like to start a VOTE on "Support split bundle by specified
boundaries."(PIP-143)
Here is the design detail https://github.com/apache/pulsar/issues/13761
and the discussion thread
https://lists.apache.org/thread/xz80vz4j1yv7zm5bh4pfxgm8p2rg289z
Thanks,
Aloys
Hi all,
Since there are no more suggestions for more than 72 hours, I have updated
the PIP https://github.com/apache/pulsar/issues/13761 according to the
discussion.
And then will send a vote thread soon.
Aloys Zhang 于2022年2月22日周二 10:38写道：
> >Should this be "positions"? We are going to split on
Hi Pulsar Community,
I recently contributed a "Security Policy and Supported Versions" page
to our website [0]. I just noticed that it is not yet showing up on
the website because it is in the versioned section of the
documentation. I think it would make sense to move this page location
so that it
rmyates commented on pull request #203:
URL:
https://github.com/apache/pulsar-helm-chart/pull/203#issuecomment-1051086894
@michaeljmarshall No worries. I think keeping the change for new
users/installs is fine and does make sense looking at the [k8s
docs](https://kubernetes.io/docs/concep
michaeljmarshall commented on pull request #203:
URL:
https://github.com/apache/pulsar-helm-chart/pull/203#issuecomment-1051068932
@rmyates - thank you for posting this message. This change was intended to
be backwards compatible, so it is valuable feedback to know it wasn't. Now that
we'
rmyates commented on pull request #203:
URL:
https://github.com/apache/pulsar-helm-chart/pull/203#issuecomment-1050973199
Note for future googlers, this change will break a helm chart upgrade if you
installed the chart before this change due to podManagementPolicy in a
StatefulSet being a
The replicated topic deletion also has a similar problem.
If the topic auto-creation is enabled, we are not able to delete
a replicated topic, because the producer used for replication
will try to reconnect. Looks like we need an option in the
`CommandCloseProducer` to avoid the replication produce
> Penghui, are you suggesting that we implement the namespace/tenant
terminated logic after completing this PIP?
I'm ok with both being implemented together or separated.
We need to determine the overall plan, not the implementation
at this moment.
> For the sake of discussion, if we implement th
Thanks, Michael,
I will wait for the solution.
Penghui
On Fri, Feb 25, 2022 at 3:12 PM Michael Marshall
wrote:
> Hello Pulsar Community,
>
> I am in the process of investigating what I believe to be a broker
> deadlock scenario that affects branch-2.9 and likely branch-2.10. (I
> haven't had a
11 matches
Mail list logo
