admin/dolphinscheduler123
queue
parameter to execute programs such as Spark and MapReduce.Security Center->Queue Management
page and clicks the "Create Queue" button to create a new queue.worker.tenant.auto.create
as true
in configuration file worker.properties
. After that DolphinScheduler will create a user if not exists, The property worker.tenant.auto.create=true
requests worker run sudo
command without password.Security Center->Tenant Management
page and clicks the Create Tenant
button to create a tenant.Users are divided into administrator users and normal users
The administrator enters the Security Center -> User Management
page and clicks the Create User
button to create a user.
Edit user information
Security Center->User Management
page and clicks the Edit
button to edit user information.Edit
button to edit the user information.Modify user password
Security Center->User Management
page and clicks the Edit
button. When editing user information, enter the new password to modify the user password.Edit
button, then the password modification is a success.Security Center -> Alarm Group Management
page and clicks the Create Alarm Group
button to create an alarm group.Since the back-end interface has login check, token management provides a way to execute various operations on the system by calling interfaces.
Security Center -> Token Management page
, clicks the Create Token
button, selects the expiration time and user, clicks the Generate Token
button, and clicks the Submit
button, then create the selected user's token successfully.Generate Token
button, and click the Submit
button, then the user creates a token successfully. /**
* test token
*/
public void doPOSTParam()throws Exception{
// create HttpClient
CloseableHttpClient httpclient = HttpClients.createDefault();
// create http post request
HttpPost httpPost = new HttpPost("http://127.0.0.1:12345/escheduler/projects/create");
httpPost.setHeader("token", "123");
// set parameters
List<NameValuePair> parameters = new ArrayList<NameValuePair>();
parameters.add(new BasicNameValuePair("projectName", "qzw"));
parameters.add(new BasicNameValuePair("desc", "qzw"));
UrlEncodedFormEntity formEntity = new UrlEncodedFormEntity(parameters);
httpPost.setEntity(formEntity);
CloseableHttpResponse response = null;
try {
// execute
response = httpclient.execute(httpPost);
// response status code 200
if (response.getStatusLine().getStatusCode() == 200) {
String content = EntityUtils.toString(response.getEntity(), "UTF-8");
System.out.println(content);
}
} finally {
if (response != null) {
response.close();
}
httpclient.close();
}
}
* Granted permissions include project permissions, resource permissions, data source permissions, UDF function permissions.
* The administrator can authorize the projects, resources, data sources and UDF functions to normal users which not created by them. Because the way to authorize projects, resources, data sources and UDF functions to users is the same, we take project authorization as an example.
* Note: The user has all permissions to the projects created by them. Projects will not be displayed in the project list and the selected project list.
Security Center -> User Management
page and clicks the Authorize
button of the user who needs to be authorized, as shown in the figure below:
Each worker node will belong to its own worker group, and the default group is "default".
When executing a task, the task can be assigned to the specified worker group, and the task will be executed by the worker node in the group.
Add or update worker group
conf/worker.properties
configuration file on the worker node where you want to configure the groups and modify the worker.groups
parameter.worker.groups
parameter is followed by the name of the group corresponding to the worker node, which is default
.worker.groups=default,test
worker.properties
. The step to modify work group as below: Security Center -> Worker Group Management -> click 'New Worker Group' -> click 'New Worker Group' -> enter 'Group Name' -> Select Exists Worker -> Click Submit
.Configure the Worker operating environment online. A Worker can specify multiple environments, and each environment is equivalent to the dolphinscheduler_env.sh
file.
The default environment is the dolphinscheduler_env.sh
file.
When executing a task, the task can be assigned to the specified worker group, and select the corresponding environment according to the worker group. Finally, the worker node executes the environment first and then executes the task.
Add or update environment
dolphinscheduler_env.sh
file.Usage environment