Hi Shawn,
So I’ve tried running MIGRATE on solr 7.3.1 using the following parameters:
1) “split.key=”
2) “split.key=!”
3) “split.key=DERP_”
4) “split.key=DERP/0!”
For 1-3, I am seeing the same ERRORs you see. For 4, I do not see any ERRORs.
Interestingly, I’m seeing this WARN message for all 4 scenarios:
org.apache.solr.common.SolrException: SolrCore not
found:split_shard2_temp_shard2_shard1_replica_n3 in [derp_shard1_replica_n1,
derp_shard2_replica_n6, herp_shard1_replica_n1, herp_shard2_replica_n6]
at
org.apache.solr.cloud.ShardLeaderElectionContext.runLeaderProcess(ElectionContext.java:312)
at
org.apache.solr.cloud.LeaderElector.runIamLeaderProcess(LeaderElector.java:170)
at org.apache.solr.cloud.LeaderElector.checkIfIamLeader(LeaderElector.java:135)
at org.apache.solr.cloud.LeaderElector.access$200(LeaderElector.java:56)
at
org.apache.solr.cloud.LeaderElector$ElectionWatcher.process(LeaderElector.java:348)
at
org.apache.solr.common.cloud.SolrZkClient$1.lambda$process$1(SolrZkClient.java:269)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
at java.util.concurrent.FutureTask.run(FutureTask.java:266)
at
org.apache.solr.common.util.ExecutorUtil$MDCAwareThreadPoolExecutor.lambda$execute$0(ExecutorUtil.java:188)
at
java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
at java.lang.Thread.run(Thread.java:748)
I wonder if this is part of the issue?
Thanks,
Matthew
On 6/22/18, 12:53 PM, "Shawn Heisey" <apa...@elyograg.org> wrote:
On 6/21/2018 9:41 AM, Matthew Faw wrote:
> Thanks for your reply. According to the MIGRATE documentation, the
split.key parameter is required, and removing it returns a missing parameter
exception. I’ve tried setting the “split.key=DERP_”, and after doing that I
still see no documents in the destination collection. Additionally, the
CLUSTERSTATUS command indicates that the routeRanges using this split key are
"routeRanges": "16f98178-16f98178", but when I use the split.key=DERP/0!, I get
the route ranges I expect (80000000-ffffffff on one shard, and 0-7fffffff on
the other).
>
> So, to me, it seems like this particular API endpoint does not work. I’d
love for someone to prove me wrong.
I have no idea how I managed to NOT see that parameter in the MIGRATE
section of the docs. I was looking through the parameter list in the
6.6 version earlier and didn't even see it there, but when I just looked
at it right now, it's there plain as day, and says it's required. I did
see it mentioned in the *text* of the MIGRATE section, just not in the
list of parameters.
The fact that this parameter is required makes no sense to me. I cannot
say for sure, but since using routing prefixes with SolrCloud is not
required, requiring a split key when migrating seems wrong to me.
I tried a test on the 7.3.0 cloud example where I manually created a
bunch of documents in one collection and then tried to do a MIGRATE with
"split.key=". I got some errors in the log:
ERROR - 2018-06-21 20:17:13.611; [ ]
org.apache.solr.update.SolrIndexSplitter; Splitting _0(7.3.0):C1: 1
documents belong to no shards and will be dropped
ERROR - 2018-06-21 20:17:13.611; [ ]
org.apache.solr.update.SolrIndexSplitter; Splitting _1(7.3.0):C1: 1
documents belong to no shards and will be dropped
ERROR - 2018-06-21 20:17:13.611; [ ]
org.apache.solr.update.SolrIndexSplitter; Splitting _3(7.3.0):C1: 1
documents belong to no shards and will be dropped
ERROR - 2018-06-21 20:17:13.611; [ ]
org.apache.solr.update.SolrIndexSplitter; Splitting _4(7.3.0):C1: 1
documents belong to no shards and will be dropped
Are you seeing ERROR or WARN in your log?
Just to be sure, I also reloaded the target collection, and I didn't see
any documents in it.
Thanks,
Shawn
The content of this email is intended solely for the individual or entity named
above and access by anyone else is unauthorized. If you are not the intended
recipient, any disclosure, copying, distribution, or use of the contents of
this information is prohibited and may be unlawful. If you have received this
electronic transmission in error, please reply immediately to the sender that
you have received the message in error, and delete it. Thank you.
