Hi All - I just ran the REPLACENODE command on a cluster with 5 nodes in
it. I ran the command async, and it failed with:
{
"responseHeader":{
"status":0,
"QTime":11},
"Operation replacenode caused
exception:":"java.util.concurrent.RejectedExecutionException:java.util.concurrent.RejectedExecutionException:
Task
org.apache.solr.common.util.ExecutorUtil$MDCAwareThreadPoolExecutor$$Lambda$52/1374786673@18107b06
rejected from org.apache.solr.common.util.ExecutorUtil$MDCAwareThreadPoolExecutor@2c993425[Running,
pool size = 10, active threads = 10, queued tasks = 0, completed tasks = 0]",
"exception":{
"msg":"Task
org.apache.solr.common.util.ExecutorUtil$MDCAwareThreadPoolExecutor$$Lambda$52/1374786673@18107b06
rejected from org.apache.solr.common.util.ExecutorUtil$MDCAwareThreadPoolExecutor@2c993425[Running,
pool size = 10, active threads = 10, queued tasks = 0, completed tasks = 0]",
"rspCode":-1},
"status":{
"state":"failed",
"msg":"found [1234] in failed tasks"}}
Prior to running the command, each shard had two replicas. Now some shards
have 4, and some 3. In addition the auto scaling policy of:
cluster-policy":[{
"replica":"<2",
"shard":"#EACH",
"node":"#ANY"}],
seems to be ignored as many collections have the same node hosting multiple
replicas. Is this related to JIRA:
https://issues.apache.org/jira/browse/SOLR-13586
?
Thank you!
-Joe
