[
https://issues.apache.org/jira/browse/SPARK-3610?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Patrick Wendell updated SPARK-3610:
-----------------------------------
Description:
Right now we use the user-defined application name when creating the logging
file for the history server. We should use some type of GUID generated from
inside of Spark instead of allowing user input here. It can cause errors if
users provide characters that are not valid in filesystem paths.
Original bug report:
The default log files for the Mllib examples use a rather long naming
convention that includes special characters like parentheses and comma.For e.g.
one of my log files is named
"binaryclassifier-with-params(input.txt,100,1.0,svm,l2,0.1)-1410566770032".
When I click on the program on the history server page (at port 18080), to view
the detailed application logs, the history server crashes and I need to restart
it. I am using Spark 1.1 on a mesos cluster.
I renamed the log file by removing the special characters and then it loads
up correctly. I am not sure which program is creating the log files. Can it be
changed so that the default log file naming convention does not include
special characters?
was:
Right now we don't have a
Original bug report:
The default log files for the Mllib examples use a rather long naming
convention that includes special characters like parentheses and comma.For e.g.
one of my log files is named
"binaryclassifier-with-params(input.txt,100,1.0,svm,l2,0.1)-1410566770032".
When I click on the program on the history server page (at port 18080), to view
the detailed application logs, the history server crashes and I need to restart
it. I am using Spark 1.1 on a mesos cluster.
I renamed the log file by removing the special characters and then it loads
up correctly. I am not sure which program is creating the log files. Can it be
changed so that the default log file naming convention does not include
special characters?
> History server log name should not be based on user input
> ---------------------------------------------------------
>
> Key: SPARK-3610
> URL: https://issues.apache.org/jira/browse/SPARK-3610
> Project: Spark
> Issue Type: Bug
> Affects Versions: 1.1.0
> Reporter: SK
> Priority: Critical
> Fix For: 1.1.0
>
>
> Right now we use the user-defined application name when creating the logging
> file for the history server. We should use some type of GUID generated from
> inside of Spark instead of allowing user input here. It can cause errors if
> users provide characters that are not valid in filesystem paths.
> Original bug report:
> The default log files for the Mllib examples use a rather long naming
> convention that includes special characters like parentheses and comma.For
> e.g. one of my log files is named
> "binaryclassifier-with-params(input.txt,100,1.0,svm,l2,0.1)-1410566770032".
> When I click on the program on the history server page (at port 18080), to
> view the detailed application logs, the history server crashes and I need to
> restart it. I am using Spark 1.1 on a mesos cluster.
> I renamed the log file by removing the special characters and then it loads
> up correctly. I am not sure which program is creating the log files. Can it
> be changed so that the default log file naming convention does not include
> special characters?
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscr...@spark.apache.org
For additional commands, e-mail: issues-h...@spark.apache.org
