Combinations: SPARK_HOME set in 'O'->point to external spark , no '-'
->head to internal spark lib
spark interpreter setting 〇 〇 - - 〇 - -
zeppelin -env.sh - - - - 〇 〇 〇
environment parameters - 〇 〇 - 〇 〇 -
Work Fine:〇 NG:× 〇 〇 〇 〇 × × ×
The consequences are zeppelin-env.sh has a top priority. An
If you set SPARK_HOME in spark interpreter setting, then please remove
SPARK_HOME in spark-env.sh, otherwise you do will hit weird issue.
小野圭二 于2018年3月6日周二 上午10:56写道：
> Hi Jeff,
>
> I did set SPARK_HOME to use external spark at first. And that was fine
> work on CentOS, but not on Mac.
> Do yo
Hi Jeff,
I did set SPARK_HOME to use external spark at first. And that was fine work
on CentOS, but not on Mac.
Do you mean try it again?
2018-03-06 11:12 GMT+09:00 Jeff Zhang :
> >>> Seems like it is not good chemistry between Spark and Zeppelin on
> Mac. From the reason that the consequence of
>>> Seems like it is not good chemistry between Spark and Zeppelin on Mac.
>From the reason that the consequence of removing the environment
parameters, Zeppelin headed to own spark lib.
Could you specify SPARK_HOME in your spark interpreter to use external
spark instead of zeppelin's own spark li
I wonder why, but it seems work fine, and would like to share how to fix it.
First of all, this issue happened just on MAC.
[THE ENV WAS]
macOS High Sierra v 10.13.3
cpu core i5
mem 8GB
Zeppelin 0.8.0 snapshot
Spark 2.2.0
[ISSUE]
see this previous mails
[SOLUTION]
ref.
http://apac
Nothing changed. I guess this property does not effect cause of failing to
call the interpreter.
i challenged it as log4j...zeppelin=DEBUG, but no way.
2018-03-05 18:24 GMT+09:00 Jeff Zhang :
>
> Try to add the following to log4j.properties for more log
>
> log4j.logger.org.apache.zeppelin.in
Try to add the following to log4j.properties for more log
log4j.logger.org.apache.zeppelin.interpreter=DEBUG
小野圭二 于2018年3月5日周一 下午5:13写道：
> Actually, there was not created the interpreter log file as said 'Cannot
> run interpreter' in the log. And it was run on local machine as MAC, i mean
> st
Actually, there was not created the interpreter log file as said 'Cannot
run interpreter' in the log. And it was run on local machine as MAC, i mean
stand alone. i stopped every firewall to make it easy. And again,this
happened just on Mac. On CentOS, it works fine.
That makes me confusion. :-b
20
Could you check the interpreter log ? The issue of not be able to
connecting to thrift port could happen due to network issue, like firewall
or you use VPN, etc.
小野圭二 于2018年3月5日周一 下午12:32写道：
> Hi,
>
> I show the all log on this error.There are 2 type error. The 1 is at the
> first run. The 2 is
Hi,
I show the all log on this error.There are 2 type error. The 1 is at the
first run. The 2 is at the second run. Seems like could not established to
Thrift callback port 51348 that was set at the first run.
First of all, does it need to establish the callback port of Thrift
server?
The notebook
Hi Jeff,
No one graved 63039 so far on Mac.
Yes, this issue has been reproduced as changing the port NO randomly.
Ono
2018-03-02 14:49 GMT+09:00 Jeff Zhang :
>
> It is possible that 63039 is used by other processes, as Mac can not
> detect whether this port is used or not from my experience.
>
It is possible that 63039 is used by other processes, as Mac can not detect
whether this port is used or not from my experience.
And can you reproduce this issue consistently ? Because each time zeppelin
will chose a random port as long as you don't specify the portRange, so if
you reproduce it co
Hi there,
I am so confusing now, let me know why if You know this, please.
The env:
Mac: High Sierra ver.10.13.3
Zep: 0.7.3
Spark: 2.2.0
Java: 1.8
notebook script: %pyspark print 'aaa' (just it for test)
In this env, i got the error in log as
ERROR ({pool-2-thre
13 matches
Mail list logo
