You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@bigtop.apache.org by "Roman Shaposhnik (Created) (JIRA)" <ji...@apache.org> on 2012/04/06 19:07:22 UTC
[jira] [Created] (BIGTOP-516) it would be cleaner to get rid of
mapreduce entries in limits.d/mapreduce.conf now that we consolidated the
user back to mapred
it would be cleaner to get rid of mapreduce entries in limits.d/mapreduce.conf now that we consolidated the user back to mapred
-------------------------------------------------------------------------------------------------------------------------------
Key: BIGTOP-516
URL: https://issues.apache.org/jira/browse/BIGTOP-516
Project: Bigtop
Issue Type: Bug
Components: General
Affects Versions: 0.4.0
Reporter: Roman Shaposhnik
Assignee: Roman Shaposhnik
Fix For: 0.4.0
--
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
[jira] [Updated] (BIGTOP-516) it would be cleaner to get rid of
mapreduce entries in limits.d/mapreduce.conf now that we consolidated the
user back to mapred
Posted by "Roman Shaposhnik (Updated) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/BIGTOP-516?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Roman Shaposhnik updated BIGTOP-516:
------------------------------------
Attachment: BIGTOP-516.patch.txt
> it would be cleaner to get rid of mapreduce entries in limits.d/mapreduce.conf now that we consolidated the user back to mapred
> -------------------------------------------------------------------------------------------------------------------------------
>
> Key: BIGTOP-516
> URL: https://issues.apache.org/jira/browse/BIGTOP-516
> Project: Bigtop
> Issue Type: Bug
> Components: General
> Affects Versions: 0.4.0
> Reporter: Roman Shaposhnik
> Assignee: Roman Shaposhnik
> Fix For: 0.4.0
>
> Attachments: BIGTOP-516.patch.txt
>
>
--
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
[jira] [Commented] (BIGTOP-516) it would be cleaner to get rid of
mapreduce entries in limits.d/mapreduce.conf now that we consolidated the
user back to mapred
Posted by "Peter Linnell (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/BIGTOP-516?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13248502#comment-13248502 ]
Peter Linnell commented on BIGTOP-516:
--------------------------------------
+1
> it would be cleaner to get rid of mapreduce entries in limits.d/mapreduce.conf now that we consolidated the user back to mapred
> -------------------------------------------------------------------------------------------------------------------------------
>
> Key: BIGTOP-516
> URL: https://issues.apache.org/jira/browse/BIGTOP-516
> Project: Bigtop
> Issue Type: Bug
> Components: General
> Affects Versions: 0.4.0
> Reporter: Roman Shaposhnik
> Assignee: Roman Shaposhnik
> Fix For: 0.4.0
>
> Attachments: BIGTOP-516.patch.txt
>
>
--
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