Re: Different docs order in different replicas of the same shard

I think that I found very simple solution: to set my updateProcessorsChain to default="true" and it is solving all my problems without moving all post-updateprocessors to be pre-updateprocessors. What do you think about it? -- Sent from: http://lucene.472066.n3.nabble.com/Solr-User-f472068.ht

Re: Different docs order in different replicas of the same shard

I thought about next solution for the my problem: Atomic Update + Replicas. I can set my *UpdateProcessorsChain* in the next order: .. . MergerUpdateProcessor will use getUpdatedDocument function of DistibutedUpdateProcessor

Re: Different docs order in different replicas of the same shard

On 5/25/2018 11:07 AM, SOLR4189 wrote: > You are right, BUT I have two indexers (one in WCF service and one in HADOOP) > and in two my indexers I'm using atomic updates in each document. According > to Atomic Update Processor Factory >

Re: Different docs order in different replicas of the same shard

You are right, BUT I have two indexers (one in WCF service and one in HADOOP) and in two my indexers I'm using atomic updates in each document. According to Atomic Update Processor Factory and according to your solution (t

Re: Different docs order in different replicas of the same shard

On 5/25/2018 7:28 AM, SOLR4189 wrote: > I use SOLR-6.5.1 and I want to start to use replicas. > > For it I want to understand something: > > 1) Can asynchronous forwarding document from leader to all replicas or some > another reasons cause that replica A may see update X then Y, and replica B > ma

Re: Different docs order in different replicas of the same shard

For (1), it's not a problem. Every update goes through the leader, where it gets a version stamp (the _version_ field). So if doc1 is updated twice the leader will assign a version stamp. Call the updated doc1.1 and doc1.2. If replica X sees doc1.2 first, it indexes it. If it subsequently sees doc1