Sean Owen commented on SPARK-17944:

Yeah, I think Solaris is the odd man out here then. Linux and OS X support 
this. I'm not sure Solaris is something Spark intends to support in general, 
for reasons like this. If there's a simple change that makes it work, OK, but 
otherwise I'd close this.

> sbin/start-* scripts use of `hostname -f` fail for Solaris 
> -----------------------------------------------------------
>                 Key: SPARK-17944
>                 URL: https://issues.apache.org/jira/browse/SPARK-17944
>             Project: Spark
>          Issue Type: Bug
>    Affects Versions: 2.0.1
>         Environment: Solaris 10, Solaris 11
>            Reporter: Erik O'Shaughnessy
>            Priority: Trivial
> {{$SPARK_HOME/sbin/start-master.sh}} fails:
> {noformat}
> $ ./start-master.sh 
> usage: hostname [[-t] system_name]
>        hostname [-D]
> starting org.apache.spark.deploy.master.Master, logging to 
> /home/eoshaugh/local/spark/logs/spark-eoshaugh-org.apache.spark.deploy.master.Master-1-m7-16-002-ld1.out
> failed to launch org.apache.spark.deploy.master.Master:
>     --properties-file FILE Path to a custom Spark properties file.
>                            Default is conf/spark-defaults.conf.
> full log in 
> /home/eoshaugh/local/spark/logs/spark-eoshaugh-org.apache.spark.deploy.master.Master-1-m7-16-002-ld1.out
> {noformat}
> I found SPARK-17546 which changed the invocation of hostname in 
> sbin/start-master.sh, sbin/start-slaves.sh and sbin/start-mesos-dispatcher.sh 
> to include the flag {{-f}}, which is not a valid command line option for the 
> Solaris hostname implementation. 
> As a workaround, Solaris users can substitute:
> {noformat}
> `/usr/sbin/check-hostname | awk '{print $NF}'`
> {noformat}
> Admittedly not an obvious fix, but it provides equivalent functionality. 

This message was sent by Atlassian JIRA

To unsubscribe, e-mail: issues-unsubscr...@spark.apache.org
For additional commands, e-mail: issues-h...@spark.apache.org

Reply via email to