Github user pwendell commented on the pull request:
https://github.com/apache/spark/pull/3456#issuecomment-64907251
Sorry I still don't see why this doesn't break sorting. Let's say I want to
answer "which task as the longest GC time in this page?" If there is pagination
there is now way to globally sort this unless we push ordering logic into the
server side rendering of the page (which this patch doesn't do). With this
patch I can only sort locally within the sub-range defined by the page
boundaries.
The second thing is, it would be good to run a heap dump and specifically
see why we OOM when rendering a large page like this. We already have to keep
around O(tasks) state in memory, so I don't see why rendering should require
excessively more memory.
---
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 [email protected] or file a JIRA ticket
with INFRA.
---
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
