* Implement the RegionServer reading violation from the quota table
* Implement the Master reporting violations to the quota table
* RegionServers need to track its enforced policies
Adds a new Chore to the Master that analyzes the reports that are
sent by RegionServers. The Master must then, for all tables with
quotas, determine the tables that are violating quotas and move
those tables into violation. Similarly, tables no longer violating
the quota can be moved out of violation.
The Chore is the "stateful" bit, managing which tables are and
are not in violation. Everything else is just performing
computation and informing the Chore on the updated state.
Added InterfaceAudience annotations and clean up the QuotaObserverChore
constructor. Cleaned up some javadoc and QuotaObserverChore. Reuse
the QuotaViolationStore impl objects.
- internalRestoreSnapshot() returns future which completes by just getting proc_id from master. Changed it to wait for the procedure to complete.
- Refactor TestAsyncSnapshotAdminApi: Add cleanup() which deletes all tables and snapshots after every test run. Simplifies individual tests.
Change-Id: Idc30fb699db32d58fd0f60da220953a430f1d3cc
Test was failing on clusters with large number of servers or regions. Using commonly using config settings like some other tests seems to work.
Signed-off-by: Michael Stack <stack@apache.org>
With Apache parent pom v12 our remote-resources-plugin execution id was
shadowing the parent declaration, and our configuration would get run to
aggregate LICENSE files correctly. When upgrading to v18, apache changed
the execution id, so our configuration no longer gets used.
Add an explicit goal to our usage of the remote-resources-plugin and
change the name to something more descriptive and less likely to
conflict (either intentionally or not).
Signed-off-by: Josh Elser <elserj@apache.org>
Use https for fetching d3 since builds.apache.org is also https. Otherwise d3 script is not loaded (unless browser is explicitly told to do so) and the fancy status markers are not drawn.
Change-Id: I97f7402141717da77499d09e44b05ecdd35c5a6f
The default behavior for abort() method of StateMachineProcedure is changed to support aborting all procedures irrespective of if rollback is supported or not. Currently its observed that sometimes procedures may fail on a step which will be considered as retryable error as abort is not supported. As a result procedure may stuck in a endless loop repeating same step again.User should have an option to abort any stuck procedure and do clean up manually. Please refer to HBASE-18016 and discussion there.
Signed-off-by: Michael Stack <stack@apache.org>
Josh Elser
tedyu
Apekshit Sharma
Guanghao Zhang
zhangduo
anastas
Umesh Agashe
Mike Drob
Jingcheng Du
huzheng
Chia-Ping Tsai
Guangxu Cheng
anoopsamjohn
Andrew Purtell
Michael Stack
Vincent
Roman Nikitchenko