Return-Path: X-Original-To: apmail-lucene-solr-user-archive@minotaur.apache.org Delivered-To: apmail-lucene-solr-user-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id AD315CAF1 for ; Fri, 12 Dec 2014 01:32:06 +0000 (UTC) Received: (qmail 63885 invoked by uid 500); 12 Dec 2014 01:31:59 -0000 Delivered-To: apmail-lucene-solr-user-archive@lucene.apache.org Received: (qmail 63810 invoked by uid 500); 12 Dec 2014 01:31:59 -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 63798 invoked by uid 99); 12 Dec 2014 01:31:58 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 12 Dec 2014 01:31:58 +0000 X-ASF-Spam-Status: No, hits=1.5 required=5.0 tests=HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS,WEIRD_PORT X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of esj.fmit@gmail.com designates 209.85.220.193 as permitted sender) Received: from [209.85.220.193] (HELO mail-vc0-f193.google.com) (209.85.220.193) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 12 Dec 2014 01:31:53 +0000 Received: by mail-vc0-f193.google.com with SMTP id hq11so624431vcb.4 for ; Thu, 11 Dec 2014 17:31:33 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; bh=Vug1fS1AlfVrvBMRTk/8nmTEpzoPuPAilTT3B4vdzo4=; b=a8HDpfPNb3pMnk8L35EALz7YsvoHZwt4fuUbHSxuIZ0mmx3EncCIHwpe47ERrwWExZ ubf88YpUMk1g83x70LmcAlS1QmnpjXpZKsv9w9NwDYN5frVS74zeNdvbnna1XDq+kF6J dELlYX6HjglRVtiOzdmM/5vhnPAD0DibcXVa5nzbwK5Rtd3+ZWyJBHHcoh68QWdDBFoy QmztS0eh7YmP3tgWfKlJuuGWTqmA9OlBV/6hbxdVykIKOMb/Y6fE13BlZdwICpxRlA9y vV5pUes0EujCgbTWC4I1Grw51Kn6C8/fw55z44r8olVlqYB+mceIpo31rImSPOOIkh1X Pekw== MIME-Version: 1.0 X-Received: by 10.220.58.133 with SMTP id g5mr9620166vch.9.1418347893070; Thu, 11 Dec 2014 17:31:33 -0800 (PST) Received: by 10.52.187.67 with HTTP; Thu, 11 Dec 2014 17:31:33 -0800 (PST) In-Reply-To: References: Date: Fri, 12 Dec 2014 14:31:33 +1300 Message-ID: Subject: Re: To understand SolrCloud configurations From: E S J To: solr-user@lucene.apache.org Content-Type: multipart/alternative; boundary=001a11c2da5455a2220509fadafa X-Virus-Checked: Checked by ClamAV on apache.org --001a11c2da5455a2220509fadafa Content-Type: text/plain; charset=UTF-8 Thanks Eric, I understand your explanation. Quick question, Are configurations sits under /configs/defaults because -configname specified as default when I execute the following command? Can I specify -configname as /c-ins/ zkcli.sh -zkhost zoo1.internal:2183,zoo2.internal:2183,zoo3.internal:2183 -cmd upconfig -confdir /collection1/conf -confname default Also I noticed that available options for -configname is default or schemaless, that is why I specified as default. Thanks, Elike On 12 December 2014 at 14:23, Erick Erickson wrote: > > bq: 1. Like to know what I have done is correct ? > Looks fine to me. > > bq: 2. Where to place the schema.xml's and other configurations. Because > for > the moment it's are under collection1/conf folder and collection1 is not an > active collection for me. ( i'm using only c-ins core) > > I think you're a bit confused here. The configuration stuff is NOT > "under collection1/conf" as far as SolrCloud is concerned, it's in > Zookeeper in /configs/default, take a look at the admin>>cloud page, > click the /configs entry and I think you'll see a "defaults" node. > > As far as SolrCloud is concerned, that's where your configs live. The > fact that they exist in /collection1/conf on your local > machine is totally irrelevant. Tomorrow, you could issue an upconfig > and use something like ".....-confdir mytotallynewdirectory/conf > -confname default" and SolrCloud would happily overwrite your configs > in the Zookeeper "default" node with the new ones, _and_ distribute > them to all the Solr nodes when they were restarted. > > So where your configs "should" live is in some kind of version > control...... > > HTH, > Erick > > On Thu, Dec 11, 2014 at 6:19 PM, E S J wrote: > > Hello Team, > > > > I would like to get clarified where to place schema.xml on SolrCloud > set-up. > > > > My Solr cloud set-up , 3 nodes, 3 shards and 3 replications, 3 ZooKeeper > > > > What I have done is, > > 1. Taken a solr.war from solr default download ( > > solr-4.10.2/example/webapps/solr.war - 4.10.2) and placed > > /webapps/ folder. > > > > 2. Taken Solr home from solr default download ( > solr-4.10.2/example/solr/) > > and placed on solr.home > > (Copied Collection folder as well along with solr.xml) > > > > 3. Started 3 solr nodes and zookeepr instances ( after correct > > configuration) > > > > 4. Register solr configurations of ZooKeeper using, > > zkcli.sh -zkhost zoo1.internal:2183,zoo2.internal:2183,zoo3.internal:2183 > > -cmd upconfig -confdir /collection1/conf -confname default > > > > 5. Create 3 Shard's and 3 Replicas : > > > http://solr1.internal:7003/solr/admin/collections?action=CREATE&name=c-ins&replicationFactor=3&numShards=3&collection.configName=default&maxShardsPerNode=3&wt=json&indent=2 > > > > > > After that I can see following folder structure in Solr node1's > > directory ( Can see similar structure on my other 2 solr > nodes) > > -rw-r--r-- solr.xml drwxrwxr-x c-ins_shard1_replica1 drwxrwxr-x > > c-ins_shard2_replica1 drwxrwxr-x c-ins_shard3_replica1 drwxr-xr-x > > collection1 > > > > > > I've done some xml docuemnt indexing and it's working fine, Zoo-keepers > are > > also working fine, My Questions are, > > > > 1. Like to know what I have done is correct ? > > 2. Where to place the schema.xml's and other configurations. Because for > > the moment it's are under collection1/conf folder and collection1 is not > an > > active collection for me. ( i'm using only c-ins core) > > > > > > Appreciate your time on this. > > > > Thanks - Elike > --001a11c2da5455a2220509fadafa--