Tom,
Thank you for trying out bunch of things with CDCR setup. I am successfully
able to replicate the exact issue on my setup, this is a problem.
I have opened a JIRA for the same:
https://issues.apache.org/jira/browse/SOLR-11724. Feel free to add any
relevant details as you like.
Amrit Sarkar
Not sure how it's possible. But I also tried using the _default config and just
adding in the source and target configuration to make sure I didn't have
something wonky in my custom solrconfig that was causing this issue. I can
confirm that until I restart the follower nodes, they will not
Tom,
(and take care not to restart the leader node otherwise it will replicate
> from one of the replicas which is missing the index).
How is this possible? Ok I will look more into it. Appreciate if someone
else also chimes in if they have similar issue.
Amrit Sarkar
Search Engineer
Hi Amrit, I tried issuing hard commits to the various nodes in the target
cluster and it does not appear to cause the follower replicas to receive the
initial index. The only way I can get the replicas to see the original index is
by restarting those nodes (and take care not to restart the
Tom,
This is very useful:
> I found a way to get the follower replicas to receive the documents from
> the leader in the target data center, I have to restart the solr instance
> running on that server. Not sure if this information helps at all.
You have to issue hardcommit on target after the
Hi Amrit,
Starting with more documents doesn't appear to have made a difference. This
time I tried with >1000 docs. Here are the steps I took:
1. Deleted the collection on both the source and target DCs.
2. Recreated the collections.
3. Indexed >1000 documents on source data center, hard
Hi Tom,
I see what you are saying and I too think this is a bug, but I will confirm
once on the code. Bootstrapping should happen on all the nodes of the
target.
Meanwhile can you index more than 100 documents in the source and do the
exact same experiment again. Followers will not copy the
I'm running into an issue with the initial CDCR bootstrapping of an existing
index. In short, after turning on CDCR only the leader replica in the target
data center will have the documents replicated and it will not exist in any of
the follower replicas in the target data center. All
