[
https://issues.apache.org/jira/browse/SOLR-4670?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Cassandra Targett resolved SOLR-4670.
-------------------------------------
Resolution: Invalid
I think this should be resolved. Not because there's been some great change and
we're sure there aren't _any_ concurrency issues, but instead because the use
case as presented here creates individual cores in a SolrCloud installation
(instead of collections) and we explicitly document this as not supported (in
several places in the Ref Guide). If we have concurrency issues today we should
file new issues using the current accepted best practices for collection
creation.
> Core mismatch in concurrent documents creation
> ----------------------------------------------
>
> Key: SOLR-4670
> URL: https://issues.apache.org/jira/browse/SOLR-4670
> Project: Solr
> Issue Type: Bug
> Components: multicore, SolrCloud
> Affects Versions: 4.0, 4.1, 4.2, 4.2.1
> Environment: CPU: 32x AMD Opteron(TM) Processor 6276
> RAM: 132073620 kB
> OS: Red Hat Enterprise Linux Server release 5.7 (Tikanga)
> JDK 1.6.0_21
> JBoss [EAP] 4.3.0.GA_CP09
> Apache Solr 4.x
> Apache ZooKeeper 3.4.5
> Reporter: Alberto Ferrini
> Priority: Major
> Labels: concurrency, multicore, solrcloud, zookeeper
>
> The issue can be reproduced in this way:
> - Install SolrCloud with at least 2 nodes
> - Install ZooKeeper with at least 2 nodes
> - Create 30 cores
> - After each core creation, create 20 random generated documents in a random
> existent core with 2 concurrent threads on all solr nodes (for example,
> document 1 in core 3 on node 1, document 2 in core 5 on node 1, document 3 in
> core 3 on node 2, etc...).
> - After all cores creation, query each core for all documents and compare
> insert data with query result
> Some documents result in different core than they are created.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
