[ 
https://issues.apache.org/jira/browse/SOLR-14228?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Gus Heck resolved SOLR-14228.
-----------------------------
    Fix Version/s:     (was: 6.6.1)
       Resolution: Invalid

> Index size
> ----------
>
>                 Key: SOLR-14228
>                 URL: https://issues.apache.org/jira/browse/SOLR-14228
>             Project: Solr
>          Issue Type: Bug
>      Security Level: Public(Default Security Level. Issues are Public) 
>    Affects Versions: 6.6.1
>         Environment: Windows Server 2016 Datacenter (64bit con 8GB di Ram) 2 
> virtual processor
> *Versions*
>  * solr-spec 
> 6.6.1
>  * solr-impl 
> 6.6.1 9aa465a89b64ff2dabe7b4d50c472de32c298683 - varunthacker - 2017-08-29 
> 22:00:32
>  * lucene-spec 
> 6.6.1
>  * lucene-impl 
> 6.6.1 9aa465a89b64ff2dabe7b4d50c472de32c298683 - varunthacker - 2017-08-29 
> 21:54:39
>  
>            Reporter: Davide Mauri
>            Priority: Major
>         Attachments: 74847C28.PNG, 88C0F203.PNG, D41A3E09.PNG
>
>
> Good morning,
> we have a sitecore 8.2 update 5 solution that uses the Solr service for 
> indexing. We had a connection problem but we can't understand what the reason 
> is. The dedicated Solr machine has 8GB of ram and the indexes are on a 
> completely free dedicated disk. Because of this problem, the state of the 
> indexes is corrupt and we have had to recreate them thus returning to 
> function. We noticed (as can be seen from the attached files) that the size 
> of an index, before the problem, was 8 GB. Could having such large files 
> create problems at usage levels? How can we solve this problem?
> We have tried to bring the index into a test environment by recreating the 
> problem, attached is a screenshot of the Solr logs.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

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

Reply via email to