Hi Sammi and others, Thanks for bringing up this discussion!
I worked with him closely in the same company previously. One of the issues caused job slowness, which was reported by some users. Sumit tried to fix it. He committed some code changes. Unfortunately, that particular change could cause data loss, a much more severe problem. The good thing was that, although the change was merged, the problem had been discovered before causing real data loss. Of course, all developers including you and me are susceptible to introducing bugs. However, the manner in which the bug was introduced, along with Sumit’s subsequent handling of the issue, has given rise to significant concern. - Why did the change get merged? No tests added along with the changes. Sumit did test it manually but the manual tests conducted were way too simple. - When we were discussing the issue, I found he actually neither understood the code nor the problem, but he dared to merge the code. Note that the code he changed was at the most important data path in Ozone. - Sumit initially proposed some other changes without trying to completely understand the code first. - When we came up with a potential bug fix, Sumit wanted to merge it without adding new tests. The reason was that adding new tests was not easy. It was understandable but unacceptable. - When Sumit agreed to add tests, the tests he proposed again were way too simple. We spent a long time having many discussions. He finally was convinced -- for that particular issue, we had to understand the problem first and also had to test the change seriously. I would agree that Sumit is smart and very good at debugging, and he has made a lot of contributions to Ozone. However, he might be immature to handle important issues. Therefore, I would disagree with nominating him as a PMC member. Regards, Tsz-Wo On Thu, Jul 30, 2026 at 12:14 AM Sammi Chen <[email protected]> wrote: > Dear PMCs, > > I would like to propose adding Sumit Agrawal[1] to the PMC. > > Sumit > - has been a committer on 2023-05-22, 3 years ago [2] > - has contributed 156 PRs [3], 476 reviews [4] > > These are the highlights of his contributions > - Fix broken Quota function with FSO bucket and Legacy bucket, and later > quota for snapshot support. [5][6] > - Improve HDDS block deletion efficiency. [7] > - Handling disk issues, preventing disk becomes full, and handle duplicate > container replicas on a datanode[8] > - Distributed tracing improvement, migrate from OpenTracing to > OpenTelemetry[9] > - Migrating Ozone Manager replication from post Ratis execution to Pre > Ratis execution, design discussion, and work on the POC. [10][11] > > Besides above feature based contributions, Sumit also has a lot of > production cluster issue investigation and fix experiences, and contributed > a lot of critical fixes to Ozone, > including performance bottleneck resolve, data loss prevention, etc. > I think he is a good candidate for Ozone PMC. He will bring his unique > insight to the community. What do you think? > > Disclaimer: We share the same employer. > > - Sammi Chen > > [1] https://github.com/sumitagrawl > [2] https://whimsy.apache.org/roster/committer/sumitagrawal > [3] > https://github.com/apache/ozone/issues?q=is%3Apr%20author%3Asumitagrawl > [4] > https://github.com/apache/ozone/pulls?q=is%3Apr+reviewed-by%3Asumitagrawl+ > [5] https://issues.apache.org/jira/browse/HDDS-7479 > [6] https://issues.apache.org/jira/browse/HDDS-7598 > [7] https://issues.apache.org/jira/browse/HDDS-6548 > [8] https://issues.apache.org/jira/browse/HDDS-12564 > [9] https://issues.apache.org/jira/browse/HDDS-13679 > [10] https://issues.apache.org/jira/browse/HDDS-11897 > [11] https://issues.apache.org/jira/browse/HDDS-11900 >
