[jira] [Work logged] (MAPREDUCE-7312) Add cache switch of MapReduce History Server

["ASF GitHub Bot (Jira)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/MAPREDUCE-7312?focusedWorklogId=523819&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-523819 ]

ASF GitHub Bot logged work on MAPREDUCE-7312:
---------------------------------------------

                Author: ASF GitHub Bot
            Created on: 14/Dec/20 11:47
            Start Date: 14/Dec/20 11:47
    Worklog Time Spent: 10m 
      Work Description: Deegue opened a new pull request #2547:
URL: https://github.com/apache/hadoop/pull/2547


   History Server scans `done` directory while initializing. If there are millions of application files to cache, it will become a time demanding action.
   
   In our cluster, it'll be 4+ hours before the initialization is done. We added a switch to control whether doing initialized cache or not.
   
   Configuring `mapreduce.jobhistory.joblist.cache.size` is not appropriate when we need cache as many applications as possible and  History Server starts up quickly as the same time.
   


----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
users@infra.apache.org


Issue Time Tracking
-------------------

            Worklog Id:     (was: 523819)
    Remaining Estimate: 0h
            Time Spent: 10m

> Add cache switch of MapReduce History Server
> --------------------------------------------
>
>                 Key: MAPREDUCE-7312
>                 URL: https://issues.apache.org/jira/browse/MAPREDUCE-7312
>             Project: Hadoop Map/Reduce
>          Issue Type: Improvement
>            Reporter: Deegue
>            Priority: Minor
>          Time Spent: 10m
>  Remaining Estimate: 0h
>
> History Server scans `done` directory while initializing. If there are millions of application files to cache, it will become a time demanding action.
> In our cluster, it'll be 4+ hours before the initialization is done.
> We added a switch to control whether doing initialized cache or not.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

---------------------------------------------------------------------
To unsubscribe, e-mail: mapreduce-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: mapreduce-issues-help@hadoop.apache.org