You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@flume.apache.org by "E. Sammer (Created) (JIRA)" <ji...@apache.org> on 2011/10/23 22:04:32 UTC

[jira] [Created] (FLUME-816) TestJdbcChannelProvider throws OOME based on RNG values

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
             Fix For: NG alpha 2


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

        

[jira] [Updated] (FLUME-816) TestJdbcChannelProvider throws OOME based on RNG values

Posted by "Arvind Prabhakar (Updated) (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/FLUME-816?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Arvind Prabhakar updated FLUME-816:
-----------------------------------

    Attachment: FLUME-816-1.patch
    
> 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

        

[jira] [Commented] (FLUME-816) TestJdbcChannelProvider throws OOME based on RNG values

Posted by "jiraposter@reviews.apache.org (Commented) (JIRA)" <ji...@apache.org>.
    [ 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

        

[jira] [Updated] (FLUME-816) TestJdbcChannelProvider throws OOME based on RNG values

Posted by "Arvind Prabhakar (Updated) (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/FLUME-816?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Arvind Prabhakar updated FLUME-816:
-----------------------------------

    Resolution: Fixed
        Status: Resolved  (was: Patch Available)

Patch committed.
                
> 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

        

[jira] [Updated] (FLUME-816) TestJdbcChannelProvider throws OOME based on RNG values

Posted by "Arvind Prabhakar (Updated) (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/FLUME-816?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Arvind Prabhakar updated FLUME-816:
-----------------------------------

    Status: Patch Available  (was: Open)

This change takes care of increasing the default heap size for JDBC channel tests.
                
> 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

        

[jira] [Commented] (FLUME-816) TestJdbcChannelProvider throws OOME based on RNG values

Posted by "Hudson (Commented) (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/FLUME-816?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13160259#comment-13160259 ] 

Hudson commented on FLUME-816:
------------------------------

Integrated in flume-728 #63 (See [https://builds.apache.org/job/flume-728/63/])
    FLUME-816. Increasing the heap size for running JDBC channel tests.

arvind : http://svn.apache.org/viewvc/?view=rev&rev=1208655
Files : 
* /incubator/flume/branches/flume-728/.gitignore
* /incubator/flume/branches/flume-728/flume-ng-channels/flume-jdbc-channel/pom.xml

                
> 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

        

[jira] [Assigned] (FLUME-816) TestJdbcChannelProvider throws OOME based on RNG values

Posted by "Arvind Prabhakar (Assigned) (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/FLUME-816?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Arvind Prabhakar reassigned FLUME-816:
--------------------------------------

    Assignee: Arvind Prabhakar
    
> 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
>
>
> 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

        

[jira] [Commented] (FLUME-816) TestJdbcChannelProvider throws OOME based on RNG values

Posted by "jiraposter@reviews.apache.org (Commented) (JIRA)" <ji...@apache.org>.
    [ https://issues.apache.org/jira/browse/FLUME-816?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13160200#comment-13160200 ] 

jiraposter@reviews.apache.org commented on FLUME-816:
-----------------------------------------------------


-----------------------------------------------------------
This is an automatically generated e-mail. To reply, visit:
https://reviews.apache.org/r/2930/#review3582
-----------------------------------------------------------

Ship it!


lgtm!

- Eric


On 2011-11-24 20:22:06, Arvind Prabhakar wrote:
bq.  
bq.  -----------------------------------------------------------
bq.  This is an automatically generated e-mail. To reply, visit:
bq.  https://reviews.apache.org/r/2930/
bq.  -----------------------------------------------------------
bq.  
bq.  (Updated 2011-11-24 20:22:06)
bq.  
bq.  
bq.  Review request for Flume and Eric Sammer.
bq.  
bq.  
bq.  Summary
bq.  -------
bq.  
bq.  Fix for FLUME-816
bq.  
bq.  
bq.  This addresses bug FLUME-816.
bq.      https://issues.apache.org/jira/browse/FLUME-816
bq.  
bq.  
bq.  Diffs
bq.  -----
bq.  
bq.    .gitignore c319325 
bq.    flume-ng-channels/flume-jdbc-channel/pom.xml 8665eee 
bq.  
bq.  Diff: https://reviews.apache.org/r/2930/diff
bq.  
bq.  
bq.  Testing
bq.  -------
bq.  
bq.  Ran all JDBC channel tests on a different system where I was able to see the OOM errors. With this change, the tests pass.
bq.  
bq.  
bq.  Thanks,
bq.  
bq.  Arvind
bq.  
bq.


                
> 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