One way would be to cron the startup script
1. enable cron on the host and Unix login that runs $SPARK_HOME/sbin/start-history-server.sh where $SPARK_HOME is set in below cron to absolute value say /opt/spark. You can run it as non root, putting it in the crontab of the corresponding user 2. crontab -e 3. Add the following to the cronfile 4. @reboot (/opt/spark/sbin/start-history-server.sh > /var/tmp/start-history-server_"`date +%Y%m%d_%H%M%S`.log" 2>&1) 5. crontab -l to verify that it is added OK to the cronfile. The other way would be to add it to startup in /etc/init.d and create symlink to /etc/rc.d. Do a Google search for it HTH view my Linkedin profile <https://www.linkedin.com/in/mich-talebzadeh-ph-d-5205b2/> *Disclaimer:* Use it at your own risk. Any and all responsibility for any loss, damage or destruction of data or any other property which may arise from relying on this email's technical content is explicitly disclaimed. The author will in no case be liable for any monetary damages arising from such loss, damage or destruction. On Tue, 7 Dec 2021 at 21:23, James Yu <ja...@ispot.tv> wrote: > Hi Users, > > We found that the history server launched by using the > "start-history-server.sh" command does not survive system reboot. Any > recommendation of making it always up even after reboot? > > Thanks, > > James >
