You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@lucene.apache.org by "sdhalex (Jira)" <ji...@apache.org> on 2019/12/21 10:13:00 UTC
[jira] [Commented] (SOLR-6209) Database connections lost during
data import
[ https://issues.apache.org/jira/browse/SOLR-6209?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17001662#comment-17001662 ]
sdhalex commented on SOLR-6209:
-------------------------------
has this bug been fixed in the newest version? Or need we still do the same workaround to avoid this bug now ? Thx. [~sanket.thakkar007] [~arafalov]
> 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
> Priority: Major
> 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
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: issues-unsubscribe@lucene.apache.org
For additional commands, e-mail: issues-help@lucene.apache.org