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

David Smiley updated SOLR-4108:
-------------------------------

    Fix Version/s:     (was: 4.7)
                   4.8

> SolrCloud: Unexpected behavior when doing atomic updates or document 
> reindexations.
> -----------------------------------------------------------------------------------
>
>                 Key: SOLR-4108
>                 URL: https://issues.apache.org/jira/browse/SOLR-4108
>             Project: Solr
>          Issue Type: Bug
>          Components: SolrCloud
>    Affects Versions: 4.0
>         Environment: Note: This issue is related with JIRA-4080.
> Context: SolrCloud deployed with nShards=1, two Solr servers, each one with 
> two cores/collections. We have then one leader and one replica for each shard.
>            Reporter: Luis Cappa Banda
>             Fix For: 4.8
>
>
> The situation is this the following:
> 1. SolrCloud with one shard and two Solr instances.
> 2. Indexation via SolrJ with CloudServer and a custom BinaryLBHttpSolrServer 
> that uses BinaryRequestWriter to execute correctly atomic updates. Check 
> JIRA-4080.
> 3. An asynchronous proccess updates partially some document fields. After 
> that operation I automatically execute a commit, so the index must be 
> reloaded.
> What I have checked is that both using atomic updates or complete document 
> reindexations random documents are not updated even if I saw debugging how 
> the add() and commit() operations were executed correctly and without errors. 
> In other words, something strange happens when you both index and update 
> documents asynchronously at the same time.
> Also, if I debug line  by line (blocking other indexation/update proccesses) 
> and I check with my own eyes when an index operation is done, I confirm that 
> the document itself updates correctly.
> What I think is that there is some critical problem with both SolrCloud and 
> CloudSolrServer interface that has something to do with index blocking while 
> writing and forwarding document updates to replicas.
> If I´m right, and considering also JIRA-4080, I would not recommend SolrCloud 
> in production at the moment.



--
This message was sent by Atlassian JIRA
(v6.2#6252)

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

Reply via email to