[ 
https://issues.apache.org/jira/browse/SOLR-4092?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13499906#comment-13499906
 ] 

Shawn Heisey commented on SOLR-4092:
------------------------------------

In order to be affected by this, the user must be running running Solr 4.1 with 
no ramBufferSizeMB in their config.

With the Solr upgrade from 3.x, Solr's memory footprint will be drastically 
altered no matter what happens with the default ramBufferSizeMB.  In many cases 
that footprint will be significantly smaller than it was before, so any change 
from this increase may be in the noise.  The user may be surprised by new index 
segments that are suddenly much larger, but since it comes with better 
performance, I doubt there would be any major fallout.

My bias is to change the test, and leave ramBufferSizeMB at 100 for all 
luceneMatchVersion values.  Or you could appeal to binary perfection and make 
it 128. :)

                
> Test failure in org.apache.solr.core.TestConfig.testDefaults31
> --------------------------------------------------------------
>
>                 Key: SOLR-4092
>                 URL: https://issues.apache.org/jira/browse/SOLR-4092
>             Project: Solr
>          Issue Type: Bug
>    Affects Versions: 4.1
>            Reporter: Shawn Heisey
>             Fix For: 4.1
>
>         Attachments: SOLR-4092-code.patch, SOLR-4092-test.patch
>
>
> Checkout of branch_4x on 2012/11/18 at about 19:00 UTC.
> [junit4:junit4] FAILURE 0.21s | TestConfig.testDefaults31 <<<
> [junit4:junit4]    > Throwable #1: java.lang.AssertionError: default 
> ramBufferSizeMB should be 16
> [junit4:junit4]    >    at 
> __randomizedtesting.SeedInfo.seed([25295D05EC822830:3C3BA9C90D30C561]:0)
> [junit4:junit4]    >    at org.junit.Assert.fail(Assert.java:93)
> [junit4:junit4]    >    at org.junit.Assert.assertTrue(Assert.java:43)
> [junit4:junit4]    >    at 
> org.apache.solr.core.TestConfig.testDefaults31(TestConfig.java:152)
> <snip>

--
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

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to