Erick Erickson created SOLR-12646:
-------------------------------------
Summary: Splitting a shard that has been touched by 6x fails with
7x.
Key: SOLR-12646
URL: https://issues.apache.org/jira/browse/SOLR-12646
Project: Solr
Issue Type: Bug
Security Level: Public (Default Security Level. Issues are Public)
Reporter: Erick Erickson
Steps to reproduce on Solr Cloud:
* create a 1-shard collection (I used 6.6).
* make sure it has more than one segment so optimize rewrites.
* upgrade to 7x
* optimize
* splitshard
This fails. It never returns. Now when I restart Solr, it tries to split the
shard and fails with:
{quote}2018-08-08 18:21:07.100 WARN (OverseerThreadFactory-9-thread-3)
[c:tech2 s:shard1 ] o.a.s.c.OverseerTaskProcessor Resetting task:
/overseer/collection-queue-work/qn-0000000006, requestid: null, taskKey: tech2
2018-08-08 18:21:07.100 ERROR (OverseerThreadFactory-9-thread-3) [c:tech2
s:shard1 ] o.a.s.c.u.ExecutorUtil Uncaught exception
java.lang.NoClassDefFoundError: Could not initialize class
org.apache.solr.client.solrj.cloud.autoscaling.Variable$Type thrown by thread:
OverseerThreadFactory-9-thread-3
java.lang.Exception: Submitter stack trace
at
org.apache.solr.common.util.ExecutorUtil$MDCAwareThreadPoolExecutor.execute(ExecutorUtil.java:184)
~[solr-solrj-7.5.0-SNAPSHOT.jar:7.5.0-SNAPSHOT
d087f9f1ef065b449c93514e21c859e6dd0f7ad7 - Erick - 2018-08-08 10:11:27]
at
org.apache.solr.cloud.OverseerTaskProcessor.run(OverseerTaskProcessor.java:302)
~[solr-core-7.5.0-SNAPSHOT.jar:7.5.0-SNAPSHOT
d087f9f1ef065b449c93514e21c859e6dd0f7ad7 - Erick - 2018-08-08 10:11:25]
at java.lang.Thread.run(Thread.java:748) [?:1.8.0_181]
{quote}
I _think_ the error is coming from SolrClientStateProvider [250], this line:
{{if (requestedTags.contains(TOTALDISK.tagName)) {}}
We get nothing interesting in the Solr logs and wind up back at
OverseerTaskProcesssor [511], this line:
resetTaskWithException(messageHandler, head.getId(), asyncId, taskKey, message);
RELATED:
The original question was on the user's list. The user had a single-shard
stand-alone collection that had at least some segments created with 6x and:
* created a 7x single-shard collection
* copied the 6x stand-alone index to "the right place"
* verified they could search
* optimized (verified that there was more than one segment before optimizing)
* tried SPLITSHARD
On their version of 7 (7.1), they got a message:
java.lang.IllegalArgumentException: Cannot merge a segment that has been
created with major version 6 into this index which has been created by
major version 7"}
I got a different message with 7x, but it still failed. I mention this because
it might underlie the cloud->cloud migration and/or be an issue we'll run into
once the cloud->cloud failure is addressed.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
