The Ops guy would probably be fired if he doesn't make sure the container
runtime is up 24/7.
From: Mich Talebzadeh
Sent: Wednesday, December 8, 2021 12:33 PM
Cc: user @spark
Subject: Re: start-history-server.sh doesn't survive system reboot.
Recommendation
will be taking because the deployment of such HS would
> be more flexible.
>
> Thanks!
> --
> *From:* Sean Owen
> *Sent:* Tuesday, December 7, 2021 1:29 PM
> *To:* James Yu
> *Cc:* user @spark
> *Subject:* Re: start-history-server.sh doesn
Sent: Tuesday, December 7, 2021 1:29 PM
To: James Yu
Cc: user @spark
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
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
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 wrote:
> Hi Users,
>
> We found
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
