[
https://issues.apache.org/jira/browse/MAPREDUCE-5411?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jason Lowe updated MAPREDUCE-5411:
----------------------------------
Status: Open (was: Patch Available)
The patch has gone stale, could you refresh it? Also a few comments:
* I think the refresh protocol should have a way of conveying success/failure
back to clients. A boolean result would be a minimum, or potentially throwing
an exception if the refresh fails with details on the failure. That would
allow the CLI to report a proper exit code if the refresh did not succeed.
* On a related note, the refresh should note it failed to the caller if a
CachedHistoryStorage is not being used. Currently it doesn't even log if
that's the case and just silently proceeds.
> Refresh size of loaded job cache on history server
> --------------------------------------------------
>
> Key: MAPREDUCE-5411
> URL: https://issues.apache.org/jira/browse/MAPREDUCE-5411
> Project: Hadoop Map/Reduce
> Issue Type: Sub-task
> Components: jobhistoryserver
> Affects Versions: 2.1.0-beta
> Reporter: Ashwin Shankar
> Assignee: Ashwin Shankar
> Labels: features
> Attachments: LOADED_JOB_CACHE_MR5411-1.txt
>
>
> We want to be able to refresh size of the loaded job
> cache(mapreduce.jobhistory.loadedjobs.cache.size) of history server
> through history server's admin interface.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
