From solr-user-return-144236-archive-asf-public=cust-asf.ponee.io@lucene.apache.org Wed Oct 3 18:45:18 2018 Return-Path: X-Original-To: archive-asf-public@cust-asf.ponee.io Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by mx-eu-01.ponee.io (Postfix) with SMTP id 45A4618065B for ; Wed, 3 Oct 2018 18:45:18 +0200 (CEST) Received: (qmail 84057 invoked by uid 500); 3 Oct 2018 16:45:16 -0000 Mailing-List: contact solr-user-help@lucene.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: solr-user@lucene.apache.org Delivered-To: mailing list solr-user@lucene.apache.org Received: (qmail 84044 invoked by uid 99); 3 Oct 2018 16:45:15 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd3-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 03 Oct 2018 16:45:15 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd3-us-west.apache.org (ASF Mail Server at spamd3-us-west.apache.org) with ESMTP id ED2521809E7 for ; Wed, 3 Oct 2018 16:45:14 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd3-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -0.102 X-Spam-Level: X-Spam-Status: No, score=-0.102 tagged_above=-999 required=6.31 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=disabled Authentication-Results: spamd3-us-west.apache.org (amavisd-new); dkim=pass (1024-bit key) header.d=elyograg.org Received: from mx1-lw-us.apache.org ([10.40.0.8]) by localhost (spamd3-us-west.apache.org [10.40.0.10]) (amavisd-new, port 10024) with ESMTP id s6YaZ2IqS5fq for ; Wed, 3 Oct 2018 16:45:13 +0000 (UTC) Received: from frodo.elyograg.org (frodo.elyograg.org [166.70.79.217]) by mx1-lw-us.apache.org (ASF Mail Server at mx1-lw-us.apache.org) with ESMTP id E439C5F358 for ; Wed, 3 Oct 2018 16:45:11 +0000 (UTC) Received: from localhost (localhost [127.0.0.1]) by frodo.elyograg.org (Postfix) with ESMTP id A4C23758 for ; Wed, 3 Oct 2018 10:45:00 -0600 (MDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=elyograg.org; h= content-language:content-transfer-encoding:content-type :content-type:in-reply-to:mime-version:user-agent:date:date :message-id:from:from:references:subject:subject:received :received; s=mail; t=1538585100; bh=DLMyG5Zfjs1gOdIK93+QTKrDZoQx IeV9HS9+ALM483U=; b=Y6V92k07yMar08GgnpBX/FZp1zu0EFVaI2kUaPLNhcnC nkxjCni5yfpmd7P5G9wYNc4L+GHkAqb0ESgFL+AQDi3Vt2zKjm+GfvhcpriyrrKr asgobqPbBIQKh3rXvw/Ko05Z9Z6BHV1y7EszyMQ3Fng8ZgVJPZb3VzRYLpJ2+4g= X-Virus-Scanned: Debian amavisd-new at frodo.elyograg.org Received: from frodo.elyograg.org ([127.0.0.1]) by localhost (frodo.elyograg.org [127.0.0.1]) (amavisd-new, port 10026) with ESMTP id GkBuiUvrvjHG for ; Wed, 3 Oct 2018 10:45:00 -0600 (MDT) Received: from [192.168.1.124] (124.int.elyograg.org [192.168.1.124]) (using TLSv1 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) (Authenticated sender: elyograg@elyograg.org) by frodo.elyograg.org (Postfix) with ESMTPSA id 3D448756 for ; Wed, 3 Oct 2018 10:45:00 -0600 (MDT) Subject: Re: Restoring and upgrading a standalone index to SolrCloud To: solr-user@lucene.apache.org References: From: Shawn Heisey Message-ID: Date: Wed, 3 Oct 2018 10:45:01 -0600 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:52.0) Gecko/20100101 Thunderbird/52.9.1 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit Content-Language: en-US On 10/3/2018 9:42 AM, Jack Schlederer wrote: > I've successfully upgraded the Lucene 5 index to Lucene 6, and then to Lucene 7, Upgrading through two major versions is not guaranteed to work.  Upgrading from an index fully built by major version X-1 is supported, but if X-2 or earlier has EVER touched the index, it's probably not going to work.  If you find that it does work, great ... but I wouldn't recommend trying it. I recommend always building indexes from scratch when upgrading, even if the new version is capable of reading the index created by the old version. > so I think I have an index that can be restored to Solr 7. Do you know if > it's possible to restore an index like this to a SolrCloud environment if I > can get it into a directory that is shared by all the nodes? Each node needs its own copy of the data, they cannot share an index directory.  Lucene works really hard to prevent sharing indexes, and this behavior should not be overridden. In general, yes, you can migrate an index (assuming it's an index that will work, note what I said above) from a non-cloud install to a cloud install.  That would be greatly complicated if the index were sharded already in the non-cloud install -- hopefully your 20GB index is one core, not multiple shards.If it's sharded ... build it from scratch, because it's not likely that the SolrCloud collection will route data to shards in precisely the same way as a non-cloud install. Here's one way to do this: * Set up your cloud, create an empty collection with one shard and as many replicas as you want. * Shut down all of the Solr nodes related to that collection. * Delete the "data" directory under all of the cores related to that collection. * Copy the data directory from the non-cloud install to one of those replica cores. * Start the Solr node where you copied the data. * Let the system fully stabilize so the replica you have just built shows up as green in the Cloud graph. * Start the other Solr nodes with the other replicas.  They will copy the index from the one that got started first. Thanks, Shawn