[
https://issues.apache.org/jira/browse/HBASE-7904?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13611272#comment-13611272
]
stack commented on HBASE-7904:
------------------------------
[~ted_yu] I asked why you would write your own version if merge exists. You
don't answer my question.
After reading reams of commentary by you pasting logs both here and over in
yarn issues, I am still not clear what the problem is. It seems like my
comment above on exit code 137 being code for OOME seems to be pertinent given
cited YARN issue to disable mem checks (could we up the heap and have this
stuff pass?) but I have no clue on how far we are from resolution or what
action to take upstream. I think I now know what is wanted regards config
reading over in YARN-449 seeing [~sseth] comments there but that issue seems to
have run off into the weeds.... Figuring what is needed should not be this hard.
> Upgrade hadoop 2.0 dependency to 2.0.4-alpha
> --------------------------------------------
>
> Key: HBASE-7904
> URL: https://issues.apache.org/jira/browse/HBASE-7904
> Project: HBase
> Issue Type: Task
> Reporter: Ted Yu
> Assignee: Ted Yu
> Priority: Critical
> Fix For: 0.95.0
>
> Attachments: 7904.txt, 7904-v2-hadoop-2.0.txt,
> 7904-v2-hadoop-2.0.txt, 7904-v2.txt, 7904-v4-hadoop-2.0.txt, 7904-v4.txt,
> 7904-v4.txt, 7904-v5-hadoop-2.0.txt, 7904-v5.txt, hbase-7904-v3.txt
>
>
> 2.0.3-alpha has been released.
> We should upgrade the dependency.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
