Solr Replication doesn't work after removing of the last element

[Former Member]

Hello experts,

I have the next issue:

FULL Indexing process consists of 4 steps:

• reload the core

• add all elements (with the same indexOperationId)

• remove all "old" elements (excluding the last indexOperationId)

• commit

In case of the last element removed (in backoffice) we have the next scenario:

• reload the core

• remove all "old" elements (actually, remove ALL elements) There is no commit in that case. So the last elements are not actually deleted. During the next execution of this job (or Indexing) core is reloaded during the first step and elements are removed.

We could activate force commit in solrconfig.xml. The last elements will be removed from the first execution. But even then after the commit lastModified field of the Core is not changed. Nothing is really commited. Solr slave nodes don't update this core during replication anymore and we get a state, when there are no elements on the Master server but there are some elements on Slaves. This state can be get back to the normal by manually removing of elements on slave nodes, or after addition of any new element of this type.

How could it be fixed? Thanks in advance, Igor.