[GitHub] [pulsar-dotpulsar] justinwujian commented on issue #107: DotPulsar refers to the MySql.Data package, which will cause the consumer status to become 'Faulted' and eventually fail to consume me
justinwujian commented on issue #107: URL: https://github.com/apache/pulsar-dotpulsar/issues/107#issuecomment-1156194070 > Sure... btw, you were running the code on a non-Windows system, right? My local development environment is Windows, but the environment deployed on the service is Linux. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: dev-unsubscr...@pulsar.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
Re: [VOTE] Pulsar Release 2.10.1 Candidate 1
+1 (non-binding) * run docker image * test protocol handlers * test proxy extensions Thanks Christophe Le lun. 13 juin 2022 à 13:43, PengHui Li a écrit : > This is the first release candidate for Apache Pulsar 2.10.1 > > It fixes the following issues: > > https://github.com/apache/pulsar/pulls?q=is%3Amerged+is%3Apr+label%3Arelease%2F2.10.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-2.10.1-candidate-1/ > > SHA-512 checksums: > > > 87045067cf123574b2b7d578f020efd177b0d9ff12a75d9f738e135cde35a034000c03e21cc8a264a6ef9e2b1df2c4493ffa3b9170b0f368d7424f1160df38cb > ./apache-pulsar-2.10.1-bin.tar.gz > > > 19c078f65b9105728adda3926a9a1527d6498f0e2337d37497a6d965a38acf94e217e58939bc5b0a8b8166511ae9ee176ee3d0c764d4777e285b7bcaeb2731e1 > ./apache-pulsar-2.10.1-src.tar.gz > > Maven staging repo: > https://repository.apache.org/content/repositories/orgapachepulsar-1156/ > > The tag to be voted upon: > v2.10.1-candidate-1 (0702b51ce09cc99044f4110e6bf98e82a0e86283) > https://github.com/apache/pulsar/releases/tag/v2.10.1-candidate-1 > > Pulsar's KEYS file containing PGP keys we use to sign the release: > https://dist.apache.org/repos/dist/dev/pulsar/KEYS > > Docker images: > > > https://hub.docker.com/layers/233293315/lph890127/pulsar/2.10.1-rc1/images/sha256-4a952b3c662b94247ffc4ff17be16ef176c293baaf346db13a095970f43adfd6?context=repo > > > https://hub.docker.com/layers/233303469/lph890127/pulsar-all/2.10.1-rc1/images/sha256-ac8180f4ba796291e961581821a1318437e49b0fa684597f5b67265a502822ee?context=repo > > Please download the source package, and follow the Release Candidate > Validation[1] > to validate the release > > [1] https://github.com/apache/pulsar/wiki/Release-Candidate-Validation > > Thanks, > Penghui >
[GitHub] [pulsar-dotpulsar] blankensteiner commented on issue #107: DotPulsar refers to the MySql.Data package, which will cause the consumer status to become 'Faulted' and eventually fail to consume
blankensteiner commented on issue #107: URL: https://github.com/apache/pulsar-dotpulsar/issues/107#issuecomment-1156398060 Roger. With the release of version 2.4.0, I am closing this issue. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: dev-unsubscr...@pulsar.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [pulsar-dotpulsar] blankensteiner closed issue #107: DotPulsar refers to the MySql.Data package, which will cause the consumer status to become 'Faulted' and eventually fail to consume messag
blankensteiner closed issue #107: DotPulsar refers to the MySql.Data package, which will cause the consumer status to become 'Faulted' and eventually fail to consume messages. URL: https://github.com/apache/pulsar-dotpulsar/issues/107 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: dev-unsubscr...@pulsar.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
Mark delete rate limiter bug?
Hi, In the Managed Cursor implementation, I saw that the position state is persisted in the ledger whenever a user calls acknowledge, be it individual or cumulative. For performance reasons there is a rate limiter, defaulting to 1 persist action per second. The bug: 17:00:00.003 - user ack a single message --> state it written to ledger 17:00:00.004 - 17:00:00.400 - use acks a single message 100 times. nothing happens after that on that subscription. 18:00 - machine crashed. You "lost" the state hence 100 messages have to be redelivered. I was wondering if it makes sense to add a timeout - say 10sec. If nothing happens to the subscription, flush the state after 10sec if it's dirty. WDYT?
Major problem
Hi, (perhaps this is a dev@ issue more than a users@ issue) I have had a Pulsar system running for ~5 months and have had no problems. Today I updated my application that uses Pulsar, and everything stopped working. I naturally assumed that the problem was in my application. And after a lot of debugging I realized that it was Pulsar not delivering messages. "Maybe ran out of memory, let's restart. Oh well, why not upgrade to new version at the same time." And that failed, I got this "IllegalAccessError" and I thought, that the new version 2.10.0 required something special/new that I have not investigated, so go back to 2.9.1 and I still had the exception (see below). And I now think that this was the problem all the while...but how? No idea. Any pointers to what can cause this in 2.9.1 and/or 2.10.0 is most welcome. BTW, running Java 11 on Debian 11. Thanks Niclas java.lang.IllegalAccessError: Update to non-static final field org.apache.pulsar.policies.data.loadbalancer.ResourceUsage.usage attempted from a different class (org.apache.pulsar.broker.loadbalance.impl.LoadManagerShared) than the field's declaring class at org.apache.pulsar.broker.loadbalance.impl.LoadManagerShared.getSystemResourceUsage(LoadManagerShared.java:220) ~[org.apache.pulsar-pulsar-broker-2.9.1.jar:2.9.1] at org.apache.pulsar.broker.loadbalance.impl.ModularLoadManagerImpl.updateLocalBrokerData(ModularLoadManagerImpl.java:915) ~[org.apache.pulsar-pulsar-broker-2.9.1.jar:2.9.1] at org.apache.pulsar.broker.loadbalance.impl.ModularLoadManagerImpl.start(ModularLoadManagerImpl.java:876) ~[org.apache.pulsar-pulsar-broker-2.9.1.jar:2.9.1] at org.apache.pulsar.broker.loadbalance.impl.ModularLoadManagerWrapper.start(ModularLoadManagerWrapper.java:102) ~[org.apache.pulsar-pulsar-broker-2.9.1.jar:2.9.1] at org.apache.pulsar.broker.PulsarService.startLoadManagementService(PulsarService.java:1022) ~[org.apache.pulsar-pulsar-broker-2.9.1.jar:2.9.1] at org.apache.pulsar.broker.PulsarService.start(PulsarService.java:737) ~[org.apache.pulsar-pulsar-broker-2.9.1.jar:2.9.1] at org.apache.pulsar.PulsarBrokerStarter$BrokerStarter.start(PulsarBrokerStarter.java:273) ~[org.apache.pulsar-pulsar-broker-2.9.1.jar:2.9.1] at org.apache.pulsar.PulsarBrokerStarter.main(PulsarBrokerStarter.java:350) [org.apache.pulsar-pulsar-broker-2.9.1.jar:2.9.1]
Re: Mark delete rate limiter bug?
Entries will filtered by ManagedCursorImpl#filterReadEntries Both of individual_ack and cumulative_ack will update ManagedCursorImpl#individualDeletedMessages, messages will be filtered which has already acked. Thanks, Tao Jiuming > 2022年6月15日 下午11:45，Asaf Mesika 写道： > > Hi, > > In the Managed Cursor implementation, I saw that the position state is > persisted in the ledger whenever a user calls acknowledge, be it individual > or cumulative. > > For performance reasons there is a rate limiter, defaulting to 1 persist > action per second. > > The bug: > 17:00:00.003 - user ack a single message --> state it written to ledger > 17:00:00.004 - 17:00:00.400 - use acks a single message 100 times. > nothing happens after that on that subscription. > > 18:00 - machine crashed. > You "lost" the state hence 100 messages have to be redelivered. > > I was wondering if it makes sense to add a timeout - say 10sec. If nothing > happens to the subscription, flush the state after 10sec if it's dirty. > > WDYT?
Re: Major problem
Hi Niclas, can you provide the output of `pulsar-admin topics stats $TOPIC` -- Matteo Merli On Wed, Jun 15, 2022 at 9:18 AM Niclas Hedhman wrote: > > Hi, > (perhaps this is a dev@ issue more than a users@ issue) > > I have had a Pulsar system running for ~5 months and have had no > problems. > > Today I updated my application that uses Pulsar, and everything stopped > working. I naturally assumed that the problem was in my application. And > after a lot of debugging I realized that it was Pulsar not delivering > messages. > > "Maybe ran out of memory, let's restart. Oh well, why not upgrade to new > version at the same time." > > And that failed, I got this "IllegalAccessError" and I thought, that the > new version 2.10.0 required something special/new that I have not > investigated, so go back to 2.9.1 and I still had the exception (see > below). And I now think that this was the problem all the while...but > how? No idea. > > Any pointers to what can cause this in 2.9.1 and/or 2.10.0 is most > welcome. > > BTW, running Java 11 on Debian 11. > > Thanks > Niclas > > > java.lang.IllegalAccessError: Update to non-static final field > org.apache.pulsar.policies.data.loadbalancer.ResourceUsage.usage > attempted from a different class > (org.apache.pulsar.broker.loadbalance.impl.LoadManagerShared) than the > field's declaring class > at > org.apache.pulsar.broker.loadbalance.impl.LoadManagerShared.getSystemResourceUsage(LoadManagerShared.java:220) > ~[org.apache.pulsar-pulsar-broker-2.9.1.jar:2.9.1] > at > org.apache.pulsar.broker.loadbalance.impl.ModularLoadManagerImpl.updateLocalBrokerData(ModularLoadManagerImpl.java:915) > ~[org.apache.pulsar-pulsar-broker-2.9.1.jar:2.9.1] > at > org.apache.pulsar.broker.loadbalance.impl.ModularLoadManagerImpl.start(ModularLoadManagerImpl.java:876) > ~[org.apache.pulsar-pulsar-broker-2.9.1.jar:2.9.1] > at > org.apache.pulsar.broker.loadbalance.impl.ModularLoadManagerWrapper.start(ModularLoadManagerWrapper.java:102) > ~[org.apache.pulsar-pulsar-broker-2.9.1.jar:2.9.1] > at > org.apache.pulsar.broker.PulsarService.startLoadManagementService(PulsarService.java:1022) > ~[org.apache.pulsar-pulsar-broker-2.9.1.jar:2.9.1] > at > org.apache.pulsar.broker.PulsarService.start(PulsarService.java:737) > ~[org.apache.pulsar-pulsar-broker-2.9.1.jar:2.9.1] > at > org.apache.pulsar.PulsarBrokerStarter$BrokerStarter.start(PulsarBrokerStarter.java:273) > ~[org.apache.pulsar-pulsar-broker-2.9.1.jar:2.9.1] > at > org.apache.pulsar.PulsarBrokerStarter.main(PulsarBrokerStarter.java:350) > [org.apache.pulsar-pulsar-broker-2.9.1.jar:2.9.1]
Re: Mark delete rate limiter bug?
There is a background flush process that was added for this precise reason. In broker.conf # How frequently to flush the cursor positions that were accumulated due to rate limiting. (seconds). # Default is 60 seconds managedLedgerCursorPositionFlushSeconds=60 -- Matteo Merli On Wed, Jun 15, 2022 at 8:45 AM Asaf Mesika wrote: > > Hi, > > In the Managed Cursor implementation, I saw that the position state is > persisted in the ledger whenever a user calls acknowledge, be it individual > or cumulative. > > For performance reasons there is a rate limiter, defaulting to 1 persist > action per second. > > The bug: > 17:00:00.003 - user ack a single message --> state it written to ledger > 17:00:00.004 - 17:00:00.400 - use acks a single message 100 times. > nothing happens after that on that subscription. > > 18:00 - machine crashed. > You "lost" the state hence 100 messages have to be redelivered. > > I was wondering if it makes sense to add a timeout - say 10sec. If nothing > happens to the subscription, flush the state after 10sec if it's dirty. > > WDYT?
Re: Major problem
On 2022-06-15 20:03, Matteo Merli wrote: Hi Niclas, can you provide the output of `pulsar-admin topics stats $TOPIC` Answer on users@ brought me back to a stable situation and issue is resolved. Thanks Niclas
[GitHub] [pulsar-client-node] k2la commented on pull request #81: Support seting topic schema when creating producers/consumers
k2la commented on PR #81: URL: https://github.com/apache/pulsar-client-node/pull/81#issuecomment-1157131659 @lcartercondon Could you please rebase to the master branch? -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: dev-unsubscr...@pulsar.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [pulsar-site] urfreespace merged pull request #118: fix: optimize crowdin build flow
urfreespace merged PR #118: URL: https://github.com/apache/pulsar-site/pull/118 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: dev-unsubscr...@pulsar.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
Re: [VOTE] Pulsar Release 2.10.1 Candidate 1
+1 (binding) - Check signatures/checksums - Check the license headers - build sources - Validate Connectors - Validate Pub/Sub and Java Functions - Validate Stateful Functions Regards, Hiroyuki From: PengHui Li Sent: Monday, June 13, 2022 20:42 To: Dev Subject: [VOTE] Pulsar Release 2.10.1 Candidate 1 This is the first release candidate for Apache Pulsar 2.10.1 It fixes the following issues: https://github.com/apache/pulsar/pulls?q=is%3Amerged+is%3Apr+label%3Arelease%2F2.10.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://jpn01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdist.apache.org%2Frepos%2Fdist%2Fdev%2Fpulsar%2Fpulsar-2.10.1-candidate-1%2F&data=05%7C01%7Chsakai%40yahoo-corp.jp%7C83a3b2e2056b44cc7cb508da4d31e7fc%7Ca208d369cd4e4f87b11998eaf31df2c3%7C1%7C0%7C637907173984777015%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=U1qRnd%2BzvI%2BnjDSlFUIESdHLfXoizi7aCs0IS6opZ%2FY%3D&reserved=0 SHA-512 checksums: 87045067cf123574b2b7d578f020efd177b0d9ff12a75d9f738e135cde35a034000c03e21cc8a264a6ef9e2b1df2c4493ffa3b9170b0f368d7424f1160df38cb ./apache-pulsar-2.10.1-bin.tar.gz 19c078f65b9105728adda3926a9a1527d6498f0e2337d37497a6d965a38acf94e217e58939bc5b0a8b8166511ae9ee176ee3d0c764d4777e285b7bcaeb2731e1 ./apache-pulsar-2.10.1-src.tar.gz Maven staging repo: https://jpn01.safelinks.protection.outlook.com/?url=https%3A%2F%2Frepository.apache.org%2Fcontent%2Frepositories%2Forgapachepulsar-1156%2F&data=05%7C01%7Chsakai%40yahoo-corp.jp%7C83a3b2e2056b44cc7cb508da4d31e7fc%7Ca208d369cd4e4f87b11998eaf31df2c3%7C1%7C0%7C637907173984777015%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=%2BZoXgziUY0T9MasJqc1cgQM%2BYx2EepebKBqfIwBQmE0%3D&reserved=0 The tag to be voted upon: v2.10.1-candidate-1 (0702b51ce09cc99044f4110e6bf98e82a0e86283) https://github.com/apache/pulsar/releases/tag/v2.10.1-candidate-1 Pulsar's KEYS file containing PGP keys we use to sign the release: https://jpn01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdist.apache.org%2Frepos%2Fdist%2Fdev%2Fpulsar%2FKEYS&data=05%7C01%7Chsakai%40yahoo-corp.jp%7C83a3b2e2056b44cc7cb508da4d31e7fc%7Ca208d369cd4e4f87b11998eaf31df2c3%7C1%7C0%7C637907173984777015%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=8d8NPmSIeP4rLa4UYkyuxv2dltYLcda2K0T5IloVTRE%3D&reserved=0 Docker images: https://jpn01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fhub.docker.com%2Flayers%2F233293315%2Flph890127%2Fpulsar%2F2.10.1-rc1%2Fimages%2Fsha256-4a952b3c662b94247ffc4ff17be16ef176c293baaf346db13a095970f43adfd6%3Fcontext%3Drepo&data=05%7C01%7Chsakai%40yahoo-corp.jp%7C83a3b2e2056b44cc7cb508da4d31e7fc%7Ca208d369cd4e4f87b11998eaf31df2c3%7C1%7C0%7C637907173984777015%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=fVo1fzvVuN3Uwvf7407TzvcEO8FNY0zojDnHuoAKzyw%3D&reserved=0 https://jpn01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fhub.docker.com%2Flayers%2F233303469%2Flph890127%2Fpulsar-all%2F2.10.1-rc1%2Fimages%2Fsha256-ac8180f4ba796291e961581821a1318437e49b0fa684597f5b67265a502822ee%3Fcontext%3Drepo&data=05%7C01%7Chsakai%40yahoo-corp.jp%7C83a3b2e2056b44cc7cb508da4d31e7fc%7Ca208d369cd4e4f87b11998eaf31df2c3%7C1%7C0%7C637907173984777015%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=lhCu%2FidFqIeOU74ZkfEDjoQckQIt%2FtDA37poaz4%2B5Bs%3D&reserved=0 Please download the source package, and follow the Release Candidate Validation[1] to validate the release [1] https://github.com/apache/pulsar/wiki/Release-Candidate-Validation Thanks, Penghui
[DISCUSS] Reject partitioned topic creation when the topic name contains the `partition` keyword.
Hello, everyone.
I want to start a discussion about *Reject partitioned topic creation when
the topic name contains the `-partition-` keyword.*
Please feel free to express your opinion.
*Background*
We first found this problem two months ago. When the user sets the
*allowAutoTopicCreation* policy as below:
> {
> allowAutoTopicCreation: true,
> allowAutoTopicCreationType: "partitioned",
> defaultNumPartitions: 1
> }
This policy will make brokers automatically create the partitioned topic
when the topic does not exist. But we don't check if users use topic
names like "persistent://public/default/-partition-YYY".
In our logic, this topic will pass the automatically created
partition topic metadata check. We will make the partitioned metadata like
this:
Z-NODE:
paritioned-topics/public/defualt/persistent/-partition-YYY
{"partitions": 1}
The things here stand at the broker's side. Everything looks like we
expect. Even the topic name includes "-partition-" keywords.
And then, we continue the process. The Pulsar Client(Java) will get this
metadata and then try to create separate topics with `-partition-{index}`.
But there have small trick things,
The client try to invoke
`TopicName.get(topicName).getPartition(partitionIndex).toString();` method
to get paritioned topic name. however, we have `partition` keywords check
in the method `TopicName.get(topicName).getPartition(partitionIndex)`[1].
If the topic name includes `-partition-` keywords, it will return the
original topic name directly. So, The client will use this topic name to
create the consumer.
Here we go. Let's summarize:
1. We make the topic `persistent://public/default/-partition-YYY` a
partitioned topic.
2. The client tries to create the topic using
`persistent://public/default/-partition-YYY` not
`persistent://public/default/-partition-YYY-partition-0`
In this condition, we have s problem for users. If they want to delete this
topic, awkward things happen.
- If the users want to use delete-partition-topic admin API, The broker
will return the error "Partitioned Topic Name should not contain
'-partition-'".
- If the users want to use delete-topic admin API, The broker will delete
this topic, but the broker doesn't remove the partition topic metadata.
So, maybe there have many methods to solve this problem. It looks like
removing the `partition` keywords check for the `delete-partition` admin
API. But it seems not to make sense. So, we chose to reject this topic
creation directly and push a PR for it[2].
Things are not over yet. In the past few days. After discussing with
Penghui Li and Baodi Shi. We found another problem that will affect the
dead letter queue(DLQ) If we reject topic creation directly. So, I push a
PR[3] to revert it soon. And then draft this discussion.
Please remember the phenomenon described above and take it into DLQ with
the partitioned topic.
When we want to create a Share model subscription, for example, that topic
name is "persistent://public/default/test-topic". And we enabled DLQ.
The client will try to create a partitioned topic that looks like
`persistent://public/default/test-topic-partition-0`. And then, when we
need to use DLQ, the client will use a new producer that topic name follows
the DLQ default naming format:
topicname-subscriptionname-DLQ =>
> persistent://public/default/test-topic-partition-0-test-sub-DLQ
With the allowAutoTopicCreation policy, we mentioned before. the topic
`persistent://public/default/test-topic-partition-0-test-sub-DLQ` will
create the partitioned topic metadata.
Z-NODE:
paritioned-topics/public/defualt/persistent/test-topic-partition-0-test-sub-DLQ
{"partitions": 1}
And the client will also do the same things we mentioned above.
So, there have some problems:
- The DLQ topic is partitioned, but the client doesn't use
`persistent://public/default/test-topic-partition-0-test-sub-DLQ-partition-0`
to create this topic.
- If the auto-creation policy `defaultNumPartitions` > 1, and the
subscription type is `Exclusive`. the error will occur. Because the
consumer already exists. Please check this logic.[4]
- If the auto-creation policy `defaultNumPartitions` > 1, and the
subscription type is `Shared`. we will create many consumers/producers to
the same topic. The number is the number of partitions.[4]
- Because this DLQ is not partitioned topic name in the broker and it has
partitioned topic metadata. So, If we have some checks in the broker, we
will get errors. Just like the replicator.[5]
*Problem*
After background explanation, we've got some problems to want to discuss:
1. Should we reject the partitioned topic metadata creation when the topic
name contains the `-partition-` keywords?
2. If you want to reject the partitioned topic metadata creation, how can
you handle DLQ?
3. If we don't let the client do the `-partition-` keyword check in
`TopicName.get(topicName).getPartition(partitionIndex).toString();`, is the
DLQ of the partition what we e
RE: [VOTE] Pulsar Release 2.10.1 Candidate 1
+1 (non-binding) - verified checksums and signatures - build from source - verified pub/sub and java functions - verified stateful functions Thanks, Shusuke Tsuda -Original Message- From: PengHui Li Sent: Monday, June 13, 2022 8:43 PM To: Dev Subject: [VOTE] Pulsar Release 2.10.1 Candidate 1 This is the first release candidate for Apache Pulsar 2.10.1 It fixes the following issues: https://github.com/apache/pulsar/pulls?q=is%3Amerged+is%3Apr+label%3Arelease%2F2.10.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://jpn01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdist.apache.org%2Frepos%2Fdist%2Fdev%2Fpulsar%2Fpulsar-2.10.1-candidate-1%2F&data=05%7C01%7Cshustsud%40yahoo-corp.jp%7C5ddcaa29fc224b6f09e608da4d31e6a8%7Ca208d369cd4e4f87b11998eaf31df2c3%7C1%7C0%7C637907173959452192%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=MlMhzU4P7GzFXx%2BNQ9DYh09Z4%2BJWzqWe%2BXbhO5pOGBo%3D&reserved=0 SHA-512 checksums: 87045067cf123574b2b7d578f020efd177b0d9ff12a75d9f738e135cde35a034000c03e21cc8a264a6ef9e2b1df2c4493ffa3b9170b0f368d7424f1160df38cb ./apache-pulsar-2.10.1-bin.tar.gz 19c078f65b9105728adda3926a9a1527d6498f0e2337d37497a6d965a38acf94e217e58939bc5b0a8b8166511ae9ee176ee3d0c764d4777e285b7bcaeb2731e1 ./apache-pulsar-2.10.1-src.tar.gz Maven staging repo: https://jpn01.safelinks.protection.outlook.com/?url=https%3A%2F%2Frepository.apache.org%2Fcontent%2Frepositories%2Forgapachepulsar-1156%2F&data=05%7C01%7Cshustsud%40yahoo-corp.jp%7C5ddcaa29fc224b6f09e608da4d31e6a8%7Ca208d369cd4e4f87b11998eaf31df2c3%7C1%7C0%7C637907173959452192%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=7881wtcvkkKTYpcJUDaaP1kD7L25hmJyWYnAsa7H1iw%3D&reserved=0 The tag to be voted upon: v2.10.1-candidate-1 (0702b51ce09cc99044f4110e6bf98e82a0e86283) https://github.com/apache/pulsar/releases/tag/v2.10.1-candidate-1 Pulsar's KEYS file containing PGP keys we use to sign the release: https://jpn01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdist.apache.org%2Frepos%2Fdist%2Fdev%2Fpulsar%2FKEYS&data=05%7C01%7Cshustsud%40yahoo-corp.jp%7C5ddcaa29fc224b6f09e608da4d31e6a8%7Ca208d369cd4e4f87b11998eaf31df2c3%7C1%7C0%7C637907173959452192%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=PTTqkrOKzXpW9I14aQRcSHl1swE8tCua%2Bo%2BTIkP%2F8jM%3D&reserved=0 Docker images: https://jpn01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fhub.docker.com%2Flayers%2F233293315%2Flph890127%2Fpulsar%2F2.10.1-rc1%2Fimages%2Fsha256-4a952b3c662b94247ffc4ff17be16ef176c293baaf346db13a095970f43adfd6%3Fcontext%3Drepo&data=05%7C01%7Cshustsud%40yahoo-corp.jp%7C5ddcaa29fc224b6f09e608da4d31e6a8%7Ca208d369cd4e4f87b11998eaf31df2c3%7C1%7C0%7C637907173959452192%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=Td0nWB8YQIgPrC0252vtyyEqokUQLCTZ9MYJbIxuhQU%3D&reserved=0 https://jpn01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fhub.docker.com%2Flayers%2F233303469%2Flph890127%2Fpulsar-all%2F2.10.1-rc1%2Fimages%2Fsha256-ac8180f4ba796291e961581821a1318437e49b0fa684597f5b67265a502822ee%3Fcontext%3Drepo&data=05%7C01%7Cshustsud%40yahoo-corp.jp%7C5ddcaa29fc224b6f09e608da4d31e6a8%7Ca208d369cd4e4f87b11998eaf31df2c3%7C1%7C0%7C637907173959452192%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=7kiKT%2BK7T%2BkJSTSAER%2BF8aFyLTXHKrjEMa%2BP0AOxiSk%3D&reserved=0 Please download the source package, and follow the Release Candidate Validation[1] to validate the release [1] https://github.com/apache/pulsar/wiki/Release-Candidate-Validation Thanks, Penghui
