lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Alberto Ferrini (JIRA)" <>
Subject [jira] [Commented] (SOLR-8635) Shards don't propagate the document update correctly
Date Thu, 04 Feb 2016 08:35:39 GMT


Alberto Ferrini commented on SOLR-8635:

Sorry Eric, I didn't know about the user's list.
Yes, I have committed the change, but the inconsistency remains.

I confirm that the creation of a new document or the deletion work correctly, only the update
from shard that not contains the document seems wrong.

I attached the access log during the described operations.



> Shards don't propagate the document update correctly
> ----------------------------------------------------
>                 Key: SOLR-8635
>                 URL:
>             Project: Solr
>          Issue Type: Bug
>          Components: SolrCloud
>    Affects Versions: 5.4.1
>         Environment: - Red Hat Enterprise Linux Server release 5.6 (Tikanga)
> - Oracle jdk1.7.0_79
> - Apache Solr 5.4.1
> - Apache Zookeeper 3.4.6
>            Reporter: Alberto Ferrini
>              Labels: shard, solrcloud, update
>         Attachments: access_log.txt, schema.xml, solrconfig.xml, zoo.cfg
> I created a SolrCloud infrastructure with 2 shards and 1 leader and 2 reaplicas for each
shard: Zookeeper is deployed in an external ensemble.
> When I add a new document, or when I delete an existing document, all works correctly.
> But when I update an existent document, the field value is not correctly propagated between
the shards, with inconsistency of the index (the query result for that document shows sometimes
the new value, sometimes the old value: I see the value because the field is stored).
> Example for the reproduction of the issue:
> - Create document with id "List" and field PATH with value 1 on shard *1*.
> - Query for document (ID:List) -> All OK
> - Create document with id "List" and field PATH with value 2 on shard *2* (document update).
> - Query for document (ID:List) -> Issue: sometimes answers with value 1, sometimes
answers with value 2

This message was sent by Atlassian JIRA

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message