You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@flume.apache.org by "jiraposter@reviews.apache.org (Commented) (JIRA)" <ji...@apache.org> on 2011/11/24 21:22:41 UTC
[jira] [Commented] (FLUME-816) TestJdbcChannelProvider throws OOME
based on RNG values
[ https://issues.apache.org/jira/browse/FLUME-816?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13156894#comment-13156894 ]
jiraposter@reviews.apache.org commented on FLUME-816:
-----------------------------------------------------
-----------------------------------------------------------
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/2930/
-----------------------------------------------------------
Review request for Flume and Eric Sammer.
Summary
-------
Fix for FLUME-816
This addresses bug FLUME-816.
https://issues.apache.org/jira/browse/FLUME-816
Diffs
-----
.gitignore c319325
flume-ng-channels/flume-jdbc-channel/pom.xml 8665eee
Diff: https://reviews.apache.org/r/2930/diff
Testing
-------
Ran all JDBC channel tests on a different system where I was able to see the OOM errors. With this change, the tests pass.
Thanks,
Arvind
> TestJdbcChannelProvider throws OOME based on RNG values
> -------------------------------------------------------
>
> Key: FLUME-816
> URL: https://issues.apache.org/jira/browse/FLUME-816
> Project: Flume
> Issue Type: Bug
> Components: Technical Debt, Test
> Affects Versions: NG alpha 1
> Reporter: E. Sammer
> Assignee: Arvind Prabhakar
> Fix For: NG alpha 2
>
> Attachments: FLUME-816-1.patch
>
>
> TestJdbcChannelProvider uses a random number to test header overflow. This causes the JVM running the tests to sometimes die from an OOME. We should cap the test so overflows the header table value field size but stays within a reasonable limit. I've been able to verify this by increasing the maven test JVM heap size to values > 128MB (or more).
--
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