Re: [Discuss] Pulsar retention policy

2024-04-13 Thread Yike Xiao 
Hi Jiuming,

Thank you for bringing this up. From a Pulsar admin perspective, the current 
retention policy implementation does not ensure that users can seek back to a 
position within a specific size limit or have to pay extra cost to achieve 
that. For example, to guarantee able to seek back to a position 10GB earlier, 
users need to set the `retention policy = backlog quota + 10GB`. However, the 
backlog quota is typically set quite large to allow for significant data 
accumulation. Therefore, users must bear the cost of a large backlog quota 
(e.g., 100GB) to ensure they can revert to a position 10GB earlier, even if 
there isn't backlog in subscription.

Regards,
Yike

From: 太上玄元道君 
Sent: Thursday, April 11, 2024 18:20
To: dev@pulsar.apache.org 
Subject: [Discuss] Pulsar retention policy

Hi, Pulsar community,

I'm opening this thread to discuss the retention policy for managed ledgers.

Currently, the retention policy is defined as a time/size-based policy to
retain messages in the ledger, but there is a difference between the
official documentation and the actual code implementation.

The official documentation states that the retention policy is to retain
the messages that were *acknowledged*. For example, if the retention size
is set to 10GB and there are 20GB of messages acknowledged, Pulsar will
retain 10GB and delete the rest.

However, the actual code implementation is different. It retains the
messages that were *written* to the ledger, including *backlog messages*
and *acknowledged messages*. For instance, if there are 10GB of messages in
the backlog and 10GB of messages were acknowledged:
1. If the retention size is set to 10GB, Pulsar will only retain the 10GB
of messages in the backlog, and the 10GB of messages that were acknowledged
will be deleted.
2. If the retention size is set to 20GB, Pulsar will retain the 10GB of
messages in the backlog and the 10GB of messages that were acknowledged.
3. If the retention size is set to 5GB, Pulsar will retain the 10GB of
messages in the backlog, but the 10GB of messages that were acknowledged
will be deleted.
4. If the retention size is set to 15GB, Pulsar will retain the 10GB of
messages in the backlog and the 5GB of messages that were acknowledged. The
rest of the acknowledged messages will be deleted.

>From Pulsar open source to the present, the code implementation has never
changed, but the meaning of the official documentation has gradually
shifted. So I'm just considering which one is better: the official
documentation or the code implementation? Does the change in the meaning of
the document align more with expectations? Does it indicate that users want
to retain the messages that were acknowledged?

For a long time, users have believed that the Retention Policy is for
retaining messages that were acknowledged. If we change the document to
match the code implementation, will it meet users' expectations?

What should we do? Change the document to match the code implementation or
change the code implementation to match the document?

Regards,
Tao Jiuming

Re: [ANNOUNCE] Baodi Shi as a new PMC member in Apache Pulsar

2024-04-12 Thread Yike Xiao 
Congrats, Baodi!

Yike Xiao

> On Apr 11, 2024, at 21:22, PengHui Li  wrote:
>
> The Apache Pulsar Project Management Committee (PMC) has invited
> Baodi Shi https://github.com/shibd to join the PMC,
> and we are pleased to announce that he has accepted.
>
> Baodi Shi is actively driving the NodeJS client release, contributing to
> multiple
> Pulsar repos, Nodejs client, CPP Client, Python Client, and Pulsar main
> repo.
>
> On behalf of the Pulsar PMC, we extend a heartfelt welcome and
> congratulations to Baodi Shi.
>
> Regards,
> Penghui

Re: [ANNOUNCE] Zike Yang as a new PMC member in Apache Pulsar

2024-04-12 Thread Yike Xiao 
Congrats, Zike!

Yike Xiao

> On Apr 11, 2024, at 21:25, PengHui Li  wrote:
>
> The Apache Pulsar Project Management Committee (PMC) has invited
> Zike Yang https://github.com/RobertIndie to join the PMC,
> and we are pleased to announce that he has accepted.
>
> Zike Yang is actively driving the Golang client release, contributing to
> multiple
> Pulsar repos, Golang client, CPP Client, Python Client, and Pulsar main
> repo.
>
> On behalf of the Pulsar PMC, we extend a heartfelt welcome and
> congratulations to Zike Yang.
>
> Regards,
> Penghui

Re: [DISCUSS] Remove the limitation between backlog quota and retention policy

2024-04-10 Thread Yike Xiao 
Here's a hint as to why this restriction was introduced.
After reviewing the current implementation of the retention policy, I found 
that the logic for determining whether a ledger exceeds the retention size and 
should be deleted is based on the following logic (pseudocode):

```
long totalSizeToDelete = 0;
for (ledger in ledgersBeforeSlowestReaderLedgerId) {
  totalSizeToDelete += ledger.size;
  if (managedLedgerTotalSize - totalSizeToDelete >= retentionSize) {
// add this ledger to ledgersToDelete list
  }
}
```

The actual code can be seen at: [1]

The issue lies in the use of `managedLedgerTotalSize - totalSizeToDelete >= 
retentionSize`, where `managedLedgerTotalSize` is used instead of 
`SUM(ledgerSize(ledgersBeforeSlowestReaderLedgerId))`. This causes ledgers that 
have not been acknowledged to also be included in the retention size comparison.

Here is an example to illustrate the problem:
Suppose the current ManagedLedger has 5 ledgers, [1, 2, 3, 4, 5], each ledger's 
size is 1MB, and the retentionSize is set to 2MB. The current 
slowestReaderLedgerId is 3. Based on the current implementation, ledgers 1 and 
2 are expected to be retained but will be deleted.
The retention policy will only actually take effect when the retentionSize 
exceeds the backlog quota.

[1]: 
https://github.com/apache/pulsar/blob/master/managed-ledger/src/main/java/org/apache/bookkeeper/mledger/impl/ManagedLedgerImpl.java#L2695-L2696

Regards,
Yike

From: Yike Xiao 
Sent: Wednesday, April 3, 2024 15:36
To: dev@pulsar.apache.org 
Subject: [DISCUSS] Remove the limitation between backlog quota and retention 
policy

Hi all,

In Pulsar, backlogs consist of unacknowledged messages. Once a message is 
acknowledged by all subscriptions, it enters the retention stage, as clearly 
illustrated in the official documentation [1]. The backlog quota limits the 
size and/or time threshold of the backlog, while the retention policy dictates 
the duration or volume of messages (acknowledged by all subscriptions) to 
retain.

However, I encountered an undocumented restriction that mandates the backlog 
quota to be greater than the retention policy. For example, a namespace with a 
backlog quota 20GB in size and unlimited in time cannot have a 2GB in size and 
7 days in time retention policy. This detail is implemented in the code [3].

This restriction poses challenges in scenarios where there's a need for a 
larger backlog quota to accommodate extensive usage while desiring a shorter 
retention period for traceback purposes. Such configurations seem unattainable 
under the current constraint.

Given that this limitation has been part of Pulsar since its initial 
open-source release, I am curious about the rationale behind it. Understanding 
the original intent or the technical considerations that led to this 
restriction would be immensely helpful.

Therefore, I propose reevaluating and potentially removing this restriction to 
allow for more flexible configurations of backlog quota and retention policy.

I would greatly appreciate your thoughts on this matter.

Thank you for your time and consideration. I look forward to your response and 
am eager to contribute further to this discussion.

[1]: 
https://jpn01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fpulsar.apache.org%2Fdocs%2Fnext%2Fcookbooks-retention-expiry%2F%23retention-policies=05%7C02%7C%7Ccb059c912d5a4f98327308dc53b0ded0%7C84df9e7fe9f640afb435%7C1%7C0%7C638477266343295533%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C0%7C%7C%7C=wRjCYXkwGq4TAhYet8FdxkpnaehpCay7ST1AZi2jKAo%3D=0<https://pulsar.apache.org/docs/next/cookbooks-retention-expiry/#retention-policies>
[3]: 
https://jpn01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fapache%2Fpulsar%2Fblob%2F7315aeb6258b7adc9d874268d50acb95ffc0cf2b%2Fpulsar-broker%2Fsrc%2Fmain%2Fjava%2Forg%2Fapache%2Fpulsar%2Fbroker%2Fadmin%2FAdminResource.java%23L374-L393=05%7C02%7C%7Ccb059c912d5a4f98327308dc53b0ded0%7C84df9e7fe9f640afb435%7C1%7C0%7C638477266343313621%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C0%7C%7C%7C=JmKZUCH%2F9dD07pGIknGpOnTfGUNmaDAn3bM7f%2FirgKg%3D=0<https://github.com/apache/pulsar/blob/7315aeb6258b7adc9d874268d50acb95ffc0cf2b/pulsar-broker/src/main/java/org/apache/pulsar/broker/admin/AdminResource.java#L374-L393>

Regards,
Yike

[DISCUSS] Remove the limitation between backlog quota and retention policy

2024-04-03 Thread Yike Xiao 
Hi all,

In Pulsar, backlogs consist of unacknowledged messages. Once a message is 
acknowledged by all subscriptions, it enters the retention stage, as clearly 
illustrated in the official documentation [1]. The backlog quota limits the 
size and/or time threshold of the backlog, while the retention policy dictates 
the duration or volume of messages (acknowledged by all subscriptions) to 
retain.

However, I encountered an undocumented restriction that mandates the backlog 
quota to be greater than the retention policy. For example, a namespace with a 
backlog quota 20GB in size and unlimited in time cannot have a 2GB in size and 
7 days in time retention policy. This detail is implemented in the code [3].

This restriction poses challenges in scenarios where there's a need for a 
larger backlog quota to accommodate extensive usage while desiring a shorter 
retention period for traceback purposes. Such configurations seem unattainable 
under the current constraint.

Given that this limitation has been part of Pulsar since its initial 
open-source release, I am curious about the rationale behind it. Understanding 
the original intent or the technical considerations that led to this 
restriction would be immensely helpful.

Therefore, I propose reevaluating and potentially removing this restriction to 
allow for more flexible configurations of backlog quota and retention policy.

I would greatly appreciate your thoughts on this matter.

Thank you for your time and consideration. I look forward to your response and 
am eager to contribute further to this discussion.

[1]: 
https://pulsar.apache.org/docs/next/cookbooks-retention-expiry/#retention-policies
[3]: 
https://github.com/apache/pulsar/blob/7315aeb6258b7adc9d874268d50acb95ffc0cf2b/pulsar-broker/src/main/java/org/apache/pulsar/broker/admin/AdminResource.java#L374-L393

Regards,
Yike

Re: [VOTE] Release Apache Pulsar 3.0.4 based on 3.0.4-candidate-1

2024-04-01 Thread Yike Xiao 
+1 (non-binding)

- Checked the signatures and checksums
- Built from source
  ```
  Apache Maven 3.8.5 (3599d3414f046de2324203b78ddcf9b5e4388aa0)
  Maven home: /usr/local/maven
  Java version: 17.0.3.1, vendor: Oracle Corporation, runtime: 
/Library/Java/JavaVirtualMachines/jdk-17.0.3.1.jdk/Contents/Home
  Default locale: en_CN, platform encoding: UTF-8
  OS name: "mac os x", version: "14.4.1", arch: "x86_64", family: "mac"
  ```
- Run standalone and checked produce and consume
- Run a cluster with 2 brokers and 3 bookies by docker image 
(`lhotari/pulsar:3.0.4-5a1fa0c`)

Regards,
Yike

From: Lari Hotari 
Sent: Friday, March 29, 2024 3:21
To: dev@pulsar.apache.org 
Subject: [VOTE] Release Apache Pulsar 3.0.4 based on 3.0.4-candidate-1

Hello Apache Pulsar Community,

This is a call for the vote to release the Apache Pulsar version 3.0.4 based on 
3.0.4-candidate-1.

Included changes since the previous release:
https://jpn01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fapache%2Fpulsar%2Fcompare%2Fv3.0.3...v3.0.4-candidate-1=05%7C02%7C%7C5eb9ece283dc4c61404808dc4f5c5dff%7C84df9e7fe9f640afb435%7C1%7C0%7C638472505351021679%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C0%7C%7C%7C=Ncq6ioCrn8CWhdJ6PFt%2BeOKb%2Bom3B2HamUwXoxYp35s%3D=0

*** Please download, test and vote on this release. This vote will stay open
for at least 72 hours ***

Only votes from PMC members are binding, but members of the community are
encouraged to test the release and vote with "(non-binding)".

Note that we are voting upon the source (tag), binaries are provided for
convenience.

The release candidate is available at:
https://jpn01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdist.apache.org%2Frepos%2Fdist%2Fdev%2Fpulsar%2Fpulsar-3.0.4-candidate-1%2F=05%7C02%7C%7C5eb9ece283dc4c61404808dc4f5c5dff%7C84df9e7fe9f640afb435%7C1%7C0%7C638472505351031981%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C0%7C%7C%7C=jxrBE37mapskOznzp4IEBgveROh5%2FzI%2Bz%2Fopg3KlVG0%3D=0

SHA-512 checksums:
9ba5d46f57c06f4c401664ed1ac2e31f7e0d93a09cda4c82ca05e3854422528e8fe6ab7c7003fed10c854f4bfda70376acb95f49df85d3cd2ed1e020e40886b2
  apache-pulsar-3.0.4-src.tar.gz
6167eada33c4c7b744c18b0b4c62a41282f42f302869f21dda2d0ea480389f7e5325007d1f13675bd7e3ee67f83a5c72940a28c968e53f7b741ea016d8c987fe
  apache-pulsar-3.0.4-bin.tar.gz

Maven staging repo:
https://jpn01.safelinks.protection.outlook.com/?url=https%3A%2F%2Frepository.apache.org%2Fcontent%2Frepositories%2Forgapachepulsar-1285=05%7C02%7C%7C5eb9ece283dc4c61404808dc4f5c5dff%7C84df9e7fe9f640afb435%7C1%7C0%7C638472505351039515%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C0%7C%7C%7C=Rp%2B0octSdDm7HjySkSpLE9HXl6uH0C51U3LICCt0NrQ%3D=0

The tag to be voted upon:
v3.0.4-candidate-1 (commit 5a1fa0c5c6709bdb7b003ce12d00abf52da293e1)
https://jpn01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fapache%2Fpulsar%2Freleases%2Ftag%2Fv3.0.4-candidate-1=05%7C02%7C%7C5eb9ece283dc4c61404808dc4f5c5dff%7C84df9e7fe9f640afb435%7C1%7C0%7C638472505351045597%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C0%7C%7C%7C=UW6pXZKj5dapTsVu55OH28l8aUQXHiOFwy7R%2B%2BXQsxc%3D=0

Pulsar's KEYS file containing PGP keys you use to sign the release:
https://jpn01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdownloads.apache.org%2Fpulsar%2FKEYS=05%7C02%7C%7C5eb9ece283dc4c61404808dc4f5c5dff%7C84df9e7fe9f640afb435%7C1%7C0%7C638472505351050849%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C0%7C%7C%7C=ze0qjM6Bpf%2FfbTg4ZI%2BcF1VP6YbCOzFEgXcPgJjvTC4%3D=0

Docker images:
docker pull lhotari/pulsar:3.0.4-5a1fa0c
https://jpn01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fhub.docker.com%2Flayers%2Flhotari%2Fpulsar%2F3.0.4-5a1fa0c%2Fimages%2Fsha256-c6379e2c94bef2515e4e1b839532f220cc46742eb7d7e4d537d162090dda05ab%3Fcontext%3Dexplore=05%7C02%7C%7C5eb9ece283dc4c61404808dc4f5c5dff%7C84df9e7fe9f640afb435%7C1%7C0%7C638472505351055521%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C0%7C%7C%7C=jOWDH70EI24cedQxANucRjS%2FcvMCmHZXBuAh68GsQDY%3D=0
docker pull lhotari/pulsar-all:3.0.4-5a1fa0c

Re: [ANNOUNCE] New Committer: Asaf Mesika

2024-02-21 Thread Yike Xiao 
Congrats! Asaf

Yike Xiao

> On Feb 21, 2024, at 18:55, houxiaoyu  wrote:
>
> Congratulations!
>
> Best,
> houxiaoyu
>
> Max Xu  于2024年2月21日周三 17:32写道：
>>
>> Congratulations, Asaf! Well deserved.
>>
>>
>> Best,
>> Max Xu
>>
>>
>>> On Wed, Feb 21, 2024 at 12:51 AM Lari Hotari  wrote:
>>>
>>> The Apache Pulsar Project Management Committee (PMC) has invited
>>> Asaf Mesika https://github.com/asafm to become a committer and we
>>> are pleased to announce that he has accepted.
>>>
>>> Welcome and Congratulations, Asaf Mesika!
>>>
>>> Please join us in congratulating and welcoming Asaf onboard!
>>>
>>> Best Regards,
>>>
>>> Lari Hotari
>>> on behalf of the Pulsar PMC
>>>

Re: [VOTE] PIP-322: Pulsar Rate Limiting Refactoring

2023-12-11 Thread Yike Xiao 
+1 (non-binding)

Regards,
Yike

From: Lari Hotari 
Sent: Monday, December 11, 2023 14:20
To: dev@pulsar.apache.org 
Subject: [VOTE] PIP-322: Pulsar Rate Limiting Refactoring

Dear Pulsar community,

I am starting a vote thread for "PIP-322: Pulsar Rate Limiting Refactoring".

PIP-322 document:
https://jpn01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fapache%2Fpulsar%2Fpull%2F21680=05%7C02%7C%7C76e3617a852742a3186308dbfa114782%7C84df9e7fe9f640afb435%7C1%7C0%7C638378724341438026%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C=L%2BeAfm0tHinRQhAEUNb4e49cGyqdN9qE7ZZ%2FqR6EFX8%3D=0

Draft changes for "PIP-322: Pulsar Rate Limiting Refactoring":
https://jpn01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fapache%2Fpulsar%2Fpull%2F21681=05%7C02%7C%7C76e3617a852742a3186308dbfa114782%7C84df9e7fe9f640afb435%7C1%7C0%7C638378724341594260%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C=%2FMMfb9YuJo9BEjjJavcuIgrMKE%2FTG3FYEP9sZ4BA%2BuE%3D=0

Discussion thread:
https://jpn01.safelinks.protection.outlook.com/?url=https%3A%2F%2Flists.apache.org%2Fthread%2Fxzrp2ypggp1oql437tvmkqgfw2b4ft33=05%7C02%7C%7C76e3617a852742a3186308dbfa114782%7C84df9e7fe9f640afb435%7C1%7C0%7C638378724341594260%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C=FemHfhjKg8ccZB9379y8ZRRczocQxer%2Fcn%2BIhc69IDQ%3D=0

Please review the PIP document and vote!

Thanks,

Lari

Re: [VOTE] Pulsar Release 3.0.2 Candidate 4

2023-11-26 Thread Yike Xiao 
+1 (non-binding)

  *   Checked the signatures and checksums
  *   Built from source
```
Apache Maven 3.8.8 (4c87b05d9aedce574290d1acc98575ed5eb6cd39)
Maven home: /usr/local/maven
Java version: 17.0.5, vendor: Oracle Corporation, runtime: 
/Library/Java/JavaVirtualMachines/jdk-17.0.5.jdk/Contents/Home
Default locale: en_CN, platform encoding: UTF-8
OS name: "mac os x", version: "14.1", arch: "aarch64", family: "mac"
```
  *   Run standalone and checked produce and consume
  *   Run a cluster with three nodes with docker image (pulsar)


From: Yubiao Feng 
Sent: Monday, November 20, 2023 10:24
To: dev@pulsar.apache.org 
Subject: [VOTE] Pulsar Release 3.0.2 Candidate 4

This is the first release candidate for Apache Pulsar version 3.0.4.

It fixes the following issues:
https://jpn01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fapache%2Fpulsar%2Fpulls%3Fq%3Dis%253Apr%2Bis%253Amerged%2Blabel%253Arelease%252F3.0.2%2Blabel%253Acherry-picked%252Fbranch-3.0=05%7C01%7C%7C3adbaf0e4b1348a45db908dbe9700e09%7C84df9e7fe9f640afb435%7C1%7C0%7C638360439699813981%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C=O0t7XQ%2Fyl8E1jqomYW9ObingScQ3j0ynFvpgpmAdWkk%3D=0+

*** 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://jpn01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdist.apache.org%2Frepos%2Fdist%2Fdev%2Fpulsar%2Fpulsar-3.0.2-candidate-4%2F=05%7C01%7C%7C3adbaf0e4b1348a45db908dbe9700e09%7C84df9e7fe9f640afb435%7C1%7C0%7C638360439699970235%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C=CEKQMg7XumWSg9OsK1iHTBNYDqtAFfnXOE52LfPZV8Y%3D=0

SHA-512 checksums:

9bd5b4030de47c10a906d6271731ca7bcfb8801984cdd625789bc0c5047138f0f2eb1aaceaec1c8941e2ccfa639bbb2458496518e87fb29abb9ebc518e2da60d

apache-pulsar-3.0.2-bin.tar.gz

6854d1776de08c9079228a5a5d2f670f92b1b905f0d92c50ee35c5bc9c53be5225626a6d84fc3bbb209b8b12ff3b142685b5c9ea33609e1bb934e9679402e0b8

apache-pulsar-3.0.2-src.tar.gz

Maven staging repo:
https://jpn01.safelinks.protection.outlook.com/?url=https%3A%2F%2Frepository.apache.org%2Fcontent%2Frepositories%2Forgapachepulsar-1249=05%7C01%7C%7C3adbaf0e4b1348a45db908dbe9700e09%7C84df9e7fe9f640afb435%7C1%7C0%7C638360439699970235%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C=oZ44u3rpSGhgdzvrWXlA3XTrLjjGIHiPlf2o9cFRvYE%3D=0

The tag to verify:
v3.0.2-candidate-4 (12c92fed7847965e3bc3769a91c866b2f0ec2e44)
https://jpn01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fapache%2Fpulsar%2Freleases%2Ftag%2Fv3.0.2-candidate-4=05%7C01%7C%7C3adbaf0e4b1348a45db908dbe9700e09%7C84df9e7fe9f640afb435%7C1%7C0%7C638360439699970235%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C=KOuCBWEIvtBkourwAuQJfx7NKFLrWWZVlAVd%2FChDpgk%3D=0

Pulsar's KEYS file containing PGP keys you use to sign the release:
https://jpn01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdist.apache.org%2Frepos%2Fdist%2Fdev%2Fpulsar%2FKEYS=05%7C01%7C%7C3adbaf0e4b1348a45db908dbe9700e09%7C84df9e7fe9f640afb435%7C1%7C0%7C638360439699970235%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C=oX2GoSYu4ZSW997%2BTdJOC%2BJxyfbvMIPalRMAC09OHwU%3D=0

Docker images:

pulsar images:
https://jpn01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fhub.docker.com%2Frepository%2Fdocker%2F9947090%2Fpulsar-all=05%7C01%7C%7C3adbaf0e4b1348a45db908dbe9700e09%7C84df9e7fe9f640afb435%7C1%7C0%7C638360439699970235%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C=XWmZ9Ytz%2BW7Wryc1M6WcLzQMSLoP3YN6ZTallD15IJs%3D=0

pulsar-all images:
https://jpn01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fhub.docker.com%2Frepository%2Fdocker%2F9947090%2Fpulsar=05%7C01%7C%7C3adbaf0e4b1348a45db908dbe9700e09%7C84df9e7fe9f640afb435%7C1%7C0%7C638360439699970235%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C=rmcHgz0Sgi7f6oTcaCA49zgfHNRfdWRxYD99pI2QPTY%3D=0

Please download the source package, and

Re: [VOTE] Pulsar Release 3.0.2 Candidate 4

2023-11-26 Thread Yike Xiao 
Update: Pulsar's KEYS file has relocated here [1]

[1]: https://dist.apache.org/repos/dist/release/pulsar/KEYS

Regards,
Yike

From: Yike Xiao 
Sent: Saturday, November 25, 2023 18:13
To: dev@pulsar.apache.org 
Subject: Re: [VOTE] Pulsar Release 3.0.2 Candidate 4

Hi Yubiao,

I was try verifying the signature of the release, but I noticed that the KEYS 
file page [1] is a 404 page.

```shell
curl 
https://jpn01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdist.apache.org%2Frepos%2Fdist%2Fdev%2Fpulsar%2FKEYS=05%7C01%7C%7C56904597636e4d3644bb08dbed9f229d%7C84df9e7fe9f640afb435%7C1%7C0%7C638365039957640858%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C=yiUjSyOGAkdISWDMW609tUVr3fHN0AeoH3g%2B1mFCd2U%3D=0<https://dist.apache.org/repos/dist/dev/pulsar/KEYS>
 -i
HTTP/1.1 404 Not Found
Date: Sat, 25 Nov 2023 10:11:19 GMT
Server: Apache
Content-Length: 196
Content-Type: text/html; charset=iso-8859-1



404 Not Found

Not Found
The requested URL was not found on this server.

```

[1]: 
https://jpn01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdist.apache.org%2Frepos%2Fdist%2Fdev%2Fpulsar%2FKEYS=05%7C01%7C%7C56904597636e4d3644bb08dbed9f229d%7C84df9e7fe9f640afb435%7C1%7C0%7C638365039957640858%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C=yiUjSyOGAkdISWDMW609tUVr3fHN0AeoH3g%2B1mFCd2U%3D=0<https://dist.apache.org/repos/dist/dev/pulsar/KEYS>

Regards,
Yike

From: Yubiao Feng 
Sent: Monday, November 20, 2023 10:24
To: dev@pulsar.apache.org 
Subject: [VOTE] Pulsar Release 3.0.2 Candidate 4

This is the first release candidate for Apache Pulsar version 3.0.4.

It fixes the following issues:
https://jpn01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fapache%2Fpulsar%2Fpulls%3Fq%3Dis%253Apr%2Bis%253Amerged%2Blabel%253Arelease%252F3.0.2%2Blabel%253Acherry-picked%252Fbranch-3.0=05%7C01%7C%7C56904597636e4d3644bb08dbed9f229d%7C84df9e7fe9f640afb435%7C1%7C0%7C638365039957640858%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C=lQDmuH%2FXe4par5cOr8OOM%2BG52ODA6Pu7elPvOy0W5P8%3D=0+<https://jpn01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fapache%2Fpulsar%2Fpulls%3Fq%3Dis%253Apr%2Bis%253Amerged%2Blabel%253Arelease%252F3.0.2%2Blabel%253Acherry-picked%252Fbranch-3.0=05%7C01%7C%7C56904597636e4d3644bb08dbed9f229d%7C84df9e7fe9f640afb435%7C1%7C0%7C638365039957640858%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C=lQDmuH%2FXe4par5cOr8OOM%2BG52ODA6Pu7elPvOy0W5P8%3D=0><https://github.com/apache/pulsar/pulls?q=is%3Apr+is%3Amerged+label%3Arelease%2F3.0.2+label%3Acherry-picked%2Fbranch-3.0>

*** 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://jpn01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdist.apache.org%2Frepos%2Fdist%2Fdev%2Fpulsar%2Fpulsar-3.0.2-candidate-4%2F=05%7C01%7C%7C56904597636e4d3644bb08dbed9f229d%7C84df9e7fe9f640afb435%7C1%7C0%7C638365039957640858%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C=x%2BrFWUjHL5uzW9nJGO%2FjRRjU7ssN4kttWrNKJspSA%2FA%3D=0<https://jpn01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdist.apache.org%2Frepos%2Fdist%2Fdev%2Fpulsar%2Fpulsar-3.0.2-candidate-4%2F=05%7C01%7C%7C56904597636e4d3644bb08dbed9f229d%7C84df9e7fe9f640afb435%7C1%7C0%7C638365039957640858%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C=x%2BrFWUjHL5uzW9nJGO%2FjRRjU7ssN4kttWrNKJspSA%2FA%3D=0><https://dist.apache.org/repos/dist/dev/pulsar/pulsar-3.0.2-candidate-4/>

SHA-512 checksums:

9bd5b4030de47c10a906d6271731ca7bcfb8801984cdd625789bc0c5047138f0f2eb1aaceaec1c8941e2ccfa639bbb2458496518e87fb29abb9ebc518e2da60d

apache-pulsar-3.0.2-bin.tar.gz

6854d1776de08c9079228a5a5d2f670f92b1b905f0d92c50ee35c5bc9c53be5225626a6d84fc3bbb209b8b12ff3b142685b5c9ea33609e1bb934e9679402e0b8

apache-pulsar-3.0.2-src.tar.gz

Maven staging repo:
https://jpn01.safelinks.protection.outlook.com/?url=https%3A%2F%2Frepository.apache.org%2Fcontent%2Frepositories%2Forgapachepulsar-1249=05%7C01%7C%7C56904597636e4d3644bb08dbed9f229d%7C84df9e7fe9f640afb435%7C1%7C0%7C638365039957640858%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C=owavmHp00L50O7trKUthTYYUcZCr9EtCdnqYQLvHd98%3D=0<https://jpn01.safelinks.protection.outlook.com/?url=https%3A%2F%2Frepository.apache.org%2Fcontent%2Frepositories%2Forgapachepulsar-1249=05%7C0

Re: [VOTE] Pulsar Release 3.0.2 Candidate 4

2023-11-25 Thread Yike Xiao 
Hi Yubiao,

I was try verifying the signature of the release, but I noticed that the KEYS 
file page [1] is a 404 page.

```shell
curl https://dist.apache.org/repos/dist/dev/pulsar/KEYS -i
HTTP/1.1 404 Not Found
Date: Sat, 25 Nov 2023 10:11:19 GMT
Server: Apache
Content-Length: 196
Content-Type: text/html; charset=iso-8859-1



404 Not Found

Not Found
The requested URL was not found on this server.

```

[1]: https://dist.apache.org/repos/dist/dev/pulsar/KEYS

Regards,
Yike

From: Yubiao Feng 
Sent: Monday, November 20, 2023 10:24
To: dev@pulsar.apache.org 
Subject: [VOTE] Pulsar Release 3.0.2 Candidate 4

This is the first release candidate for Apache Pulsar version 3.0.4.

It fixes the following issues:
https://jpn01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fapache%2Fpulsar%2Fpulls%3Fq%3Dis%253Apr%2Bis%253Amerged%2Blabel%253Arelease%252F3.0.2%2Blabel%253Acherry-picked%252Fbranch-3.0=05%7C01%7C%7C3adbaf0e4b1348a45db908dbe9700e09%7C84df9e7fe9f640afb435%7C1%7C0%7C638360439699813981%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C=O0t7XQ%2Fyl8E1jqomYW9ObingScQ3j0ynFvpgpmAdWkk%3D=0+

*** 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://jpn01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdist.apache.org%2Frepos%2Fdist%2Fdev%2Fpulsar%2Fpulsar-3.0.2-candidate-4%2F=05%7C01%7C%7C3adbaf0e4b1348a45db908dbe9700e09%7C84df9e7fe9f640afb435%7C1%7C0%7C638360439699970235%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C=CEKQMg7XumWSg9OsK1iHTBNYDqtAFfnXOE52LfPZV8Y%3D=0

SHA-512 checksums:

9bd5b4030de47c10a906d6271731ca7bcfb8801984cdd625789bc0c5047138f0f2eb1aaceaec1c8941e2ccfa639bbb2458496518e87fb29abb9ebc518e2da60d

apache-pulsar-3.0.2-bin.tar.gz

6854d1776de08c9079228a5a5d2f670f92b1b905f0d92c50ee35c5bc9c53be5225626a6d84fc3bbb209b8b12ff3b142685b5c9ea33609e1bb934e9679402e0b8

apache-pulsar-3.0.2-src.tar.gz

Maven staging repo:
https://jpn01.safelinks.protection.outlook.com/?url=https%3A%2F%2Frepository.apache.org%2Fcontent%2Frepositories%2Forgapachepulsar-1249=05%7C01%7C%7C3adbaf0e4b1348a45db908dbe9700e09%7C84df9e7fe9f640afb435%7C1%7C0%7C638360439699970235%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C=oZ44u3rpSGhgdzvrWXlA3XTrLjjGIHiPlf2o9cFRvYE%3D=0

The tag to verify:
v3.0.2-candidate-4 (12c92fed7847965e3bc3769a91c866b2f0ec2e44)
https://jpn01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fapache%2Fpulsar%2Freleases%2Ftag%2Fv3.0.2-candidate-4=05%7C01%7C%7C3adbaf0e4b1348a45db908dbe9700e09%7C84df9e7fe9f640afb435%7C1%7C0%7C638360439699970235%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C=KOuCBWEIvtBkourwAuQJfx7NKFLrWWZVlAVd%2FChDpgk%3D=0

Pulsar's KEYS file containing PGP keys you use to sign the release:
https://jpn01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdist.apache.org%2Frepos%2Fdist%2Fdev%2Fpulsar%2FKEYS=05%7C01%7C%7C3adbaf0e4b1348a45db908dbe9700e09%7C84df9e7fe9f640afb435%7C1%7C0%7C638360439699970235%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C=oX2GoSYu4ZSW997%2BTdJOC%2BJxyfbvMIPalRMAC09OHwU%3D=0

Docker images:

pulsar images:
https://jpn01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fhub.docker.com%2Frepository%2Fdocker%2F9947090%2Fpulsar-all=05%7C01%7C%7C3adbaf0e4b1348a45db908dbe9700e09%7C84df9e7fe9f640afb435%7C1%7C0%7C638360439699970235%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C=XWmZ9Ytz%2BW7Wryc1M6WcLzQMSLoP3YN6ZTallD15IJs%3D=0

pulsar-all images:
https://jpn01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fhub.docker.com%2Frepository%2Fdocker%2F9947090%2Fpulsar=05%7C01%7C%7C3adbaf0e4b1348a45db908dbe9700e09%7C84df9e7fe9f640afb435%7C1%7C0%7C638360439699970235%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C=rmcHgz0Sgi7f6oTcaCA49zgfHNRfdWRxYD99pI2QPTY%3D=0

Please download the source package, and follow the README to build
and run the Pulsar standalone