[
https://issues.apache.org/jira/browse/BIGTOP-576?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13438066#comment-13438066
]
Roman Shaposhnik commented on BIGTOP-576:
-----------------------------------------
Hash, take a look at this: BIGTOP-478 we went back to mapred as a user name.
Perhaps going back to mapred in every single bit (like package names, file
locations, etc) would've made sense but...
> Minor discrepancy in naming of logs/users vs. base log directories
> ------------------------------------------------------------------
>
> Key: BIGTOP-576
> URL: https://issues.apache.org/jira/browse/BIGTOP-576
> Project: Bigtop
> Issue Type: Improvement
> Components: General
> Environment: CentOS6
> Reporter: Harsh J
> Assignee: Roman Shaposhnik
> Priority: Trivial
> Labels: nitpick
> Fix For: 0.5.0
>
>
> I noticed the following log file in my installation:
> {{/var/log/hadoop-mapreduce/yarn-mapred-historyserver-test.vm.log}}
> My very minute complaint here is: Why is the user for MR history server
> {{mapred}}, when the log dir is named {{mapreduce}}. Or take it vice versa.
> Can we have this standardized somehow? Like both using mapreduce/mapreduce
> or, mapred/mapred?
> I understand it would be difficult to make the change now, nor is the current
> form a problem in any way. I'm not suggesting we change this immediately and
> break things in any way, but would be good if we did fix this to be more
> consistent somehow in future.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
