GitHub user yongtang opened a pull request:

    https://github.com/apache/spark/pull/17181

    [SPARK-19824][Core] Standalone master JSON not showing cores for running 
applications

    ## What changes were proposed in this pull request?
    
    This fix tries to address the issue raised in SPARK-19824 where
    the JSON API of the standalone master ("/json") does not show
    the number of cores for a running (active) application, which is
    available on the master UI.
    
    The reason was that in master UI, `coresGranted` was used:
    
https://github.com/apache/spark/blob/v2.1.0/core/src/main/scala/org/apache/spark/deploy/master/ui/MasterPage.scala#L220
    while in JSON API, the `desc.maxCores` was used. In case
    there is no limit on `maxCores`, this filed will be missing on
    JSON API. (Master UI show cores granted so the field is always available).
    
    This fix address the discrepancy by changing JSON API to use
    `coredGranted` so that UI and JSON API are consistent.
    
    ## How was this patch tested?
    
    The test was done manually.
    
    Please review http://spark.apache.org/contributing.html before opening a 
pull request.


You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/yongtang/spark SPARK-19824

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/spark/pull/17181.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #17181
    
----

----


---
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]

Reply via email to