diff options
| author | Andrew Or <andrew@databricks.com> | 2015-03-25 13:28:32 -0700 |
|---|---|---|
| committer | Andrew Or <andrew@databricks.com> | 2015-03-25 13:28:32 -0700 |
| commit | c1b74df6042b33b2b061cb07c2fbd82dba9074bb (patch) | |
| tree | d35c54daae8f4592fd934990fc9207c377d3cf4a /docs/mllib-clustering.md | |
| parent | acef51defb991bcdc99b76cf2a126afd6d60ec70 (diff) | |
| download | spark-c1b74df6042b33b2b061cb07c2fbd82dba9074bb.tar.gz spark-c1b74df6042b33b2b061cb07c2fbd82dba9074bb.tar.bz2 spark-c1b74df6042b33b2b061cb07c2fbd82dba9074bb.zip | |
[SPARK-5771] Master UI inconsistently displays application cores
If the user calls `sc.stop()`, then the number of cores under "Completed Applications" will be 0. If the user does not call `sc.stop()`, then the number of cores will be however many cores were being used before the application exited. This PR makes both cases have the behavior of the latter.
Note that there have been a series of PR that attempted to fix this. For the full discussion, please refer to #4841. The unregister event is necessary because of a subtle race condition explained in that PR.
Tested this locally with and without calling `sc.stop()`.
Author: Andrew Or <andrew@databricks.com>
Closes #5177 from andrewor14/master-ui-cores and squashes the following commits:
62449d1 [Andrew Or] Freeze application state before finishing it
Diffstat (limited to 'docs/mllib-clustering.md')
0 files changed, 0 insertions, 0 deletions