Just thought about another possibility which is to containerize the history server and run the container with proper restart policy. This may be the approach we will be taking because the deployment of such HS would be more flexible.
Thanks! ________________________________ From: Sean Owen <sro...@gmail.com> Sent: Tuesday, December 7, 2021 1:29 PM To: James Yu <ja...@ispot.tv> Cc: user @spark <user@spark.apache.org> Subject: Re: start-history-server.sh doesn't survive system reboot. Recommendation? The scripts just launch the processes. To make any process restart on system restart, you would need to set it up as a system service (i.e. controlled by 'service'). That's easy enough but out of scope for Spark itself. On Tue, Dec 7, 2021 at 3:23 PM James Yu <ja...@ispot.tv<mailto: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
