lhotari closed issue #164:
URL: https://github.com/apache/pulsar-helm-chart/issues/164
--
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-unsubsc
lhotari commented on issue #164:
URL:
https://github.com/apache/pulsar-helm-chart/issues/164#issuecomment-1042660744
The helm chart version is independent from Pulsar's version. There's a
separate PR #200 that would make image tag match the appVersion by default.
--
This is an automated
lhotari commented on pull request #190:
URL:
https://github.com/apache/pulsar-helm-chart/pull/190#issuecomment-1042658696
Rebased on latest master branch changes.
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
U
+1 (binding)
- Check signatures/checksums
- Check the license headers
- build sources
- Validate Pub/Sub and Java Functions
- Validate Stateful Functions
Regards,
Hiroyuki
From: Ran Gao
Sent: Thursday, February 17, 2022 03:26
To: dev@pulsar.apache.org
Subj
I forgot to close this one.
Closing now with 5 +1s votes;
* Matteo
* PengHui
* Hang
* Enrico
* Sijie
--
Matteo Merli
On Mon, Jan 24, 2022 at 11:47 PM Enrico Olivelli wrote:
>
> What's the status of this PIP ?
>
> We have a pending PR,
> we can commit it as soon as the VOTE thread is offi
Congratulations
Haiting Jiang 于2022年2月16日周三 22:12写道：
> Congrats!
>
> Thanks,
> Haiting
>
> On 2022/02/16 10:51:52 Guangning E wrote:
> > Configurations!
> >
> >
> > Thanks,
> > Guangning
> >
> > Jia Zhai 于2022年2月16日周三 15:40写道：
> >
> > > Congratulations
> > >
> > >
> > > On Wed, Feb 16, 2022 at
+1 (non-binding)
- checked checksum and signature
- run produce and consume
Thanks,
Shusuke Tsuda
-Original Message-
From: Chris Kellogg
Sent: Thursday, February 17, 2022 12:53 PM
To: dev@pulsar.apache.org
Subject: Re: [VOTE] Pulsar Client Go Release 0.8.0 Candidate 1
+1
Checked the
On Wed, Feb 16, 2022 at 9:55 PM Michael Marshall wrote:
> Given that our community members who focus on testing are otherwise
> about to prepare for a quick 3 day round of testing, I don't believe
> they would object to a last minute change that gives them more time
> for testing. In your view, wh
> Ideally, people shouldn't be aware of partitioned vs non-partitioned.
I'm not sure I agree that people shouldn't be aware of these details
considering the two types of topics provide different guarantees
regarding ordering. Enrico's request is essentially to have a way to
fail fast when a topic
Chart history added to
https://pulsar.apache.org/charts/index.yaml
With commit
https://github.com/apache/pulsar-site/commit/f45d4f89c13fe25802f374f8d5c015334690c37f
Please append something to the url if you get the old version when
previewing the chart index in the browser, for example
https://pul
Thanks for creating the branch, Penghui.
> Yes, but I think that the code freeze is only meaningful if it’s
> communicated in advance.
Given that our community members who focus on testing are otherwise
about to prepare for a quick 3 day round of testing, I don't believe
they would object to a la
The chart index is now published,
https://pulsar.apache.org/charts/index.yaml .
However, the history isn't there. I'll fix that with a manual commit.
-Lari
On Thu, Feb 17, 2022 at 7:31 AM Guangning E wrote:
> yes, this pr for fixed it =>
> https://github.com/apache/pulsar-helm-chart/pull/231
>
lhotari commented on a change in pull request #223:
URL: https://github.com/apache/pulsar-helm-chart/pull/223#discussion_r808695020
##
File path: charts/pulsar/templates/zookeeper-statefulset.yaml
##
@@ -151,7 +157,9 @@ spec:
command:
- timeout
lhotari merged pull request #223:
URL: https://github.com/apache/pulsar-helm-chart/pull/223
--
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-un
lhotari merged pull request #232:
URL: https://github.com/apache/pulsar-helm-chart/pull/232
--
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-un
tuteng commented on pull request #231:
URL:
https://github.com/apache/pulsar-helm-chart/pull/231#issuecomment-1042593947
It is duplicated with pr #232 and I will close it
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and
tuteng closed pull request #231:
URL: https://github.com/apache/pulsar-helm-chart/pull/231
--
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-uns
urfreespace commented on a change in pull request #231:
URL: https://github.com/apache/pulsar-helm-chart/pull/231#discussion_r808690607
##
File path: .ci/release.sh
##
@@ -71,9 +71,9 @@ function release::git_setup() {
function release::publish_charts() {
release::git_se
urfreespace commented on a change in pull request #231:
URL: https://github.com/apache/pulsar-helm-chart/pull/231#discussion_r808689895
##
File path: .ci/release.sh
##
@@ -71,9 +71,9 @@ function release::git_setup() {
function release::publish_charts() {
release::git_se
lhotari opened a new pull request #232:
URL: https://github.com/apache/pulsar-helm-chart/pull/232
- also use shallow cloning
--
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.
yes, this pr for fixed it =>
https://github.com/apache/pulsar-helm-chart/pull/231
Dave Fisher 于2022年2月17日周四 13:21写道：
> Change L74 to pulsar-site
>
> Change L76 to asf-site-next
>
> All the best,
> Dave
>
> Sent from my iPhone
>
> > On Feb 16, 2022, at 9:02 PM, Sijie Guo wrote:
> >
> > Yes, we
Change L74 to pulsar-site
Change L76 to asf-site-next
All the best,
Dave
Sent from my iPhone
> On Feb 16, 2022, at 9:02 PM, Sijie Guo wrote:
>
> Yes, we just need to change the CI process in `pulsar-helm-chart` to
> publish the index.yaml file to the new website.
>
> See
> https://github.co
tuteng opened a new pull request #231:
URL: https://github.com/apache/pulsar-helm-chart/pull/231
Fixes #
### Motivation
This update fixes an issue with the site release that caused the helm chart
to no longer be used.
Exception:
```
...Unable to get an update fr
Yes, we just need to change the CI process in `pulsar-helm-chart` to
publish the index.yaml file to the new website.
See
https://github.com/apache/pulsar-helm-chart/blob/master/.ci/release.sh#L72
On Wed, Feb 16, 2022 at 8:55 PM Guangning E wrote:
> That seems to be because the new site switch t
We can revert the PRs that switched over if necessary and follow with more
testing.
It’s a trade off.
All the best,
Dave
Sent from my iPhone
> On Feb 16, 2022, at 8:54 PM, Sijie Guo wrote:
>
> Hi everyone,
>
> Just want to let everyone know that the Pulsar Helm Charts repo is
> temporarily
That seems to be because the new site switch today is causing this
exception, we should update the helm chart ci to fix this issue, will take
a look at it later
Thanks,
Guangning
Sijie Guo 于2022年2月17日周四 12:52写道：
> I send a notice to users@ mailing list and #general channel about the
> situation
Hi everyone,
Just want to let everyone know that the Pulsar Helm Charts repo is
temporarily down due to the new Pulsar website push. The
`charts/index.yaml` was not added to the new Pulsar site. So if you are
using the helm command to pull the charts, it will fail. A bunch of the
committers is loo
I send a notice to users@ mailing list and #general channel about the
situation.
- Sijie
On Wed, Feb 16, 2022 at 8:46 PM Sijie Guo wrote:
> Hi all,
>
> I think the new website push has broken the Pulsar Helm Chart repo.
>
> We might need to take a look at how to fix it.
>
> - Sijie
>
Thanks for pointing that out, Penghui. I can confirm that my KEY is not signed.
While it's not the same as in person verification, I'll note that
since becoming a committer I have signed all of my git commits with
the same gpg key used to sign these release artifacts. At the very
least, we can be
Hi all,
I think the new website push has broken the Pulsar Helm Chart repo.
We might need to take a look at how to fix it.
- Sijie
Thanks, Michael, looking forward to future collaboration.
Best,
Penghui
On Thu, Feb 17, 2022 at 12:37 PM Michael Marshall
wrote:
> Thanks for your reply, Penghui. I saw your note on that thread but
> didn't realize it affected 2.8.3.
>
> I absolutely did not mean to imply that you don't want t
Hi Yu,
Thank you and all the other contributors for all the great work! Well done.
- Sijie
On Wed, Feb 16, 2022 at 8:04 PM Yu wrote:
> Thanks for your quick feedback, Penghui and Dianjin.
>
> As mentioned in the last email, "*...**there are some known issues (eg.
> localized pages and some CLI
Thanks for your reply, Penghui. I saw your note on that thread but
didn't realize it affected 2.8.3.
I absolutely did not mean to imply that you don't want to share here.
I appreciate your many contributions to the community and the mailing
list, and I look forward to future collaboration.
Thanks
Thanks for your quick feedback, Penghui and Dianjin.
As mentioned in the last email, "*...**there are some known issues (eg.
localized pages and some CLI pages are not available). We're fixing them*
*...* "
We'll keep you updated once we resolve them.
On Thu, Feb 17, 2022 at 11:52 AM Dianjin Wan
+1
Checked the signatures, complied and ran the pular perf tool (produce
and consume) against a standalone cluster.
On Wed, Feb 16, 2022 at 5:29 PM PengHui Li wrote:
>
> +1
>
> - Checked the signatures
> - Run produce and consume on a standalone
>
> Penghui
>
> On Thu, Feb 17, 2022 at 12:45 AM M
Great work!
Any plans for multi-language translation support? There were some languages
supported, such as Chinese, Japanese, French and more, but now cannot find
the button in the new website.
Best,
Dianjin Wang
On Thu, Feb 17, 2022 at 11:15 AM Yu wrote:
> Hi Pulsarers,
>
> As you may notice
I just go through the new website,
looks like the CLI's document always return code 404
I have created an issue for tracking the problem
https://github.com/apache/pulsar/issues/14332
Thanks,
Penghui
On Thu, Feb 17, 2022 at 11:32 AM PengHui Li wrote:
> Great news!
>
> Thanks for the great work
Great news!
Thanks for the great work @Yu, @@urfreespace, @dave2wave.
Penghui
On Thu, Feb 17, 2022 at 11:15 AM Yu wrote:
> Hi Pulsarers,
>
> As you may notice, the new Pulsar website goes live!
> https://pulsar.apache.org/
>
> We hope you enjoy the new feature and the fresh appearance!
>
> CHA
Hi Pulsarers,
As you may notice, the new Pulsar website goes live!
https://pulsar.apache.org/
We hope you enjoy the new feature and the fresh appearance!
CHANGE: documentation main page URL is changed from
https://pulsar.apache.org/docs/en/next/standalone/ to
https://pulsar.apache.org/docs/next/
Thanks for the explanation Dave.
Best,
Penghui
On Thu, Feb 17, 2022 at 10:37 AM Dave Fisher wrote:
> While it’s preferred that KEYS are signed it’s not required. The last
> Apache key signing party was at Apachecon Las Vegas in 2019. Here’s looking
> forward to the next one. Bring your governme
Hi Lari,
Thanks for raising a proposal and starting the discussion thread here.
Increasing the thread does not solve the underlying problem.
but also brings additional resource consumption.
Thanks, Matteo provided a great explanation,
and, I totally agree with his explanation.
What should we try
While it’s preferred that KEYS are signed it’s not required. The last Apache
key signing party was at Apachecon Las Vegas in 2019. Here’s looking forward to
the next one. Bring your government ids.
Regards,
Dave
Sent from my iPhone
> On Feb 16, 2022, at 6:11 PM, PengHui Li wrote:
>
> Hi Mi
+1 (binding)
- Checked the signature
- Build from the source
- Start the standalone
- Publish and consume messages
- Check the Cassandra connector
- Check the stateful function
Thanks for the great work,
Penghui
On Thu, Feb 17, 2022 at 2:26 AM Ran Gao wrote:
> This is the third release candida
Anonymitaet merged pull request #1:
URL: https://github.com/apache/pulsar-site/pull/1
--
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
Hi Michael,
Please check your key
```
gpg: assuming signed data in 'apache-pulsar-2.8.3-bin.tar.gz'
gpg: Signature made Wed Feb 16 04:49:42 2022 CST
gpg:using RSA key BD4291E509D771B79E7BD1F5C5724B3F5588C4EB
gpg: Good signature from "Michael Marshall " [unknown]
gpg: WARNING: This
Hi all,
Put an update here, I have created branch-2.10[1]
[1]https://github.com/apache/pulsar/tree/branch-2.10
On Thu, Feb 17, 2022 at 9:23 AM PengHui Li wrote:
> Hi Micheal
>
> > Penghui, is your current plan to create branch-2.10, create the
> release artifacts, and start a vote on them all
Hi Lari,
thanks for the proposal, though I don't think it would be good to
change this default value.
Pulsar HTTP API is an administrative service and it is not on the
critical data path.
If all the threads in the pool are busy, it is good to apply back
pressure and slow down the incoming new req
+1 (binding)
- Checked the signature
- Start the standalone
- Publish and consume messages
- Check the Cassandra connector
- Check the stateful function
Thanks for the great work,
Penghui
On Wed, Feb 16, 2022 at 12:35 PM Michael Marshall
wrote:
> This is the second release candidate for Apache
+1
- Checked the signatures
- Run produce and consume on a standalone
Penghui
On Thu, Feb 17, 2022 at 12:45 AM Matteo Merli
wrote:
> +1
>
> Checked signatures, compiled and run perf tool.
>
>
>
> --
> Matteo Merli
>
>
> On Tue, Feb 15, 2022 at 7:28 PM r...@apache.org
> wrote:
> >
> > Hi ever
Hi Micheal
> Penghui, is your current plan to create branch-2.10, create the
release artifacts, and start a vote on them all within a few days of
each other?
Yes, I will create branch-2.10 today.
For starting the vote, we need to confirm these 2 PRs[1] will not introduce
breaking changes. Very g
Yes, but I think that the code freeze is only meaningful if it’s
communicated in advance.
The fact that it was included in the original PIP but never followed in the
practice means it would be a last minute change.
On Wed, Feb 16, 2022 at 2:37 PM Michael Marshall
wrote:
> When we discussed the
> I agree that it can be non-trivial to determine if an issue is an
internal test or an upstream issue.
My main point is that we should prefer early communication of
potential issues that affect pending releases and accept that the
issue might prove to be nothing more than a short delay in the rel
When we discussed the code freeze in the community meeting on 2/3, I
was under the impression that it was a new development to our existing
release process. I subsequently learned it was already defined in
PIP 47. Even if we haven't been following this part of PIP 47, what
is the value in waiting u
bsheltonihs opened a new issue #230:
URL: https://github.com/apache/pulsar-helm-chart/issues/230
**Is your feature request related to a problem? Please describe.**
I am using argo-cd to deploy on openshift using these helm charts. The issue
I have is when I enable functions the `broker-r
bsheltonihs opened a new issue #229:
URL: https://github.com/apache/pulsar-helm-chart/issues/229
**Is your feature request related to a problem? Please describe.**
I am using argo-cd to deploy on openshift using these helm charts. The issue
I have is the backend admin service port is `77
I don't think we should expose this feature flag on the client-side.
Ideally, people shouldn't be aware of partitioned vs non-partitioned.
- Sijie
On Wed, Feb 16, 2022 at 1:37 AM Enrico Olivelli wrote:
> Ping
>
> Il Dom 13 Feb 2022, 11:49 Enrico Olivelli ha
> scritto:
>
> > Hello,
> > I have a
Michael, as we chatted in last weekly meeting (though not yet
formalized), since we have never really done a feature freeze on the
branch during paste releases, we should start from the next release,
to give a decent preview of what to expect to developers in terms of
dates.
> While some may feel
I agree that it can be non-trivial to determine if an issue is an
internal test or an upstream issue.
My main point is that we should prefer early communication of
potential issues that affect pending releases and accept that the
issue might prove to be nothing more than a short delay in the relea
> I will build the release and start the vote before next Monday(GMT+8)
Penghui, is your current plan to create branch-2.10, create the
release artifacts, and start a vote on them all within a few days of
each other?
> I'm doing my best to follow PIP 47, but when seeing a potential break
> change
This is the third release candidate for Apache Pulsar, version 2.9.2.
*** 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://dis
URL: https://github.com/apache/pulsar/issues/14329
Motivation
Since Pulsar Admin API uses the blocking servlet API, all Jetty threads
might be occupied and this causes unavailability of the Pulsar Admin
API. The default value for the maximum number of threads for Jetty is
too low in Pulsar. That
+1
Checked signatures, compiled and run perf tool.
--
Matteo Merli
On Tue, Feb 15, 2022 at 7:28 PM r...@apache.org
wrote:
>
> Hi everyone,
> Please review and vote on the release candidate #1 for the version
> 0.8.0, as follows:
> [ ] +1, Approve the release
> [ ] -1, Do not approve the rel
dave2wave opened a new pull request #1:
URL: https://github.com/apache/pulsar-site/pull/1
Motivation
We are ready to switch over website publishing to the pulsar-site repository.
Modifications
Update the .asf.yaml file which to publish the website from the
asf-site-next branch.
Hi all
Just put an update here.
We have 2 PRs[1] https://github.com/apache/pulsar/pull/13376 and
https://github.com/apache/pulsar/pull/13341
need to do the final verification, and you are also very welcome to verify
these 2 changes in your environment, cases.
I will build the release and start t
Thanks for the great work!
Penghui
On Wed, Feb 16, 2022 at 6:54 PM Lari Hotari wrote:
> I'll vote again with -1.
>
> The "CI - Integration - Cli / cli" build job passes cleanly for 2.7.4 .
> This means that it's very likely that there's a regression in 2.7.5 . I'll
> investigate the issue.
>
>
Hi lari,
> So finally, I understand that "the problem" is that all HTTP server
threads are blocked and this makes the Pulsar Admin API unavailable.
To support the blocking servlet API, Jetty uses a default thread pool that
can grow to up to 200 threads (
https://github.com/eclipse/jetty.project/b
Congrats!
Thanks,
Haiting
On 2022/02/16 10:51:52 Guangning E wrote:
> Configurations!
>
>
> Thanks,
> Guangning
>
> Jia Zhai 于2022年2月16日周三 15:40写道：
>
> > Congratulations
> >
> >
> > On Wed, Feb 16, 2022 at 11:39 AM Yu wrote:
> >
> > > Hi Lili,
> > >
> > > Congrats! Well deserved! You've m
sama8 commented on pull request #434:
URL: https://github.com/apache/pulsar-manager/pull/434#issuecomment-1041477673
Sharing if relevant -> [SAML Jackson](https://github.com/boxyhq/jackson) :)
--
This is an automated message from the Apache Git Service.
To respond to the message, please l
I created PR https://github.com/apache/pulsar/pull/14320 to set
numHttpServerThreads=200 .
Please review
On 2022/02/16 12:39:34 Lari Hotari wrote:
> On 2022/02/16 00:58:20 PengHui Li wrote:
> > Which is a sync method. Ultimately this could lead to all the pulsar-web
> > thread
> > blocked. we'd
On 2022/02/16 00:58:20 PengHui Li wrote:
> Which is a sync method. Ultimately this could lead to all the pulsar-web
> thread
> blocked. we'd better not introduce blocking calls if we use AsyncResponse.
>
> > What issue did you see? Please share more context. Thanks for the
> patience.
>
> It happ
> The contributors found there are many places that might also have the same
> problem.
I'm trying to understand "the problem" even though I haven't received replies
from any of the contributors. For example, my question in
https://github.com/apache/pulsar/issues/14013#issuecomment-1033528348 ha
I'll vote again with -1.
The "CI - Integration - Cli / cli" build job passes cleanly for 2.7.4 . This
means that it's very likely that there's a regression in 2.7.5 . I'll
investigate the issue.
-Lari
On 2022/02/16 10:21:23 Lari Hotari wrote:
> The branch-2.7 build didn't complete cleanly for
Configurations!
Thanks,
Guangning
Jia Zhai 于2022年2月16日周三 15:40写道：
> Congratulations
>
>
> On Wed, Feb 16, 2022 at 11:39 AM Yu wrote:
>
> > Hi Lili,
> >
> > Congrats! Well deserved! You've made a lot of great changes to the Pulsar
> > website!
> >
> > On Tue, Feb 15, 2022 at 5:56 PM ZhangJian
The branch-2.7 build didn't complete cleanly for the release commit
https://github.com/apache/pulsar/commit/ed40840a65c413202c0aab6b9b1a29ed370f6fb7
.
(click on the red cross icon before the text "Release 2.7.5" to see the build
results popup)
There are 3 failing build jobs:
- 2 for "CI - Build
Ping
Il Dom 13 Feb 2022, 11:49 Enrico Olivelli ha scritto:
> Hello,
> I have a use case in which my application MUST use a non-partitioned
> topic to work properly, but the topic name is (of course) configurable
> by the user.
> If I am not using a non-partitioned topic, I do not have string
> g
tuteng commented on pull request #194:
URL:
https://github.com/apache/pulsar-client-node/pull/194#issuecomment-1041259278
> Should we update the document as well? I think we need to define `OS_ARCH`
environment variable when we compile the node client.
Yes I think the documentation
+1
On 2022/02/11 13:47:50 Lari Hotari wrote:
> This is the first release candidate for Apache Pulsar, version 2.7.5.
>
> It contains the following commits after the previous release:
> https://github.com/apache/pulsar/compare/v2.7.4...v2.7.5-candidate-1
>
> *** Please download, test and vote on
77 matches
Mail list logo
