zhongjiajie commented on a change in pull request #692:
URL:
https://github.com/apache/dolphinscheduler-website/pull/692#discussion_r809750667
##########
File path: docs/en-us/release/faq.md
##########
@@ -607,4 +607,15 @@ sed -i 's/Defaults requirett/#Defaults requirett/g'
/etc/sudoers
---
+## Q：Support for multiple YARN clusters
Review comment:
Maybe using the keyword `Deploy` is more reasonable
```suggestion
## Q: Deploy for multiple YARN clusters
```
##########
File path: docs/en-us/release/faq.md
##########
@@ -607,4 +607,15 @@ sed -i 's/Defaults requirett/#Defaults requirett/g'
/etc/sudoers
---
+## Q：Support for multiple YARN clusters
+A：By deploying different worker in different yarn clusters，the steps are as
follows(eg: AWS EMR):
+
+ 1. Deploying the worker server on the master node of the EMR cluster
+
+ 2. Changing yarn.application.status.address to current emr's yarn url in
the conf/common.properties
+
+ 3. Execute command bin/dolphinscheduler-daemon.sh start worker-server and
bin/dolphinscheduler-daemon.sh start logger-server to start worker-server and
logger-server
Review comment:
```suggestion
3. Execute command `bin/dolphinscheduler-daemon.sh start worker-server`
and `bin/dolphinscheduler-daemon.sh start logger-server` to start worker-server
and logger-server
```
##########
File path: docs/en-us/release/faq.md
##########
@@ -607,4 +607,15 @@ sed -i 's/Defaults requirett/#Defaults requirett/g'
/etc/sudoers
---
+## Q：Support for multiple YARN clusters
+A：By deploying different worker in different yarn clusters，the steps are as
follows(eg: AWS EMR):
+
+ 1. Deploying the worker server on the master node of the EMR cluster
+
+ 2. Changing yarn.application.status.address to current emr's yarn url in
the conf/common.properties
Review comment:
We better use "``" hint configure file or code
```suggestion
2. Changing yarn.application.status.address to current emr's yarn url in
the `conf/common.properties`
```
--
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]
