I've not seen this happen ... did your Solr pod get killed during this
operation? I'm not sure if this copy operation could be done as a
multi given the jute buffer limitations (iirc, the total size of all
setData for a multi must be under the jute buffer size) ... so it's
possible to end up with a partially created configset in ZK ...

On Mon, Jun 21, 2021 at 1:21 PM Joel Bernstein <[email protected]> wrote:
>
> I was deploying the solr-operator in GKE and everything worked as expected 
> except for one error and I was wondering if others had come across this. I 
> was using the same commands and example deployment described here: 
> https://solr.apache.org/operator/articles/explore-v030-gke.html.
>
> The _default configSet didn't fully load so a collection referencing this 
> configSet fails. The logs from the pod that loaded the _default config are 
> below. You'll see that only a few files from lang dir are loaded and the 
> collection creation failed. I re-uploaded the config from inside the pod and 
> it worked fine. Could this be a race condition with the initial configSet 
> load? Anyone else run into this?
>
> 2021-06-21 18:33:27.954 INFO  
> (OverseerThreadFactory-22-thread-1-processing-n:explore-solrcloud-2.explore-solrcloud-headless.default:8983_solr)
>  [   ] o.a.s.c.c.ZkConfigManager Copying zk node /configs/_default to 
> /configs/testcol.AUTOCREATED
> 2021-06-21 18:33:27.965 INFO  
> (OverseerThreadFactory-22-thread-1-processing-n:explore-solrcloud-2.explore-solrcloud-headless.default:8983_solr)
>  [   ] o.a.s.c.c.ZkConfigManager Copying zk node 
> /configs/_default/managed-schema to 
> /configs/testcol.AUTOCREATED/managed-schema
> 2021-06-21 18:33:27.984 INFO  
> (OverseerThreadFactory-22-thread-1-processing-n:explore-solrcloud-2.explore-solrcloud-headless.default:8983_solr)
>  [   ] o.a.s.c.c.ZkConfigManager Copying zk node 
> /configs/_default/solrconfig.xml to 
> /configs/testcol.AUTOCREATED/solrconfig.xml
> 2021-06-21 18:33:28.004 INFO  
> (OverseerThreadFactory-22-thread-1-processing-n:explore-solrcloud-2.explore-solrcloud-headless.default:8983_solr)
>  [   ] o.a.s.c.c.ZkConfigManager Copying zk node 
> /configs/_default/lang/stopwords_hu.txt to 
> /configs/testcol.AUTOCREATED/lang/stopwords_hu.txt
> 2021-06-21 18:33:28.025 INFO  
> (OverseerThreadFactory-22-thread-1-processing-n:explore-solrcloud-2.explore-solrcloud-headless.default:8983_solr)
>  [   ] o.a.s.c.c.ZkConfigManager Copying zk node 
> /configs/_default/lang/stopwords_fi.txt to 
> /configs/testcol.AUTOCREATED/lang/stopwords_fi.txt
> 2021-06-21 18:33:28.046 INFO  
> (OverseerThreadFactory-22-thread-1-processing-n:explore-solrcloud-2.explore-solrcloud-headless.default:8983_solr)
>  [   ] o.a.s.c.c.ZkConfigManager Copying zk node 
> /configs/_default/lang/stopwords_el.txt to 
> /configs/testcol.AUTOCREATED/lang/stopwords_el.txt
> 2021-06-21 18:34:30.667 INFO  (qtp1111613684-17) [   
> x:testcol_shard2_replica_n2] o.a.s.h.a.CoreAdminOperation core create command 
> qt=/admin/cores&coreNodeName=core_node5&collection.configName=_default&newCollection=true&name=testcol_shard2_replica_n2&action=CREATE&numShards=3&collection=testcol&shard=shard2&wt=javabin&version=2&replicaType=NRT
>
> 2021-06-21 18:34:30.796 ERROR 
> (OverseerThreadFactory-22-thread-2-processing-n:explore-solrcloud-2.explore-solrcloud-headless.default:8983_solr)
>  [ ] o.a.s.c.a.c.OverseerCollectionMessageHandler Error from shard: 
> http://explore-solrcloud-0.explore-solrcloud-headless.default:8983/solr => 
> org.apache.solr.client.solrj.impl.HttpSolrClient$RemoteSolrException: Error 
> from server at 
> http://explore-solrcloud-0.explore-solrcloud-headless.default:8983/solr: 
> Error CREATEing SolrCore 'testcol_shard1_replica_n1': Unable to create core 
> [testcol_shard1_replica_n1] Caused by: Can't find resource 
> 'lang/contractions_it.txt' in classpath or '/configs/_default', 
> cwd=/opt/solr-8.8.2/server
>
>
>
>
>
> Joel Bernstein
> http://joelsolr.blogspot.com/

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to