It appears that RESTORE pretty much ignores the configuration that was backed up by the backup command, so why does backup bother? The documented behavior of RESTORE is not very clear, and a scenario where we are restoring a collection from a backup after the configuration in the original collection has changed could lead to problems in the restored collection.
Our use case for this is where we may have to quickly revert a collection to a previous state with no down time. The fact that the restored collection may be incompatible with the latest configuration in Zookeeper could be an issue. This could be mediated by following solid processes, but sometimes administrators don't follow such guidelines in the real world. On Thu, May 11, 2017 at 9:38 AM, Webster Homer <webster.ho...@sial.com> wrote: > When I ran the backup and restore of a real collection: > sial-catalog-product which I restored to sial-catalog-product-2 I didn't > see a new config for sial-catalog-product-2 in Zookeeper. When I did what > you describe it I see the config name is sial-catalog-product not > sial-catalog-product-2 > > So was the config uploaded from the backup or is it simply the config for > sial-catalog-product which at restore time may not be the same as the > configuration that was saved? > > On Wed, May 10, 2017 at 5:20 PM, Shawn Heisey <apa...@elyograg.org> wrote: > >> On 5/10/2017 12:26 PM, Webster Homer wrote: >> > Looking at the solrcloud restore API I am confused about the solr >> > configuration >> <snip> >> > 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 is what the documentation says: >> >> == >> The collection created will be of the same number of shards and replicas >> as the original collection, preserving routing information, etc. >> Optionally, you can override some parameters documented below. While >> restoring, if a configSet with the same name exists in ZooKeeper then >> Solr will reuse that, or else it will upload the backed up configSet in >> ZooKeeper and use that. >> == >> >> Here's what I *HOPE* this means: The configuration name is saved as well >> as the actual configuration. If a configuration with the same name as >> the backed up configuration exists in zookeeper already, it will be used >> without modification, but if that config doesn't exist, the backed up >> configuration will be uploaded to zookeeper with the original config name. >> >> You seem to be assuming that the configuration will have the same name >> as the collection, and that's not what I would assume. I wonder which >> of us is right. >> >> You can check the configname being used by the restored collection by >> clicking on Cloud, then Tree, opening the "collections" folder, and >> clicking on the restored collection. It will be on the right side, >> below the table. >> >> Thanks, >> Shawn >> >> > -- 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 therewith. Click http://www.emdgroup.com/disclaimer to access the German, French, Spanish and Portuguese versions of this disclaimer.
