[VOTE] PIP-313 Support force unsubscribe using consumer api

[Rajan Dhabalia]

Hi,

I would like to start voting thread for PIP-313  which also addresses issue
# https://github.com/apache/pulsar/issues/21451

PIP design PR:
https://github.com/apache/pulsar/pull/21452

Thread:
https://lists.apache.org/thread/hptx8z9mktn94gvqtt4547wzcfcgdsrv

Thanks,
Rajan

Re: [VOTE] Pulsar Release 3.1.2 Candidate 1

[guo jiwei]

Hi
 We find a regression in 3.0,  Apache/Pulsar/#17512
 has fixed the data being
deleted when offload met Metastore exception, but Apache/Pulsar/#17915
 skip the logic, causing the
broker to delete the data from the tiered storage.
 I suggest dropping this vote and fix the issue then raise a new candidate.

Regards
Jiwei Guo (Tboy)


On Sat, Dec 2, 2023 at 4:56 PM houxiaoyu  wrote:

> This is the first release candidate for Apache Pulsar version 3.1.2.
>
> It fixes the following issues:
>
> https://github.com/apache/pulsar/pulls?q=is%3Apr+is%3Amerged+label%3Arelease%2F3.1.2+label%3Acherry-picked%2Fbranch-3.1+
>
> *** Please download, test and vote on this release. This vote will
> stay open for at least 72 hours ***
>
> Note that we are voting upon the source (tag), binaries are provided
> for convenience.
>
> Source and binary files:
> https://dist.apache.org/repos/dist/dev/pulsar/pulsar-3.1.2-candidate-1/
>
> SHA-512 checksums:
>
>
> 47e487de57c4354ed07a1690197eed9057e67ee85055d11c098ae6cff642b20e4966d43c3d52f449a942547d417dd20b94c353c7485cbd599f6f059147826f5f
> apache-pulsar-3.1.2-bin.tar.gz
>
>
> 664a5811788817c302c1e2a943f959339832ef77417e2ca566696948e330172ada878e1487402e9aff6a0a81a89b44404c797114eb2f27922f58831adfaa0582
> apache-pulsar-3.1.2-src.tar.gz
>
> Maven staging repo:
> https://repository.apache.org/content/repositories/orgapachepulsar-1255/
>
> The tag to verify:
> v3.1.2-candidate-1 (9f110390ebd3ccaeb67adec9c51631e735414ccd)
> https://github.com/apache/pulsar/releases/tag/v3.1.2-candidate-1
>
> Pulsar's KEYS file containing PGP keys you use to sign the release:
> https://dist.apache.org/repos/dist/dev/pulsar/KEYS
>
> Docker images:
>
> pulsar images:
> https://hub.docker.com/repository/docker/anonhxygo/pulsar
>
> pulsar-all images:
> https://hub.docker.com/repository/docker/anonhxygo/pulsar-all
>
> Please download the source package, and follow the README to build
> and run the Pulsar standalone service.
>
>
> Regards
> houxiaoyu
>

Re: [VOTE] Pulsar Release 3.1.2 Candidate 1

[houxiaoyu]

Thanks jiwei.

Drop this vote and I will raise the next candidate after fixing the bug

guo jiwei  于2023年12月7日周四 17:02写道：

> Hi
>  We find a regression in 3.0,  Apache/Pulsar/#17512
>  has fixed the data being
> deleted when offload met Metastore exception, but Apache/Pulsar/#17915
>  skip the logic, causing the
> broker to delete the data from the tiered storage.
>  I suggest dropping this vote and fix the issue then raise a new candidate.
>
> Regards
> Jiwei Guo (Tboy)
>
>
> On Sat, Dec 2, 2023 at 4:56 PM houxiaoyu  wrote:
>
> > This is the first release candidate for Apache Pulsar version 3.1.2.
> >
> > It fixes the following issues:
> >
> >
> https://github.com/apache/pulsar/pulls?q=is%3Apr+is%3Amerged+label%3Arelease%2F3.1.2+label%3Acherry-picked%2Fbranch-3.1+
> >
> > *** Please download, test and vote on this release. This vote will
> > stay open for at least 72 hours ***
> >
> > Note that we are voting upon the source (tag), binaries are provided
> > for convenience.
> >
> > Source and binary files:
> > https://dist.apache.org/repos/dist/dev/pulsar/pulsar-3.1.2-candidate-1/
> >
> > SHA-512 checksums:
> >
> >
> >
> 47e487de57c4354ed07a1690197eed9057e67ee85055d11c098ae6cff642b20e4966d43c3d52f449a942547d417dd20b94c353c7485cbd599f6f059147826f5f
> > apache-pulsar-3.1.2-bin.tar.gz
> >
> >
> >
> 664a5811788817c302c1e2a943f959339832ef77417e2ca566696948e330172ada878e1487402e9aff6a0a81a89b44404c797114eb2f27922f58831adfaa0582
> > apache-pulsar-3.1.2-src.tar.gz
> >
> > Maven staging repo:
> > https://repository.apache.org/content/repositories/orgapachepulsar-1255/
> >
> > The tag to verify:
> > v3.1.2-candidate-1 (9f110390ebd3ccaeb67adec9c51631e735414ccd)
> > https://github.com/apache/pulsar/releases/tag/v3.1.2-candidate-1
> >
> > Pulsar's KEYS file containing PGP keys you use to sign the release:
> > https://dist.apache.org/repos/dist/dev/pulsar/KEYS
> >
> > Docker images:
> >
> > pulsar images:
> > https://hub.docker.com/repository/docker/anonhxygo/pulsar
> >
> > pulsar-all images:
> > https://hub.docker.com/repository/docker/anonhxygo/pulsar-all
> >
> > Please download the source package, and follow the README to build
> > and run the Pulsar standalone service.
> >
> >
> > Regards
> > houxiaoyu
> >
>

Re: [DISCUSS] PIP-321 Split the responsibilities of namespace replication-clusters

[Xiangying Meng]

Hi Girish,

I'm very pleased that we have reached some consensus now. Pulsar already
supports geo-replication at the topic level, but the existing
implementation of this topic level replication does not match our
expectations.

At the moment, I can think of three directions to solve this problem:

1. Treat this issue as a bug and fix it so that Pulsar can truly support
replication at the topic level.
2. Limit the replication topic policy, so that the replication clusters at
the topic level must be included in the replication clusters configured at
the namespace level. In this case, the topic level replication would serve
as a supplement to the namespace replication, rather than a true topic
level policy.
3. Remove topic level replication.

I lean towards the first option, as it would make Pulsar's replication
configuration more flexible and would not break the previous behavior logic.

>Yes, that's my viewpoint. In case that's not your view point, then in your
>use cases do you ever have more than one namespace inside a tenant?
>With every property coming at topic level, it makes no sense for the
>namespace hierarchy to exist anymore.

I didn't propose this from the perspective of a user, but from the
perspective of a Pulsar maintainer. The replication cluster at the topic
level cannot function independently like other topic policies, and I
attempted to fix it after finding the reason.

>From the user's perspective, I could modify my system to put topics with
the same replication strategy under the same namespace. From the
maintainer's perspective, if a feature can help users use Pulsar more
flexibly and conveniently without introducing risks, then this feature
should be implemented. Perhaps business systems do not want to maintain too
many namespaces, as they would need to configure multiple namespace
policies or it might make their business logic complex. The other
configurations for topics under this namespace might be consistent, with
only a few topics needing to enable replication. In this case, topic level
replication becomes valuable. Therefore, I lean towards the first option,
to solve this problem and make it a truly expected topic policy.

On Thu, Dec 7, 2023 at 12:45 PM Girish Sharma 
wrote:

> Hello Xiangying,
>
>
> On Thu, Dec 7, 2023 at 6:32 AM Xiangying Meng 
> wrote:
>
> > Hi Girish,
> >
> > What you are actually opposing is the implementation of true topic-level
> > geo-replication. You believe that topics should be divided into different
> > namespaces based on replication. Following this line of thought, what we
> > should do is restrict the current topic-level replication settings, not
> > allowing the replication clusters set at the topic level to exceed the
> > range of replication clusters set in the namespace.
> >
>
> Yes, that's my viewpoint. In case that's not your view point, then in your
> use cases do you ever have more than one namespace inside a tenant?
> With every property coming at topic level, it makes no sense for the
> namespace hierarchy to exist anymore.
>
>
> >
> > One point that confuses me is that we provide a setting for topic-level
> > replication clusters, but it can only be used to amend the namespace
> > settings and cannot work independently. Isn't this also a poor design for
> > Pulsar?
> >
>
> This feature was originally added in pulsar without a PIP. And the PR [0]
> also doesn't have much context around why it was needed and why it is being
> added.. So I can't comment on why this was added..
> But my understanding is that even in a situation when the topics are
> divided into proper namespaces based on use cases and suddenly there is an
> exceptional need for one of the existing topics to have lesser replication,
> then instead of following a long exercise of moving that topic to a new
> namespace, you can use this feature.
>
> [0] - https://github.com/apache/pulsar/pull/12136
>
>
>
> >
> > On Thu, Dec 7, 2023 at 2:28 AM Girish Sharma 
> > wrote:
> >
> > > Hello, replies inline.
> > >
> > > On Wed, Dec 6, 2023 at 5:28 PM Xiangying Meng 
> > > wrote:
> > >
> > > > Hi Girish,
> > > >
> > > > Thank you for your explanation. Because Joe's email referenced the
> > > current
> > > > implementation of Pulsar, I misunderstood him to be saying that this
> > > > current implementation is not good.
> > > >
> > > > A possible use case is where there is one or a small number of topics
> > in
> > > > the namespace that store important messages, which need to be
> > replicated
> > > to
> > > > other clusters. Meanwhile, other topics only need to store data in
> the
> > > > local cluster.
> > > >
> > >
> > > Is it not possible to simply have the other topics in a namespace which
> > > allows for that other cluster, and the local topics remain in the
> > namespace
> > > with local cluster needs. Seems to me like a proper use case of two
> > > different namespaces as the use case is different in both cases.
> > >
> > >
> > >
> > > >
> > > > For example, only topic1 needs 

Re: [ANNOUNCE] Apache Pulsar 3.0.2 released

[Kiryl Valkovich]

Hi, Zike

Thanks for fixing it.

One more thing to fix. v3.0.2 release is missing on the Downloads page. I 
raised one more issue here:
https://github.com/apache/pulsar/issues/21694


From: Zike Yang 
Date: Wednesday, December 6, 2023 at 1:08 PM
To: dev@pulsar.apache.org 
Subject: Re: [ANNOUNCE] Apache Pulsar 3.0.2 released
Hi, Kiryl

Thanks for your catch. I have submitted a PR to fix it:
https://github.com/apache/pulsar-site/pull/746 PTAL.

Thanks,
Zike Yang

On Wed, Dec 6, 2023 at 4:41 PM Kiryl Valkovich
 wrote:
>
> Congrats on the release!
>
> Small fixes in the Release table are needed. I raised the issue here:
> https://github.com/apache/pulsar/issues/21677
>
>
> Best,
> Kiryl
>
> From: Yubiao Feng 
> Date: Wednesday, December 6, 2023 at 8:17 AM
> To: dev@pulsar.apache.org , us...@pulsar.apache.org 
> , annou...@apache.org 
> Subject: [ANNOUNCE] Apache Pulsar 3.0.2 released
> The Apache Pulsar team is proud to announce Apache Pulsar version 3.0.2.
>
> Pulsar is a highly scalable, low-latency messaging platform running on
> commodity hardware. It provides simple pub-sub semantics over topics,
> guaranteed at-least-once delivery of messages, automatic cursor management
> for
> subscribers, and cross-datacenter replication.
>
> For Pulsar release details and downloads, visit:
>
> https://pulsar.apache.org/download
>
> Release Notes are at:
> https://pulsar.apache.org/release-notes
>
> We would like to thank the contributors that made the release possible.
>
> Regards,
>
> The Pulsar Team

Re: [VOTE] DotPulsar Release 3.1.1 RC 1

[Daniel Blankensteiner]

+1 (binding)

Tested on Windows 10 with .NET 8(.0.100).

Best regards

Daniel Blankensteiner

tison skrev den 2023-12-07 03:14:

Hi everyone,

This is a quick fix patch release for exactly
https://github.com/apache/pulsar-dotpulsar/commit/f35e6824f0790696bf4300dcd7a00967cf6c250e
:

Fixed a bug where disposing a disconnected consumer, reader or
producer would cause a hang

Please review and vote on the release candidate #1 for the version
3.1.1, as follows:
[ ] +1, Approve the release
[ ] -1, Do not approve the release (please provide specific comments)

DotPulsar's KEYS file contains PGP keys we used to sign this release:
https://downloads.apache.org/pulsar/KEYS

Please download these packages and review this release candidate:
- Review release notes
- Download the source package (verify shasum, and asc) and follow the
README.md to build and run DotPulsar.

The vote will be open for at least 72 hours. It is adopted by majority
approval, with at least 3 PMC affirmative votes.

Source file:
https://dist.apache.org/repos/dist/dev/pulsar/pulsar-dotpulsar-3.1.1-rc.1/

Nuget package:
https://www.nuget.org/packages/DotPulsar/3.1.1-rc.1

The tag to be voted upon:
https://github.com/apache/pulsar-dotpulsar/tree/3.1.1-rc.1

SHA-512 checksums:
784a0afb1a78122bb4c90ed8b2a3945b14628c78b9c0b902e376c74fa0b0d644ace8646357a22fbbebaac5929e0f7781deb416f17c68bb354903159023b5e012
 pulsar-dotpulsar-3.1.1.tar.gz

Best,
tison.

Re: [VOTE] DotPulsar Release 3.1.1 RC 1

[tison]

+1 (binding)

+ Signature and checksum match
+ Download link valid
+ Can compile from source (on macOS aarch64)
+ LICENSE and NOTICE present

Best,
tison.

Daniel Blankensteiner  于2023年12月8日周五 15:24写道：
>
> +1 (binding)
>
> Tested on Windows 10 with .NET 8(.0.100).
>
> Best regards
>
> Daniel Blankensteiner
>
> tison skrev den 2023-12-07 03:14:
> > Hi everyone,
> >
> > This is a quick fix patch release for exactly
> > https://github.com/apache/pulsar-dotpulsar/commit/f35e6824f0790696bf4300dcd7a00967cf6c250e
> > :
> >
> > Fixed a bug where disposing a disconnected consumer, reader or
> > producer would cause a hang
> >
> > Please review and vote on the release candidate #1 for the version
> > 3.1.1, as follows:
> > [ ] +1, Approve the release
> > [ ] -1, Do not approve the release (please provide specific comments)
> >
> > DotPulsar's KEYS file contains PGP keys we used to sign this release:
> > https://downloads.apache.org/pulsar/KEYS
> >
> > Please download these packages and review this release candidate:
> > - Review release notes
> > - Download the source package (verify shasum, and asc) and follow the
> > README.md to build and run DotPulsar.
> >
> > The vote will be open for at least 72 hours. It is adopted by majority
> > approval, with at least 3 PMC affirmative votes.
> >
> > Source file:
> > https://dist.apache.org/repos/dist/dev/pulsar/pulsar-dotpulsar-3.1.1-rc.1/
> >
> > Nuget package:
> > https://www.nuget.org/packages/DotPulsar/3.1.1-rc.1
> >
> > The tag to be voted upon:
> > https://github.com/apache/pulsar-dotpulsar/tree/3.1.1-rc.1
> >
> > SHA-512 checksums:
> > 784a0afb1a78122bb4c90ed8b2a3945b14628c78b9c0b902e376c74fa0b0d644ace8646357a22fbbebaac5929e0f7781deb416f17c68bb354903159023b5e012
> >  pulsar-dotpulsar-3.1.1.tar.gz
> >
> > Best,
> > tison.