nchammas commented on code in PR #57536:
URL: https://github.com/apache/spark/pull/57536#discussion_r3652585361


##########
docs/spark-standalone.md:
##########
@@ -100,13 +100,16 @@ Once you've set up this file, you can launch or stop your 
cluster with the follo
 - `sbin/start-master.sh` - Starts a master instance on the machine the script 
is executed on.
 - `sbin/start-workers.sh` - Starts a worker instance on each machine specified 
in the `conf/workers` file.
 - `sbin/start-worker.sh` - Starts a worker instance on the machine the script 
is executed on.
-- `sbin/start-connect-server.sh` - Starts a Spark Connect server on the 
machine the script is executed on.
+- `sbin/start-connect-server.sh` - Starts a [Spark 
Connect](spark-connect-overview.html) server on the machine the script is 
executed on.
+- `sbin/start-history-server.sh` - Starts the History Server, which lets you 
view logs for completed applications. Requires event logging to be enabled (see 
[Monitoring and Instrumentation](monitoring.html)).

Review Comment:
   The section this is in is called "Cluster Launch Scripts", so I don't know 
if we want to leave mention of the History server out of here since it gets a 
dedicated mention in the monitoring page. The Thrift server also gets its own 
call out in the "Distributed SQL Engine" page (which is currently not in this 
list).
   
   I like the idea of having a complete list of the `sbin` scripts users may be 
interested in, even if some of them get additional explanation elsewhere. In 
that case, I'd also add the Thrift server here.
   
   What do you think, @uros-b?



-- 
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]


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to