Github user srowen commented on the issue:
https://github.com/apache/spark/pull/18815
I think we should close this.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wi
Github user guoxiaolongzte commented on the issue:
https://github.com/apache/spark/pull/18815
Ok. That master, worker log and Executor log can be displayed in the WEB UI?
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If
Github user ajbozarth commented on the issue:
https://github.com/apache/spark/pull/18815
Ok then I'm really confused, if the logs we're talking about can already be
viewed in the ui why do we need to display their location on the system?
---
If your project is set up for it, you can
Github user guoxiaolongzte commented on the issue:
https://github.com/apache/spark/pull/18815
Why is the Executor log can be displayed in the WEB UI?
Similarly, I think master, worker log and Executor log is the same. They
can be displayed in the WEB UI.
![image](htt
Github user ajbozarth commented on the issue:
https://github.com/apache/spark/pull/18815
I'm not a fan of this, I remember talking about surfacing this a while ago
and we decided that it was a bad idea, but we may have been talking about
surfacing the log not the path. Either way only
Github user jiangxb1987 commented on the issue:
https://github.com/apache/spark/pull/18815
Yea my concern is whether it is vulnerable to show the log path, maybe
system admin want to keep that private.
---
If your project is set up for it, you can reply to this email and have your
re
Github user guoxiaolongzte commented on the issue:
https://github.com/apache/spark/pull/18815
Yes, I am also considering this security issue. If this only shows a path,
only authorized people can log on to the spark cluster lunix server for log
view, which is relatively safe.
---
If
Github user srowen commented on the issue:
https://github.com/apache/spark/pull/18815
I don't know if this is that important, so not sure if it's worth much
code. Would people generally be able to access the logs anyway? is there a
security issue if I can see the masters logs and open
Github user guoxiaolongzte commented on the issue:
https://github.com/apache/spark/pull/18815
Ok, i will work it, just like hbase. Show master and worker logs, and
provide online viewing. Is this okay?
---
If your project is set up for it, you can reply to this email and have your
re
Github user srowen commented on the issue:
https://github.com/apache/spark/pull/18815
OK, then how can this work? this won't render as a usable link.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does no
Github user guoxiaolongzte commented on the issue:
https://github.com/apache/spark/pull/18815
Yes, it is not an http URI ,at present only a path to tell the user log
path where to facilitate the lunix server query related log information.
---
If your project is set up for it, you ca
Github user srowen commented on the issue:
https://github.com/apache/spark/pull/18815
It's not an http URI though right? it's a path. I'm missing why this is
browseable.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If
Github user guoxiaolongzte commented on the issue:
https://github.com/apache/spark/pull/18815
1.The master process information is as followsï¼
/usr/java8/jdk/bin/java -cp
/opt/ZDH/parcels/lib/spark_gxl/conf/:/opt/ZDH/parcels/lib/spark_gxl/jars/*:/opt/ZDH/parcels/lib/spark_gxl/con
Github user srowen commented on the issue:
https://github.com/apache/spark/pull/18815
Hm, I thought so, even in standalone mode, but I don't know.
OK, if it's a file URI, is that going to be browseable?
---
If your project is set up for it, you can reply to this email and have you
Github user guoxiaolongzte commented on the issue:
https://github.com/apache/spark/pull/18815
@srowen
Are you sure that the master and worker logs can be stored in hdfs?
Spark's master and worker logs are generated by log4j.
---
If your project is set up for it, you can reply
Github user srowen commented on the issue:
https://github.com/apache/spark/pull/18815
This won't necessarily be available to people viewing the UI? it could be
an HDFS location
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as w
Github user guoxiaolongzte commented on the issue:
https://github.com/apache/spark/pull/18815
@srowen Help review the code,Thanks.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
Github user AmplabJenkins commented on the issue:
https://github.com/apache/spark/pull/18815
Can one of the admins verify this patch?
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feat
18 matches
Mail list logo