Details
-
Improvement
-
Status: Closed
-
Major
-
Resolution: Fixed
-
None
-
None
-
Incompatible change, Reviewed
-
This JIRA modifies the signature of PriorityFunction#getPriority() method to also take request user as a parameter; all RPC requests sent by super users (as determined by cluster configuration) are executed with Admin QoS.
Description
HBASE-13351 annotates Master RPCs so that RegionServer RPCs are treated with a higher priority compared to user RPCs (and they are handled by a separate set of handlers, etc.). It may be good to stretch this to users too - hbase superuser (configured via hbase.superuser) gets higher priority over other users in the RPC handling. That way the superuser can always perform administrative operations on the cluster even if all the normal priority handlers are occupied (for example, we had a situation where all the master's handlers were tied up with many simultaneous createTable RPC calls from multiple users and the master wasn't able to perform any operations initiated by the admin). (Discussed this some with enis and elserj).
Does this make sense to others?
Attachments
Attachments
Issue Links
- breaks
-
HBASE-15315 Remove always set super user call as high priority
- Closed
- is related to
-
HBASE-10619 Don't allow non super users to do DDL ops on system tables
- Closed
- relates to
-
HBASE-16676 All RPC requests serviced by PriorityRpcServer in some deploys after HBASE-13375
- Closed
-
HBASE-13351 Annotate internal MasterRpcServices methods with admin priority
- Closed
-
HBASE-13755 Provide single super user check implementation
- Closed