This section describes how to create a role on MRS Manager and authorize and manage Manager and components.
Up to 1,000 roles can be created on MRS Manager.
You have learned service requirements.
Role Name is mandatory and contains 3 to 30 digits, letters, and underscores (_). Description is optional.
Resource Supporting Permission Management |
Permission Setting |
---|---|
Alarm |
Authorizes the Manager alarm function. You can select View to view alarms and Management to manage alarms. |
Audit |
Authorizes the Manager audit log function. You can select View to view audit logs and Management to manage audit logs. |
Dashboard |
Authorizes the Manager overview function. You can select View to view the cluster overview. |
Hosts |
Authorizes the node management function. You can select View to view node information and Management to manage nodes. |
Services |
Authorizes the service management function. You can select View to view service information and Management to manage services. |
System_cluster_management |
Authorizes the MRS cluster management function. You can select Management to use the MRS patch management function. |
System_configuration |
Authorizes the MRS cluster configuration function. You can select Management to configure MRS clusters on Manager. |
System_task |
Authorizes the MRS cluster task function. You can select Management to manage periodic tasks of MRS clusters on Manager. |
Tenant |
Authorizes the Manager multi-tenant management function. You can select Management to manage multi-tenants. |
Resource Supporting Permission Management |
Permission Setting |
---|---|
SUPER_USER_GROUP |
Grants you HBase administrator rights. |
Global |
HBase resource type, indicating the whole HBase. |
Namespace |
HBase resource type, indicating namespace, which is used to store HBase tables. It has the following permissions:
|
Table |
HBase resource type, indicating a data table, which is used to store data. It has the following permissions:
|
ColumnFamily |
HBase resource type, indicating a column family, which is used to store data. It has the following permissions:
|
Qualifier |
HBase resource type, indicating a column, which is used to store data. It has the following permissions:
|
By default, permissions of an HBase resource type of each level are shared by resource types of sub-levels. However, the Recursive option is not selected by default. For example, if Read and Write permissions are added to the default namespace, they are automatically added to the tables, column families, and columns in the namespace. If a child resource is set after the parent resource, the permission of the child resource is the union of the permissions of the parent resource and the current child resource.
Resource Supporting Permission Management |
Permission Setting |
---|---|
Folder |
HDFS resource type, indicating an HDFS directory, which is used to store files or subdirectories. It has the following permissions:
|
Files |
HDFS resource type, indicating a file in HDFS. It has the following permissions:
|
Permissions of an HDFS directory of each level are not shared by directory types of sub-levels by default. For example, if Read and Execute permissions are added to the tmp directory, you must select Recursive at the same time to add permissions to subdirectories.
Resource Supporting Permission Management |
Permission Setting |
---|---|
Hive Admin Privilege |
Grants you Hive administrator rights. |
Database |
Hive resource type, indicating a Hive database, which is used to store Hive tables. It has the following permissions:
|
Table |
Hive resource type, indicating a Hive table, which is used to store data. It has the following permissions:
|
By default, permissions of a Hive resource type of each level are shared by resource types of sub-levels. However, the Recursive option is not selected by default. For example, if Select and Insert permissions are added to the default database, they are automatically added to the tables and columns in the database. If a child resource is set after the parent resource, the permission of the child resource is the union of the permissions of the parent resource and the current child resource.
Resource Supporting Permission Management |
Permission Setting |
---|---|
Cluster Admin Operations |
Grants you Yarn administrator rights. |
root |
Root queue of Yarn. It has the following permissions:
|
Parent Queue |
Yarn resource type, indicating a parent queue containing sub-queues. A root queue is a type of a parent queue. It has the following permissions:
|
Leaf Queue |
Yarn resource type, indicating a leaf queue. It has the following permissions:
|
By default, permissions of a Yarn resource type of each level are shared by resource types of sub-levels. However, the Recursive option is not selected by default. For example, if the Submit permission is added to the root queue, it is automatically added to the sub-queue. Permissions inherited by sub-queues will not be displayed as selected in the Permission table. If a child resource is set after the parent resource, the permission of the child resource is the union of the permissions of the parent resource and the current child resource.
Resource Supporting Permission Management |
Permission Setting |
---|---|
Storage Policy Admin |
Grants you storage policy administrator rights. |
Modifying a role
If you change permissions assigned by the role, it takes 3 minutes to make new configurations take effect.
Deleting a role