[
https://issues.apache.org/jira/browse/HBASE-20556?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16484636#comment-16484636
]
Sean Busbey commented on HBASE-20556:
-------------------------------------
bq. Mike Drob and Sean Busbey do we want HBASE-20608 to go in before this so we
can ensure a clean run or are we okay with ignoring the failures? It appears
that this has been failing for some time.
now that we know HBASE-20608 is failing I'd like us not to continue pushing
stuff without knowing wether or not there are more problems hidden underneath.
That said, I don't have the bandwidth to go around blocking patches currently
so weigh my opinion accordingly.
bq. Also, I'm not sure if either of you have context on the unit test
'failures', but it looks like the tests hit a hard limit on memory (since I
doubt we are calling system.exit() in our test code). Is there something we can
do to fix that (also likely not related to this change)? Is memory something we
control at the test level or overall test execution level?
we have some control over things like memory, but it's done at the overall test
execution level IIRC. I don't know what the current settings are. I don't have
the nightly/precommit yetus stuff in working memory at the moment because I'm
too far in the weeds on HBASE-20331. should be pushing away from that a bit
soon and can get an idea.
> Backport HBASE-16490 to branch-1
> --------------------------------
>
> Key: HBASE-20556
> URL: https://issues.apache.org/jira/browse/HBASE-20556
> Project: HBase
> Issue Type: Sub-task
> Components: HFile, snapshots
> Affects Versions: 1.4.4, 1.4.5
> Reporter: Tak Lon (Stephen) Wu
> Assignee: Tak Lon (Stephen) Wu
> Priority: Major
> Attachments: HBASE-20556.branch-1.001.patch,
> HBASE-20556.branch-1.002.patch, HBASE-20556.branch-1.003.patch
>
>
> As part of HBASE-20555, HBASE-16490 is the first patch that is needed for
> backporting HBASE-18083
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
