Solr Backup restore

[Mohammed Farhan Ejaz <fa...@gmail.com>]

Hello,

I have a Solr Cloud with 2 node cluster. It has 2 replicas one on each node
with a single shard.

The cores created are <<collection_name>>_shard1_replica1 and
<<collection_name>>_shard1_replica2.

When I create a collection back up and restore the documents are indexed
properly on both the nodes, but the cores created are
<<collection_name>>_shard1_replica0 and
<<collection_name>>_shard1_replica1

Additionally, when I delete or add documents it gets only deleted from one
node which means the replication does not work. I noticed on one node I do
not have the index folder on one of the nodes from where document is not
getting deleted or added.

What could I be possibly doing wrong?

Re: Solr Backup restore

[David Smiley <da...@gmail.com>]

It would help if you could devise a simple set of command line steps to
reproduce/demonstrate the problem using the "bin/solr -e solrcloud" setup.
The problem you see ought to be reproducible here if there is a problem.

~ David Smiley
Apache Lucene/Solr Search Developer
http://www.linkedin.com/in/davidwsmiley


On Thu, Sep 12, 2019 at 10:13 AM Mohammed Farhan Ejaz <fa...@gmail.com>
wrote:

> Hello,
>
> I have a Solr Cloud with 2 node cluster. It has 2 replicas one on each node
> with a single shard.
>
> The cores created are <<collection_name>>_shard1_replica1 and
> <<collection_name>>_shard1_replica2.
>
> When I create a collection back up and restore the documents are indexed
> properly on both the nodes, but the cores created are
> <<collection_name>>_shard1_replica0 and
> <<collection_name>>_shard1_replica1
>
> Additionally, when I delete or add documents it gets only deleted from one
> node which means the replication does not work. I noticed on one node I do
> not have the index folder on one of the nodes from where document is not
> getting deleted or added.
>
> What could I be possibly doing wrong?
>