You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@spark.apache.org by "Sean Owen (JIRA)" <ji...@apache.org> on 2016/11/12 10:05:58 UTC

[jira] [Updated] (SPARK-18382) "run at null:-1" in UI when no file/line info in call site info

     [ https://issues.apache.org/jira/browse/SPARK-18382?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Sean Owen updated SPARK-18382:
------------------------------
    Assignee: Sean Owen
    Priority: Trivial  (was: Minor)
     Summary: "run at null:-1" in UI when no file/line info in call site info  (was: What does “run at null:-1” mean in Apache Spark WEB UI?)

This is easy to touch up cosmetically so it shows what it's "supposed" to, the default of "<unknown>:0" instead of "null:-1". 

It looks like it happens when there are no debug symbols. Do you build Spark yourself and maybe strip these with flags like '-optimize'?

> "run at null:-1" in UI when no file/line info in call site info
> ---------------------------------------------------------------
>
>                 Key: SPARK-18382
>                 URL: https://issues.apache.org/jira/browse/SPARK-18382
>             Project: Spark
>          Issue Type: Bug
>          Components: Spark Core, Web UI
>    Affects Versions: 2.0.0
>         Environment: Windows 10, Scala Eclipse Luna, Intel i3, 6gb RAM
>            Reporter: Emiliano Amendola
>            Assignee: Sean Owen
>            Priority: Trivial
>
> From my Apache WEB UI dashboard. I've seen a lot of this run at null:-1 jobs, several actually in my particular project that comprises basically of: connect to a JDBC PostgreSQL Server, fetch some tables, creating some temp tables and do some aggregations with org.apache.spark.sql.Cube() method.
> Link to image: http://i.stack.imgur.com/UEfgM.png



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@spark.apache.org
For additional commands, e-mail: issues-help@spark.apache.org