Re: [DISCUSS] Cherry-pick PR-16059 to 2.10 to prevent infinite unloading
Hi dev, I pushed a PR https://github.com/apache/pulsar/pull/20822 to fix the infinite unloading. Please help review this PR. Thanks! Thanks, Kai On 2023/07/09 23:40:03 PengHui Li wrote: > Hi Heesung, > > For 2.10, I would like to suggest fixing the issue instead of cherry-picking > the PR. The problem that https://github.com/apache/pulsar/pull/388 had > resolved will happen again if `loadBalancerDistributeBundlesEvenlyEnabled` > is disabled. We should try to remove the configuration in the future > because users are difficult to decide whether to enable or disable it. Both > of them have problems, just different issues. > > > I think we also need to consider the namespace anit-affinity-group logic > too. > > +1, it should be fixed to avoid an infinite bundle unloading loop. > > Thanks, > Penghui > > On Sat, Jul 8, 2023 at 4:07 AM Heesung Sohn > wrote: > > > Hi dev, > > > > I think we also need to consider the namespace anit-affinity-group logic > > too. These logics seem to do similar things. > > > > https://pulsar.apache.org/docs/3.0.x/administration-load-balance/#distribute-anti-affinity-namespaces-across-failure-domains > > > > > > PengHui > > We got three biding votes here. Do you think we should proceed to > > cherry-pick the PR to 2.10, then? > > > > Thanks, > > Heesung > > > > > > > > > > > > On Sun, Jul 2, 2023 at 5:22 PM PengHui Li wrote: > > > > > > `removeMostServicingBrokersForNamespace ` is introduced by [1] to > > > solve the problem that when all bundles in a particular namespace > > > belong to 1 or few machines, customers owning that namespace will be > > > heavily impacted if that broker goes down. Of course, this PR caused > > > the infinite unloading issue and we need to fix it. > > > > > > Thanks for the context. > > > It looks like we can also try to fix the infinite unloading issue. > > > Now, the broker is unloading the bundles without checking the > > distribution > > > of the bundles under a namespace, but it will check when finding > > > a new owner. Is it possible to check the bundle distribution before > > > unloading the bundles to avoid infinite unloading? > > > > > > Regards, > > > Penghui > > > > > > > > > On Sun, Jul 2, 2023 at 3:28 PM Enrico Olivelli > > > wrote: > > > > > > > +1 > > > > > > > > Enrico > > > > > > > > Il Dom 2 Lug 2023, 06:19 Hang Chen ha scritto: > > > > > > > > > +1 for cherry-picking it to branch-2.10. We have a flag to control > > > > > whether to enable or disable it. > > > > > > > > > > `removeMostServicingBrokersForNamespace ` is introduced by [1] to > > > > > solve the problem that when all bundles in a particular namespace > > > > > belong to 1 or few machines, customers owning that namespace will be > > > > > heavily impacted if that broker goes down. Of course, this PR caused > > > > > the infinite unloading issue and we need to fix it. > > > > > > > > > > > I agree with making it false for the next major version release by > > > > > default. > > > > > We'd better remove the config in the next version instead of change > > > > > the default value to `false`, which will make Pulsar's configuration > > > > > keep increasing. > > > > > > > > > > Thanks, > > > > > Hang > > > > > > > > > > [1] https://github.com/apache/pulsar/pull/388 > > > > > > > > > > PengHui Li 于2023年7月1日周六 09:38写道： > > > > > > > > > > > > +1 for cherry-pick to branch-2.10 since users don't have a > > workaround > > > > > > for this issue, and the change is well-understand, low risk. > > > > > > > > > > > > I agree with making it false for the next major version release by > > > > > default. > > > > > > > > > > > > Thanks, > > > > > > Penghui > > > > > > > > > > > > On Sat, Jul 1, 2023 at 9:26 AM Heesung Sohn > > > > > > wrote: > > > > > > > > > > > > > Hi dev, > > > > > > > > > > > > > > I realized that `removeMostServicingBrokersForNamespace` func in > > > the > > > > > broker > > > > > > > selection logic can cause infinite unloading. > > > > > > > > > > > > > > Suppose an overloaded broker unloaded a bundle and only has the > > > > minimum > > > > > > > number of bundles(in that namespace) among brokers. In that case, > > > the > > > > > > > selection logic (`removeMostServicingBrokersForNamespace`) will > > > > filter > > > > > out > > > > > > > other brokers and always reassign the bundle to the previous > > > broker. > > > > > This > > > > > > > will cause infinite unloading(like a boomerang). > > > > > > > > > > > > > > To mitigate this issue, we need to cherry-pick this PR to disable > > > > this > > > > > > > logic by the config. > > > > > > > https://github.com/apache/pulsar/pull/16059 > > > > > > > > > > > > > > And we probably want to disable this > > > > > > > `removeMostServicingBrokersForNamespace` logic by default. > > > > > > > > > > > > > > Regards, > > > > > > > Heesung > > > > > > > > > > > > > > > > > > > > > >
[DISCUSS] Release Pulsar C++ Client 3.3.0
Hi all, I would like to propose releasing the Pulsar C++ Client 3.2.0. It has been about 2 months since the last release. There have been many new features and bug fixes since then. It's time to release a new version. Please let me know if you have any PRs that need to be included in 3.3.0. Thanks, Yunze
[GitHub] [pulsar-connectors] dependabot[bot] opened a new pull request, #6: Bump org.testng:testng from 6.13.1 to 7.5.1 in /pulsar-io/netty
dependabot[bot] opened a new pull request, #6: URL: https://github.com/apache/pulsar-connectors/pull/6 Bumps [org.testng:testng](https://github.com/cbeust/testng) from 6.13.1 to 7.5.1. Release notes Sourced from https://github.com/cbeust/testng/releases";>org.testng:testng's releases. TestNG v7.5.1 What's Changed Cherrypick Zip Slip Vulnerability to 7.5 release by https://github.com/prashil-g";>@prashil-g in https://redirect.github.com/cbeust/testng/pull/2899";>cbeust/testng#2899 New Contributors https://github.com/prashil-g";>@prashil-g made their first contribution in https://redirect.github.com/cbeust/testng/pull/2899";>cbeust/testng#2899 Full Changelog: https://github.com/cbeust/testng/compare/7.5...7.5.1";>https://github.com/cbeust/testng/compare/7.5...7.5.1 Changelog Sourced from https://github.com/testng-team/testng/blob/master/CHANGES.txt";>org.testng:testng's changelog. Current Fixed: GITHUB-2934: Parallel Dataproviders & retries causes test result count to be skewed (Krishnan Mahadevan) Fixed: GITHUB-2925: Issue in ITestcontext.getAllTestMethods() with annotation https://github.com/BeforeSuite";>@BeforeSuite (Krishnan Mahadevan) Fixed: GITHUB-2928: The constructor of TestRunner encountered NBC changes in 7.8.0 (Krishnan Mahadevan) Fixed: GITHUB-581: Parameters of nested test suites are overridden(Krishnan Mahadevan) Fixed: GITHUB-727 : Fixing data races (Krishnan Mahadevan) Fixed: GITHUB-2913: Maps containing nulls can be incorrectly considered equal (Alex Heneveld) 7.8.0 Fixed: GITHUB-2906: Generate testng-results.xml per test suite (Krishnan Mahadevan) New: GITHUB-2897: Not exception but warning if some (not all) of the given test names are not found in suite files. (Bruce Wen) New: GITHUB-2907: Added assertListContains and assertListContainsObject methods to check if specific object present in List (Dmytro Budym) Fixed: GITHUB-2888: Skipped Tests with DataProvider appear as failed (Joaquin Moreira) Fixed: GITHUB-2884: Discrepancies with DataProvider and Retry of failed tests (Krishnan Mahadevan) Fixed: GITHUB-2879: Test listeners specified in parent testng.xml file are not included in testng-failed.xml file (Krishnan Mahadevan) Fixed: GITHUB-2866: TestNG.xml doesn't honour Parallel value of a clone (Krishnan Mahadevan) Fixed: GITHUB-2875: JUnitReportReporter should capture the test case output at the test case level Fixed: GITHUB-2771: After upgrading to TestNG 7.5.0, setting ITestResult.status to FAILURE doesn't fail the test anymore (Julien Herr & Krishnan Mahadevan) Fixed: GITHUB-2862: Allow test classes to define "configfailurepolicy" at a per class level (Krishnan Mahadevan) Fixed: GITHUB-2796: Option for onAfterClass to run after https://github.com/AfterClass";>@AfterClass (Oliver Hughes) Fixed: GITHUB-2857: XmlTest index is not set for test suites invoked with YAML (Sergei Baranov) Fixed: GITHUB-2880: Before configuration and before invocation set 'SKIP' when beforeMethod is 'skip' (Bob Shi) Fixed: GITHUB-2886: testng-results xml reports config skips from base classes as ignored (Krishnan Mahadevan) 7.7.1 Fixed: GITHUB-2854: overloaded assertEquals methods do not work from Groovy (Krishnan Mahadevan) 7.7.0 Fixed: GITHUB-2852: [SECURITY] Fix Zip Slip Vulnerability (Jonathan Leitschuh) Fixed: GITHUB-2792: JUnitTestClass sets XmlTest as null when running JUnit 4 Tests using TestNG (Krishnan Mahadevan) Fixed: GITHUB-2847: Deprecate support for running JUnit tests (Krishnan Mahadevan) Fixed: GITHUB-2844: Deprecate support for running Spock Tests (Krishnan Mahadevan) Fixed: GITHUB-550: Weird https://github.com/BeforeMethod";>@BeforeMethod and https://github.com/AfterMethod";>@AfterMethod behaviour with dependsOnMethods (Krishnan Mahadevan) Fixed: GITHUB-893: TestNG should provide an Api which allow to find all dependent of a specific test (Krishnan Mahadevan) New: Added .yml file extension for yaml suite files, previously only .yaml was allowed for yaml (Steven Jubb) Fixed: GITHUB-141: regular expression in "dependsOnMethods" does not work (Krishnan Mahadevan) Fixed: GITHUB-2770: FileAlreadyExistsException when report is generated (melloware) Fixed: GITHUB-2825: Programmatically Loading TestNG Suite from JAR File Fails to Delete Temporary Copy of Suite File (Steven Jubb) Fixed: GITHUB-2818: Add configuration key for callback discrepancy behavior (Krishnan Mahadevan) Fixed: GITHUB-2819: Ability to retry a data provider in case of failures (Krishnan Mahadevan) Fixed: GITHUB-2308: StringIndexOutOfBoundsException in findClassesInPackage - Surefire/Maven - JDK 11 fails (Krishnan Mahadevan) Fixed: GITHUB:2788: TestResult.isSuccess() is TRUE when test fails due to expectedExceptions (Krishnan Mahadevan) Fixed: GITHUB-2800: Running Test Classes with Inherited
[GitHub] [pulsar-connectors] dependabot[bot] opened a new pull request, #5: Bump junit:junit from 4.10 to 4.13.1 in /pulsar-io/flume
dependabot[bot] opened a new pull request, #5: URL: https://github.com/apache/pulsar-connectors/pull/5 Bumps [junit:junit](https://github.com/junit-team/junit4) from 4.10 to 4.13.1. Release notes Sourced from https://github.com/junit-team/junit4/releases";>junit:junit's releases. JUnit 4.13.1 Please refer to the https://github.com/junit-team/junit/blob/HEAD/doc/ReleaseNotes4.13.1.md";>release notes for details. JUnit 4.13 Please refer to the https://github.com/junit-team/junit/blob/HEAD/doc/ReleaseNotes4.13.md";>release notes for details. JUnit 4.13 RC 2 Please refer to the https://github.com/junit-team/junit4/wiki/4.13-Release-Notes";>release notes for details. JUnit 4.13 RC 1 Please refer to the https://github.com/junit-team/junit4/wiki/4.13-Release-Notes";>release notes for details. JUnit 4.13 Beta 3 Please refer to the https://github.com/junit-team/junit4/wiki/4.13-Release-Notes";>release notes for details. JUnit 4.13 Beta 2 Please refer to the https://github.com/junit-team/junit4/wiki/4.13-Release-Notes";>release notes for details. JUnit 4.13 Beta 1 Please refer to the https://github.com/junit-team/junit4/wiki/4.13-Release-Notes";>release notes for details. JUnit 4.12 Please refer to the https://github.com/junit-team/junit/blob/HEAD/doc/ReleaseNotes4.12.md";>release notes for details. JUnit 4.12 Beta 3 Please refer to the https://github.com/junit-team/junit/blob/HEAD/doc/ReleaseNotes4.12.md";>release notes for details. JUnit 4.12 Beta 2 No release notes provided. JUnit 4.12 Beta 1 No release notes provided. JUnit 4.11 No release notes provided. Commits https://github.com/junit-team/junit4/commit/1b683f4ec07bcfa40149f086d32240f805487e66";>1b683f4 [maven-release-plugin] prepare release r4.13.1 https://github.com/junit-team/junit4/commit/ce6ce3aadc070db2902698fe0d3dc6729cd631f2";>ce6ce3a Draft 4.13.1 release notes https://github.com/junit-team/junit4/commit/c29dd8239d6b353e699397eb090a1fd27411fa24";>c29dd82 Change version to 4.13.1-SNAPSHOT https://github.com/junit-team/junit4/commit/1d174861f0b64f97ab0722bb324a760bfb02f567";>1d17486 Add a link to assertThrows in exception testing https://github.com/junit-team/junit4/commit/543905df72ff10364b94dda27552efebf3dd04e9";>543905d Use separate line for annotation in Javadoc https://github.com/junit-team/junit4/commit/510e906b391e7e46a346e1c852416dc7be934944";>510e906 Add sub headlines to class Javadoc https://github.com/junit-team/junit4/commit/610155b8c22138329f0723eec22521627dbc52ae";>610155b Merge pull request from GHSA-269g-pwp5-87pp https://github.com/junit-team/junit4/commit/b6cfd1e3d736cc2106242a8be799615b472c7fec";>b6cfd1e Explicitly wrap float parameter for consistency (https://redirect.github.com/junit-team/junit4/issues/1671";>#1671) https://github.com/junit-team/junit4/commit/a5d205c7956dbed302b3bb5ecde5ba4299f0b646";>a5d205c Fix GitHub link in FAQ (https://redirect.github.com/junit-team/junit4/issues/1672";>#1672) https://github.com/junit-team/junit4/commit/3a5c6b4d08f408c8ca6a8e0bae71a9bc5a8f97e8";>3a5c6b4 Deprecated since jdk9 replacing constructor instance of Double and Float (https://redirect.github.com/junit-team/junit4/issues/1660";>#1660) Additional commits viewable in https://github.com/junit-team/junit4/compare/r4.10...r4.13.1";>compare view [](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores) Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting `@dependabot rebase`. [//]: # (dependabot-automerge-start) [//]: # (dependabot-automerge-end) --- Dependabot commands and options You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will
[GitHub] [pulsar-presto] dependabot[bot] opened a new pull request, #9: Bump org.glassfish.jersey.core:jersey-common from 2.31 to 2.34 in /presto-distribution
dependabot[bot] opened a new pull request, #9: URL: https://github.com/apache/pulsar-presto/pull/9 Bumps org.glassfish.jersey.core:jersey-common from 2.31 to 2.34. [](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores) Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting `@dependabot rebase`. [//]: # (dependabot-automerge-start) [//]: # (dependabot-automerge-end) --- Dependabot commands and options You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself) You can disable automated security fix PRs for this repo from the [Security Alerts page](https://github.com/apache/pulsar-presto/network/alerts). -- 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-connectors] dependabot[bot] opened a new pull request, #4: Bump org.apache.solr:solr-core from 8.6.3 to 8.8.2 in /pulsar-io/solr
dependabot[bot] opened a new pull request, #4: URL: https://github.com/apache/pulsar-connectors/pull/4 Bumps org.apache.solr:solr-core from 8.6.3 to 8.8.2. [](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores) Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting `@dependabot rebase`. [//]: # (dependabot-automerge-start) [//]: # (dependabot-automerge-end) --- Dependabot commands and options You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot ignore this major version` will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this minor version` will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself) You can disable automated security fix PRs for this repo from the [Security Alerts page](https://github.com/apache/pulsar-connectors/network/alerts). -- 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: Re: [DISCUSS] Seek for maintainers of pulsar-manager
NOTE: Earlier mail was sent in such a messy state, so I am sending my reply again. IMO, Pulsar-manager[1] really could benefit from more tests. Fortunately, I am familiar with the tech stack tho might need some recollection on front-end :)) If you plan on continuing the work, Tison. I will also start to look around and put in some work. Thanks, JooHyukKim (vince) [1] https://github.com/apache/pulsar-manager On 2023/07/23 07:44:05 Joo Hyuk Kim wrote: > > However, the tech stack is a bit old to take up and it seems we have > fewer contributors maintain this project. I tried to resolve some issues > but encountered troubles in both lack of time and lack of collaborators. > > > It really seems that the Pulsar-manager project lacks contributions and > could benefit from more tests. > > > > Thus, I started this thread to seek maintainers (or collaborators, I'm > spending some time on this project, but it's a bit frustrating to me to > recap the design alone (of course, the project needs a recap)) of > pulsar-manager. > > > Fortunately, I am familiar with the tech stack, especially with the backend > in Spring. Although the frontend might need some recollection :)). > > > If you plan on continuing the work, Tison. I will also start to look around > and put in some work. > > > Thanks, > > JooHyukKim (vince) > > On Wed, Jul 19, 2023 at 6:40 PM tison wrote: > > > Hi devs, > > > > The pulsar-manager project[1], while it's still under 0.x version series, > > has had low traffic during the past years. > > > > I recently drove the release of pulsar-manager 0.4.0[2] and saw an > > increasing issue traffics around the community. > > > > However, the tech stack is a bit old to take up and it seems we have fewer > > contributors maintain this project. I tried to resolve some issues but > > encountered troubles in both lack of time and lack of collaborators. > > > > I remember a thread talking about Pulsar UI[3]. But no maintainer of > > pulsar-manager showed up in that thread. The pulsar-manager project looks > > half-implemented and stalls. > > > > Thus, I started this thread to seek maintainers (or collaborators, I'm > > spending some time on this project, but it's a bit frustrating to me to > > recap the design alone (of course, the project needs a recap)) of > > pulsar-manager. > > > > Also cc @users, let me know how you use this project, what's your > > expectations of this project, and if you are will to share your > > requirements as well as patches among the community. > > > > Looking forward to your feedback! > > > > Best, > > tison. > > > > [1] https://github.com/apache/pulsar-manager > > [2] https://lists.apache.org/thread/03h1yvqx0lkj3htxd55zj6wfk95bcvlo > > [3] https://lists.apache.org/thread/y20bkzwtkqtky517g560cdoq7g95ttkx > > >
Re: [DISCUSS] Seek for maintainers of pulsar-manager
> However, the tech stack is a bit old to take up and it seems we have fewer contributors maintain this project. I tried to resolve some issues but encountered troubles in both lack of time and lack of collaborators. It really seems that the Pulsar-manager project lacks contributions and could benefit from more tests. > Thus, I started this thread to seek maintainers (or collaborators, I'm spending some time on this project, but it's a bit frustrating to me to recap the design alone (of course, the project needs a recap)) of pulsar-manager. Fortunately, I am familiar with the tech stack, especially with the backend in Spring. Although the frontend might need some recollection :)). If you plan on continuing the work, Tison. I will also start to look around and put in some work. Thanks, JooHyukKim (vince) On Wed, Jul 19, 2023 at 6:40 PM tison wrote: > Hi devs, > > The pulsar-manager project[1], while it's still under 0.x version series, > has had low traffic during the past years. > > I recently drove the release of pulsar-manager 0.4.0[2] and saw an > increasing issue traffics around the community. > > However, the tech stack is a bit old to take up and it seems we have fewer > contributors maintain this project. I tried to resolve some issues but > encountered troubles in both lack of time and lack of collaborators. > > I remember a thread talking about Pulsar UI[3]. But no maintainer of > pulsar-manager showed up in that thread. The pulsar-manager project looks > half-implemented and stalls. > > Thus, I started this thread to seek maintainers (or collaborators, I'm > spending some time on this project, but it's a bit frustrating to me to > recap the design alone (of course, the project needs a recap)) of > pulsar-manager. > > Also cc @users, let me know how you use this project, what's your > expectations of this project, and if you are will to share your > requirements as well as patches among the community. > > Looking forward to your feedback! > > Best, > tison. > > [1] https://github.com/apache/pulsar-manager > [2] https://lists.apache.org/thread/03h1yvqx0lkj3htxd55zj6wfk95bcvlo > [3] https://lists.apache.org/thread/y20bkzwtkqtky517g560cdoq7g95ttkx >
Re: [ANNOUNCE] Zili Chen (tison) as new PMC member in Apache Pulsar
Congrats! Best, lifepuzzlefun On 2023/07/23 04:13:35 Haiting Jiang wrote: > Congrats! > > Best, > Haiting > > On Sun, Jul 23, 2023 at 9:38 AM houxiaoyu wrote: > > > > Congrats, Tison! > > > > Best, > > Xiaoyu Hou > > > > Dave Fisher 于2023年7月22日周六 22:23写道： > > > > > Congratulations! > > > > > > Sent from my iPhone > > > > > > > On Jul 21, 2023, at 10:05 AM, Michael Marshall > > > wrote: > > > > > > > > Hi Pulsar Community, > > > > > > > > The Apache Pulsar Project Management Committee (PMC) has invited Zili > > > Chen > > > > (https://github.com/tisonkun) as a member of the PMC and we are > > > > pleased to announce that tison has accepted. > > > > > > > > tison is very active in the community by contributing and reviewing > > > > many PRs, actively engaging on the mailing list, triaging GitHub > > > > Issues, and helping out with the website. > > > > > > > > On behalf of the Pulsar PMC, welcome and congratulations to tison! > > > > > > > > Best, > > > > Michael > > > >
