Github user squito commented on the pull request:
https://github.com/apache/spark/pull/6263#issuecomment-159409155
Hi @archit279thakur,
good questions about what to do with the time it was killed. The reason I
wanted it included is so the user could put it together with the timeline, to
see what stages were running when the executor was killed, to help them debug
*why* the executor was removed. I dont' have strong opinions about where it
should go in the UI -- I'm willing to believe that it will just lead to too
much clutter. @CodingCat , any thoughts? But in either case, it would still
be nice to have in the json endpoint.
btw, the mima failure is from this:
```
[error] * method
this(java.lang.String,java.lang.String,Int,Long,Long,Int,Int,Int,Int,Long,Long,Long,Long,Long,scala.collection.Map)Unit
in class org.apache.spark.status.api.v1.ExecutorSummary does not have a
correspondent in new version
[error] filter with:
ProblemFilters.exclude[MissingMethodProblem]("org.apache.spark.status.api.v1.ExecutorSummary.this")
```
you can add that line to `project/MimaExcludes.scala`, that constructor is
private so this a false positive.
---
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 wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---
---------------------------------------------------------------------
To unsubscribe, e-mail: reviews-unsubscr...@spark.apache.org
For additional commands, e-mail: reviews-h...@spark.apache.org
