Re: [Discuss] draft PIP for "Changes to GitHub Actions based Pulsar CI"

Thank you for the comments Penghui. Exactly what you said, we should make the tests stable. The proposals in the other draft PIP "Changes to flaky test handling" deals with that. It's currently a draft and needs more eyes. Would you be able to take a closer look at that too? BR, Lari On Fri, Jan

Re: [Discuss] draft PIP for "Changes to GitHub Actions based Pulsar CI"

Thanks for the comments, Yong. Very good point. Re-running a single job isn't supported. Currently, re-rerunning is required because it is the way we deal with flaky tests. There is a separate draft PIP for "Changes to flaky test handling" in discussion, https://lists.apache.org/thread.html/r4c23

Re: [Discuss] draft PIP for "Changes to GitHub Actions based Pulsar CI"

Currently, especially for the integration tests, a lot time to build pulsar distributions and docker images. I think before merge tests we should to make the test stable, otherwise rerun the test will become more expensive. Thanks, Penghui On Jan 29, 2021, 11:55 AM +0800, Yong Zhang , wrote: > I

Re: [Discuss] draft PIP for "Changes to GitHub Actions based Pulsar CI"

I am not sure that merge all the workflows into one workflow is a good idea. As I know, Github Actions doesn't allow to rerun a single job in a workflow. That means if there has any failure in the workflow, we need to rerun all steps/stage. There has a worst-case is we failed in the different test

Re: [Discuss] draft PIP for "Changes to flaky test handling"

Looking forward to the Pulsar test be more stable and CI can pass easily! -- Yong On Fri, 29 Jan 2021 at 00:35, Lari Hotari wrote: > Thank you Jennifer. I'll take a look soon. > Regards, Lari > > On Thu, Jan 28, 2021 at 4:13 PM Jinfeng Huang > > wrote: > > > Hi Lari, > > Thank you very much fo

Re: [E] Re: [PIP-78] Split the individual acknowledgments into multiple entries

My only point was, if the broker tries to manage more than 10M unack message ranges (per subscription) then the broker has to face many negative consequences in terms of memory and CPU, and then it will require to build additional debt to solve such problems. Therefore, I consider 10M unack message

Re: [E] Re: [PIP-78] Split the individual acknowledgments into multiple entries

Agreed with Lin. I think we should try to abstract this into an interface and allow different implementations. Rajan - what is your real concern making it abstract? - Sijie On Wed, Jan 27, 2021 at 7:37 PM Lin Lin wrote: > Hi Rajan, > Thank you for your PR. > The main difference lies in whether

[Discuss] draft PIP for "Changes to GitHub Actions based Pulsar CI"

Dear Pulsar community members, Currently, the Pulsar GitHub Actions workflows are consuming the majority of the shared pool of resources allocated for github.com/apache projects. Other Apache projects have been impacted and there is a demand to improve the Pulsar CI

[Workshop] Bring streaming to Cassandra with Pulsar

Hi Pulsar enthusiasts, With a growing amount of data flowing between sources, applications and users, solid streaming technologies are now a must when building cloud-native data driven applications. One such technology lifting data driven applications off the ground is Pulsar, which is able to

Re: [Discuss] draft PIP for "Changes to flaky test handling"

Thank you Jennifer. I'll take a look soon. Regards, Lari On Thu, Jan 28, 2021 at 4:13 PM Jinfeng Huang wrote: > Hi Lari, > Thank you very much for driving the process. > I've left some comments and my concerns in your google doc, hope it won't > bother you too much. > > Best Regards, > Jennifer

Re: [Discuss] draft PIP for "Changes to flaky test handling"

Hi Lari, Thank you very much for driving the process. I've left some comments and my concerns in your google doc, hope it won't bother you too much. Best Regards, Jennifer On Wed, Jan 27, 2021 at 10:54 PM Enrico Olivelli wrote: > I really would love to see our CI environment in good shape. > S

[GitHub] [pulsar-helm-chart] rvashishth opened a new issue #103: Add node_exporter template

rvashishth opened a new issue #103: URL: https://github.com/apache/pulsar-helm-chart/issues/103 **Is your feature request related to a problem? Please describe.** The grafana dashboards should display metrics for nodes and containers. Use prometheus `node_exporter` to export kubernetes n