[
https://issues.apache.org/jira/browse/SPARK-7909?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14564166#comment-14564166
]
Matthew Goodman commented on SPARK-7909:
----------------------------------------
Using the prebuilt binaries from the links provided yields a working cluster.
Is there a timeline for when the spark 1.4.0 binaries make the s3 bucket? I
can add the link to the spark/init.sh script, but it will bounce until the
binary is actually place in the bucket.
In either case I suspect the naming convention will be similar, so would a PR
for the changes outlined above be a good step at this stage?
> spark-ec2 and associated tools not py3 ready
> --------------------------------------------
>
> Key: SPARK-7909
> URL: https://issues.apache.org/jira/browse/SPARK-7909
> Project: Spark
> Issue Type: Improvement
> Components: EC2
> Environment: ec2 python3
> Reporter: Matthew Goodman
>
> At present there is not a possible permutation of tools that supports Python3
> on both the launching computer and running cluster. There are a couple
> problems involved:
> - There is no prebuilt spark binary with python3 support.
> - spark-ec2/spark/init.sh contains inline py3 unfriendly print statements
> - Config files for cluster processes don't seem to make it to all nodes in a
> working format.
> I have fixes for some of this, but the config and running context debugging
> remains elusive to me.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
