Ray Mattingly

Results 24 comments of Ray Mattingly

I believe [this test failure](https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-5713/2/testReport/org.apache.hadoop.hbase.regionserver/TestHRegion/precommit_checks___yetus_jdk8_Hadoop3_checks______/) is unrelated

We've removed the minimum wait interval logic. I'm going to open a separate Jira regarding tiny backoffs and how we can improve them.

🤔 that's new. Just pushed a rebase

I believe the two test failures on [the latest build](https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-5713/7/testReport/) are unrelated.

Hey @pankaj72981 and @mokai87, is there any reason not to merge this backport? We're seeing this error in a mostly vanilla build of HBase 2.6.2, and would love to get...

We're going to handle this backport here: https://github.com/apache/hbase/pull/7118

> Enabling/disabling tables happens often enough that it might be fine to simply fail and force the user to manually handle the failure. Do you mean "happens ~often~ infrequently enough"?...

That's a good question. Despite the existing behavior, I think the intention was always for this to be more of a soft limit — the [TimedQuota proto](https://github.com/apache/hbase/blob/740e9372105b7d31721e3f7eea6b2b2e85d55f84/hbase-protocol-shaded/src/main/protobuf/server/Quota.proto#L35-L40) actually calls the...

I agree with you, and considered the MARTL approach internally but didn't do a good job of documenting this publicly. My pushback is not that we _shouldn't_ add support for...