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

Bernd Fehling commented on SOLR-3011:
-------------------------------------

It works with 3.5 but after applying the SOLR-3011 patch it fails. 
I know that "threads" will be removed with 4.0 but nevertheless it is helpful 
when loading tons of data on a multi CPU machine.
I try to provide a unit test as new issue with reference to this issue.

Stupid question, if "threads" will be removed with 4.0 does this mean that the 
redesign of dataimport is multi-threading by default so that no "threads" 
parameter is needed, or will it be sized down to single-thread?


                
> DIH MultiThreaded bug
> ---------------------
>
>                 Key: SOLR-3011
>                 URL: https://issues.apache.org/jira/browse/SOLR-3011
>             Project: Solr
>          Issue Type: Sub-task
>          Components: contrib - DataImportHandler
>    Affects Versions: 3.5
>            Reporter: Mikhail Khludnev
>            Assignee: James Dyer
>            Priority: Minor
>             Fix For: 3.6
>
>         Attachments: SOLR-3011.patch, SOLR-3011.patch, SOLR-3011.patch, 
> SOLR-3011.patch, SOLR-3011.patch, 
> patch-3011-EntityProcessorBase-iterator.patch, 
> patch-3011-EntityProcessorBase-iterator.patch
>
>
> current DIH design is not thread safe. see last comments at SOLR-2382 and 
> SOLR-2947. I'm going to provide the patch makes DIH core threadsafe. Mostly 
> it's a SOLR-2947 patch from 28th Dec. 

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

        

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

Reply via email to