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

Alexandre Rafalovitch closed SOLR-6209.
---------------------------------------
    Resolution: Workaround

Unknown Solr version, old version of 3rd party product (database) and possible 
workaround provided.

I am closing this issue. If this still happens with latest Solr version, I 
recommend opening a new issue with updated details and information on 
product/component versions.

> Database connections lost during data import
> --------------------------------------------
>
>                 Key: SOLR-6209
>                 URL: https://issues.apache.org/jira/browse/SOLR-6209
>             Project: Solr
>          Issue Type: Bug
>         Environment: OS: Windows 7
> RAM: 8 GB
>            Reporter: SANKET
>              Labels: solr
>   Original Estimate: 30h
>  Remaining Estimate: 30h
>
> Follow the steps to generate the error:
> 1. Configure the large amount of data (around 4  GB  or more than 50 millions 
> of records)
> 2. Give proper data-config.xml file for indexing the data from remote 
> database server.
> 3. During indexing the data into solr from SQL SERVER 2010, at the half way 
> unplug the network cable and see the status in solr.
> e.g.
> localhost:8083/solr/core1/dataimport?command=status
> or
> localhost:8083/solr/core1/dataimport
> 4. Pass few seconds then again plug back the cable.
> 5. You can clearly see that there is just only "Time Elapsed" parameter 
> increase. "Total Rows Fetched" & "Total Documents Processed" remains same for 
> infinite time.
> 6. You can regenerate this for small data also.
> 7. Work around is you need to restart the solr. (But this is not good 
> solution)
> Note:
> This is very important issue because, so many organizations not using this 
> valuable products just because of the this database infinite connection issue.
> Solution can be: Forcefully abort the data indexing or provide mechanism for 
> forcefully abort the indexing.
> Hope you guys knows that abort command is also not working.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org

Reply via email to