[ 
https://issues.apache.org/jira/browse/MAPREDUCE-7295?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18044004#comment-18044004
 ] 

ASF GitHub Bot commented on MAPREDUCE-7295:
-------------------------------------------

github-actions[bot] commented on PR #2270:
URL: https://github.com/apache/hadoop/pull/2270#issuecomment-3634837497

   We're closing this stale PR because it has been open for 100 days with no 
activity. This isn't a judgement on the merit of the PR in any way. It's just a 
way of keeping the PR queue manageable.
   If you feel like this was a mistake, or you would like to continue working 
on it, please feel free to re-open it and ask for a committer to remove the 
stale tag and review again.
   Thanks all for your contribution.




> Add support to read history files from the done directory
> ---------------------------------------------------------
>
>                 Key: MAPREDUCE-7295
>                 URL: https://issues.apache.org/jira/browse/MAPREDUCE-7295
>             Project: Hadoop Map/Reduce
>          Issue Type: Wish
>          Components: jobhistoryserver
>    Affects Versions: 2.9.2, 3.2.1
>            Reporter: Gaurangi Saxena
>            Priority: Minor
>
> We would like to add a configuration option that enables a history-server to 
> read files directly from done directory, instead of moving them from 
> intermediate to done directory.
> Current setup of mapreduce code, displays files that our moved by a history 
> server from intermediate to done. We cannot have two servers (job cluster and 
> static history server) doing this as it could lead to race conditions. 
> Our service wants to configure a static history server that displays jobs run 
> on multiple clusters. We would like this server to only read from log 
> directories.
>  
>  



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to