Github user 2ooom commented on the issue:
https://github.com/apache/spark/pull/18860
@srowen At criteo the issue has grown critical about 3 month ago and at
that point (we had 11k rows in history table at a time and) when history page
was taking at least 1min to load. Now we'
Github user 2ooom closed the pull request at:
https://github.com/apache/spark/pull/18860
---
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
Github user 2ooom commented on the issue:
https://github.com/apache/spark/pull/18860
Thank you @srowen
---
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
GitHub user 2ooom opened a pull request:
https://github.com/apache/spark/pull/18777
[SPARK-21254] [WebUI] History UI Performance fixes
## What changes were proposed in this pull request?
As described in JIRA ticket, History page is taking ~1min to load for cases
when
GitHub user 2ooom opened a pull request:
https://github.com/apache/spark/pull/18783
[SPARK-21254] [WebUI] History UI performance fixes
## What changes were proposed in this pull request?
As described in JIRA ticket, History page is taking ~1min to load for cases
when
Github user 2ooom commented on the issue:
https://github.com/apache/spark/pull/18783
@srowen This one is for master branch, #18777 is for `branch-2.1`
---
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
Github user 2ooom closed the pull request at:
https://github.com/apache/spark/pull/18777
---
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
Github user 2ooom commented on the issue:
https://github.com/apache/spark/pull/18783
@srowen Done
---
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
Github user 2ooom commented on the issue:
https://github.com/apache/spark/pull/18783
Thank you @ajbozarth
---
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
Github user 2ooom commented on a diff in the pull request:
https://github.com/apache/spark/pull/18783#discussion_r130645467
--- Diff: pom.xml ---
@@ -179,7 +179,7 @@
1.1
2.52.0
2.6
-1.8
+
2.27
1.8
--- End diff
Github user 2ooom commented on the issue:
https://github.com/apache/spark/pull/18783
Could we try to run tests and build on Jenkins?
---
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
Github user 2ooom commented on the issue:
https://github.com/apache/spark/pull/18783
Thank you @srowen. Seems like jenkins is happy. Should we merge in this
case?
---
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
GitHub user 2ooom opened a pull request:
https://github.com/apache/spark/pull/18860
[SPARK-21254] [WebUI] History UI performance fixes
## This is a backport of PR #18783 to the latest released branch 2.2.
## What changes were proposed in this pull request?
As
13 matches
Mail list logo
