SunnyZ-L opened a new issue #7844:
URL: https://github.com/apache/dolphinscheduler/issues/7844


   ### Search before asking
   
   - [X] I had searched in the 
[issues](https://github.com/apache/dolphinscheduler/issues?q=is%3Aissue) and 
found no similar issues.
   
   
   ### What happened
   
   docs link: 
https://dolphinscheduler.apache.org/zh-cn/docs/2.0.1/user_doc/guide/installation/pseudo-cluster.html
   In the 2.0.1 pseudo-cluster deployment document, there are the following 
problems:
   
   1. The `chown -R` operation mentioned in the following steps, the document 
did not mention where `dolphinscheduler-bin` was created or generated before 
this,Not friendly here
   
![图片](https://user-images.githubusercontent.com/56599784/148323864-25d37fbb-76db-4e67-b6c5-aab8c7114618.png)
   
   2. The following message is wrong, and the database cannot be initialized by 
the `create-dolphinscheduler.sh` script in version 2.0.1
   
![图片](https://user-images.githubusercontent.com/56599784/148327184-93476f41-2dd7-4eb0-92bb-b8789549aee1.png)
   
   3. Before starting the service, it is best to add the `su dolphinscheduler` 
operation prompt to prevent starting operations under non-deployment users
   
![图片](https://user-images.githubusercontent.com/56599784/148327313-cdafc765-3841-470a-b0b1-480b5c3bc498.png)
   
   
   ### What you expected to happen
   
   See "what happend"
   
   ### How to reproduce
   
   see 2.0.1 docs
   
https://dolphinscheduler.apache.org/zh-cn/docs/2.0.1/user_doc/guide/installation/pseudo-cluster.html
   
   ### Anything else
   
   _No response_
   
   ### Version
   
   2.0.1
   
   ### Are you willing to submit PR?
   
   - [X] Yes I am willing to submit a PR!
   
   ### Code of Conduct
   
   - [X] I agree to follow this project's [Code of 
Conduct](https://www.apache.org/foundation/policies/conduct)
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]


Reply via email to