lucene-solr-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Webster Homer <>
Subject solrcloud collections restore documentation is confusing about the restored configset
Date Wed, 10 May 2017 18:26:53 GMT
Looking at the solrcloud restore API I am confused about the solr
What configuration gets loaded into the restored collection? The one in
Zookeeper or the one from the backup?

Say I have a collection,  BAZ which has a configuration BAZ.config
Now I create a backup of BAZ
I make changes to the BAZ configuration, load updated data into BAZ.

I then discover a problem with the updated BAZ so I restore BAZ to BAZ-Old

I didn't see a new config in Zookeeper named BAS-Old
Did the restore replace the BAZ.config with the config from the backup? or
is BAZ-Old now using the modified config that BAZ is using.

The RESTORE says that you can specify a config name but the config must
already be in Zookeeper.

So what is the real story and can the documentation be made clearer?

It seems to me that the restore should create a new configset in Zookeeper
from the backed up configset and use the new collection name as the name of
the config set.


This message and any attachment are confidential and may be privileged or 
otherwise protected from disclosure. If you are not the intended recipient, 
you must not copy this message or attachment or disclose the contents to 
any other person. If you have received this transmission in error, please 
notify the sender immediately and delete the message and any attachment 
from your system. Merck KGaA, Darmstadt, Germany and any of its 
subsidiaries do not accept liability for any omissions or errors in this 
message which may arise as a result of E-Mail-transmission or for damages 
resulting from any unauthorized changes of the content of this message and 
any attachment thereto. Merck KGaA, Darmstadt, Germany and any of its 
subsidiaries do not guarantee that this message is free of viruses and does 
not accept liability for any damages caused by any virus transmitted 

Click to access the German, French, 
Spanish and Portuguese versions of this disclaimer.

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message