MAPREDUCE-7295 Add support for a read-only history server #2270
Conversation
…rectory Change-Id: If06fea445e89396fee3b058dccbd5e7013d0d8e3 Reviewed-on: https://bigdataoss-internal-review.googlesource.com/c/third_party/apache/hadoop/+/18630 Reviewed-by: Igor Dvorzhak <idv@google.com>
…ltiple done directories 1. Remove dependency on JodaTime 2. Disable wait on move to done directory when in readonly mode Change-Id: I9b3c39cd86a226948bb68b9ddd8ee9885f79e635 Reviewed-on: https://bigdataoss-internal-review.googlesource.com/c/third_party/apache/hadoop/+/21290 Reviewed-by: Igor Dvorzhak <idv@google.com>
jiwq
left a comment
jiwq
left a comment
There was a problem hiding this comment.
@Gaurangi94 Thanks for your contribution. I think we should move this JIRA to MapReduce project first. Do you have the detail design docs?
Gaurangi94
changed the title
Hello, I have moved the issue to https://issues.apache.org/jira/browse/MAPREDUCE-7295. Is there a specific template I should follow for the design doc? |
As I know don't have the specific template. But I think you can follow the other design doc such as https://issues.apache.org/jira/browse/YARN-5139 |
2 participants
Currently history server implementation moves files from intermediate to done directory. We would like to add an additional server that can function as an alternate read only history server. To support it we would need to provide a functionality to read from done directory only. This will be a useful feature for multi cluster environments. #2028
NOTICE
Please create an issue in ASF JIRA before opening a pull request,
and you need to set the title of the pull request which starts with
the corresponding JIRA issue number. (e.g. HADOOP-XXXXX. Fix a typo in YYY.)
For more details, please see https://cwiki.apache.org/confluence/display/HADOOP/How+To+Contribute