You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@bigtop.apache.org by "Konstantin Boudnik (JIRA)" <ji...@apache.org> on 2015/11/02 04:30:28 UTC
[jira] [Comment Edited] (BIGTOP-2104) Packages upgrade to Spark
1.5.1
[ https://issues.apache.org/jira/browse/BIGTOP-2104?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14984692#comment-14984692 ]
Konstantin Boudnik edited comment on BIGTOP-2104 at 11/2/15 3:30 AM:
---------------------------------------------------------------------
Ok, apparently {{spark.master yarn}} will only affect submitted applications and it needs to be fixed for non-yarn deployments like standalone, etc. Perhaps it might be done as a separate JIRA or as an improvement for the Puppet recipes update.
In the meanwhile, I have figured out what was wrong with the startup (although I don't know why). For some reason, master is binding to the container's IP address (e.g. 172.17.0.10) despite that {{SPARK_MASTER_IP}} is set to the container's hostname. Work however is trying to connect the master via the hostname and the whole shenanigan fails ;(
It doesn't seem like a packaging issue, but more like a screwup on the Spark side. Yet, we still need to figure out why this is happening. I anyone has ideas - please chime in!
I tend to commit this patch tomorrow afternoon unless I hear otherwise from the author or someone else.
was (Author: cos):
Ok, apparently {{spark.master yarn}} will only affect submitted applications and it needs to be fixed for non-yarn deployments like standalone, etc. Perhaps it might be done as a separate JIRA or as an improvement for the Puppet recipes update.
In the meanwhile, I have figured out what was wrong with the startup (although I don't know why). For some reason, master is binding to the container's IP address (e.g. 172.17.0.10) despite that {{SPARK_MASTER_IP}} is set to the container's hostname. Work however is trying to connect the master via the hostname and the whole shenanigan fails ;(
It doesn't seem like a packaging issue, but more like a screwup on the Spark side. I tend to commit this patch tomorrow afternoon unless I hear otherwise from the author or someone else.
> Packages upgrade to Spark 1.5.1
> -------------------------------
>
> Key: BIGTOP-2104
> URL: https://issues.apache.org/jira/browse/BIGTOP-2104
> Project: Bigtop
> Issue Type: Sub-task
> Components: debian, rpm
> Affects Versions: 1.0.0
> Reporter: Konstantin Boudnik
> Assignee: Jonathan Kelly
> Fix For: 1.1.0
>
> Attachments: BIGTOP-2104.patch
>
>
> Let's upgrade packaging separately
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)