Skip to content

[SPARK-12784][UI]Fix Spark UI IndexOutOfBoundsException with dynamic allocation #10728

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
wants to merge 2 commits into from
Closed

Conversation

zsxwing
Copy link
Member

@zsxwing zsxwing commented Jan 12, 2016

Add listener.synchronized to get storageStatusList and execInfo atomically.

@tgravescs
Copy link
Contributor

thanks for picking this up so quickly.
I need to look at this a bit further, so I assume the other end modifying the listener.storageStatusList is also synchronized?

One concern I have here is that I don't want to affect application performance just because someone is viewing the UI. If the UI load blocks the application from running, that is bad. I would rather see us get a read only copy of it or something then synchronize.

I'll try to look in more detail tomorrow.

@zsxwing
Copy link
Member Author

zsxwing commented Jan 12, 2016

It usually doesn't affect your application performance. It only blocks the listener bus thread when rendering a page.

@SparkQA
Copy link

SparkQA commented Jan 13, 2016

Test build #49269 has finished for PR 10728 at commit 0c6d0c5.

  • This patch passes all tests.
  • This patch merges cleanly.
  • This patch adds no public classes.

@zsxwing
Copy link
Member Author

zsxwing commented Jan 13, 2016

CC @andrewor14

@andrewor14
Copy link
Contributor

@sarutak

@andrewor14
Copy link
Contributor

This looks OK, and yeah we're not blocking any thread that's actually doing the scheduling or execution so it should be fine.

@@ -52,12 +52,17 @@ private[ui] class ExecutorsPage(
private val listener = parent.listener

def render(request: HttpServletRequest): Seq[Node] = {
val storageStatusList = listener.storageStatusList
val (storageStatusList, execInfo) = listener.synchronized {
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I would add a comment to explain why we need to do this in synchronized though, and include issue number

@sarutak
Copy link
Member

sarutak commented Jan 14, 2016

LGTM

@SparkQA
Copy link

SparkQA commented Jan 14, 2016

Test build #49343 has finished for PR 10728 at commit b47a574.

  • This patch passes all tests.
  • This patch merges cleanly.
  • This patch adds no public classes.

@sarutak
Copy link
Member

sarutak commented Jan 14, 2016

I found a needless semi-colon in ExecutorsPage.scala.

https://github.com/apache/spark/blob/master/core/src/main/scala/org/apache/spark/ui/exec/ExecutorsPage.scala#L110

But it's not a big deal and we have already passed SparkQA so I think it's OK to merge without removing the semi-colon.

@zsxwing
Copy link
Member Author

zsxwing commented Jan 14, 2016

Thanks, merging to master, 1.6 and 1.5

asfgit pushed a commit that referenced this pull request Jan 14, 2016
… allocation

Add `listener.synchronized` to get `storageStatusList` and `execInfo` atomically.

Author: Shixiong Zhu <shixiong@databricks.com>

Closes #10728 from zsxwing/SPARK-12784.

(cherry picked from commit 501e99e)
Signed-off-by: Shixiong Zhu <shixiong@databricks.com>
@asfgit asfgit closed this in 501e99e Jan 14, 2016
asfgit pushed a commit that referenced this pull request Jan 14, 2016
… allocation

Add `listener.synchronized` to get `storageStatusList` and `execInfo` atomically.

Author: Shixiong Zhu <shixiong@databricks.com>

Closes #10728 from zsxwing/SPARK-12784.

(cherry picked from commit 501e99e)
Signed-off-by: Shixiong Zhu <shixiong@databricks.com>
@zsxwing zsxwing deleted the SPARK-12784 branch January 14, 2016 17:55
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants