Return-Path: 
 <solr-user-return-118850-apmail-lucene-solr-user-archive=lucene.apache.org@lucene.apache.org>
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 D099C18B20
	for <apmail-lucene-solr-user-archive@minotaur.apache.org>;
 Mon, 14 Dec 2015 17:49:57 +0000 (UTC)
Received: (qmail 26901 invoked by uid 500); 14 Dec 2015 17:49:53 -0000
Delivered-To: apmail-lucene-solr-user-archive@lucene.apache.org
Received: (qmail 26829 invoked by uid 500); 14 Dec 2015 17:49:53 -0000
Mailing-List: contact solr-user-help@lucene.apache.org; run by ezmlm
Precedence: bulk
List-Help: <mailto:solr-user-help@lucene.apache.org>
List-Unsubscribe: <mailto:solr-user-unsubscribe@lucene.apache.org>
List-Post: <mailto:solr-user@lucene.apache.org>
List-Id: <solr-user.lucene.apache.org>
Reply-To: solr-user@lucene.apache.org
Delivered-To: mailing list solr-user@lucene.apache.org
Received: (qmail 26817 invoked by uid 99); 14 Dec 2015 17:49:53 -0000
Received: from Unknown (HELO spamd3-us-west.apache.org) (209.188.14.142)
    by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 14 Dec 2015 17:49:53 +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 F311E180455
	for <solr-user@lucene.apache.org>; Mon, 14 Dec 2015 17:49:52 +0000 (UTC)
X-Virus-Scanned: Debian amavisd-new at spamd3-us-west.apache.org
X-Spam-Flag: NO
X-Spam-Score: -0.121
X-Spam-Level: 
X-Spam-Status: No, score=-0.121 tagged_above=-999 required=6.31
	tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1,
	RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001]
	autolearn=disabled
Authentication-Results: spamd3-us-west.apache.org (amavisd-new);
	dkim=pass (2048-bit key) header.d=googlemail.com
Received: from mx1-eu-west.apache.org ([10.40.0.8])
	by localhost (spamd3-us-west.apache.org [10.40.0.10]) (amavisd-new,
 port 10024)
	with ESMTP id agBAE5dtzwm9 for <solr-user@lucene.apache.org>;
	Mon, 14 Dec 2015 17:49:52 +0000 (UTC)
Received: from mail-lf0-f49.google.com (mail-lf0-f49.google.com
 [209.85.215.49])
	by mx1-eu-west.apache.org (ASF Mail Server at mx1-eu-west.apache.org) with
 ESMTPS id A069920D14
	for <solr-user@lucene.apache.org>; Mon, 14 Dec 2015 17:49:51 +0000 (UTC)
Received: by lfcy184 with SMTP id y184so53315947lfc.1
        for <solr-user@lucene.apache.org>;
 Mon, 14 Dec 2015 09:49:45 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=googlemail.com; s=20120113;
        h=mime-version:date:message-id:subject:from:to:content-type;
        bh=49Vpoh8oNOP17CI8n46fQTEc0MaJuaEeY8rW+Ld59PE=;
        b=vm9Cxkdw9CFZBiYKzuJdLjf+yW1C2gs6jHNvdq3XYRQOWZW3iQtlOhIorswoxUMwSH
         +59cmf8BUZTwEUF1zygf4hxXk2NnJVWfuDQs/WaBN06EEBWECx/4a//pV144FGbwhfge
         Ysyboz5ydNwZrl0Wz4mldosk5xDLxI2zSFE1/Wqaoeu1lEZYWbsS7yebrok9gK6AK+pJ
         NXsDvLnFPWtY0s4C7/AClGW1Prah/9go1DS/uNYpnQOHEJGS+HMB8eODkzvaM1Hb2EHz
         QcXVuL0Nzu9tcwv+SGFUJ7Bnmp03uGHiBqtf2/Ev4pFoibOYNcc6hobMrpYUi7UR8X0G
         dBBA==
MIME-Version: 1.0
X-Received: by 10.25.78.17 with SMTP id c17mr5974728lfb.47.1450115385630; Mon,
 14 Dec 2015 09:49:45 -0800 (PST)
Received: by 10.25.84.134 with HTTP; Mon, 14 Dec 2015 09:49:45 -0800 (PST)
Date: Mon, 14 Dec 2015 11:49:45 -0600
Message-ID: 
 <CAFHbX1KBA0WGWPf8XOKKtdQ6Yh9g4nU85bb=dK3dNmvi-RF_Vw@mail.gmail.com>
Subject: Moving to SolrCloud, specifying dataDir correctly
From: Tom Evans <tevans.uk@googlemail.com>
To: solr-user@lucene.apache.org
Content-Type: text/plain; charset=UTF-8

Hi all

We're currently in the process of migrating our distributed search
running on 5.0 to SolrCloud running on 5.4, and setting up a test
cluster for performance testing etc.

We have several cores/collections, and in each core's solrconfig.xml,
we were specifying an empty <dataDir>, and specifying the same
core.baseDataDir in core.properties.

When I tried this in SolrCloud mode, specifying
"-Dsolr.data.dir=/mnt/solr/" when starting each node, it worked fine
for the first collection, but then the second collection tried to use
the same directory to store its index, which obviously failed. I fixed
this by changing solrconfig.xml in each collection to specify a
specific directory, like so:

  <dataDir>${solr.data.dir:}products</dataDir>

Looking back after the weekend, I'm not a big fan of this. Is there a
way to add a core.properties to ZK, or a way to specify
core.baseDatadir on the command line, or just a better way of handling
this that I'm not aware of?

Cheers

Tom