From solr-user-return-149517-archive-asf-public=cust-asf.ponee.io@lucene.apache.org Tue Sep 3 14:48:49 2019 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 [207.244.88.153]) by mx-eu-01.ponee.io (Postfix) with SMTP id 1C1AC180637 for ; Tue, 3 Sep 2019 16:48:49 +0200 (CEST) Received: (qmail 99483 invoked by uid 500); 3 Sep 2019 16:56:15 -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 99468 invoked by uid 99); 3 Sep 2019 16:56: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; Tue, 03 Sep 2019 16:56: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 03BE0180281 for ; Tue, 3 Sep 2019 14:48:46 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd3-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -0.197 X-Spam-Level: X-Spam-Status: No, score=-0.197 tagged_above=-999 required=6.31 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H3=0.001, RCVD_IN_MSPIKE_WL=0.001, SPF_HELO_NONE=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=disabled Authentication-Results: spamd3-us-west.apache.org (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com Received: from mx1-ec2-va.apache.org ([10.40.0.8]) by localhost (spamd3-us-west.apache.org [10.40.0.10]) (amavisd-new, port 10024) with ESMTP id O8VE6n0YKzgi for ; Tue, 3 Sep 2019 14:48:44 +0000 (UTC) Received-SPF: Pass (mailfrom) identity=mailfrom; client-ip=209.85.160.177; helo=mail-qt1-f177.google.com; envelope-from=erickerickson@gmail.com; receiver= Received: from mail-qt1-f177.google.com (mail-qt1-f177.google.com [209.85.160.177]) by mx1-ec2-va.apache.org (ASF Mail Server at mx1-ec2-va.apache.org) with ESMTPS id EF05CBC7A9 for ; Tue, 3 Sep 2019 14:48:43 +0000 (UTC) Received: by mail-qt1-f177.google.com with SMTP id a13so20271737qtj.1 for ; Tue, 03 Sep 2019 07:48:43 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=from:content-transfer-encoding:mime-version:subject:date:references :to:in-reply-to:message-id; bh=gBXaeFfixfOdoKQlbuEPX8gCHZS8V7psZnebmRbOu7M=; b=rgR2wDQF6+4XXqN76296a69aoQ+3av4mJQKiC8Bdh2kOoL/Wk5US6ZJ80Q4YqU73Ei Nnt7jSBiVSwhMzlaNfkCMxM/1C6FJ/qu0MhlDvPsu7lP8nnr6NtnF32CpUSjcpz/Yh/K Z3NW7cgUaZ7KBdUEpw03m0fxNLl5AEYyvJ7jOr9Nb8P6Q+lsghcmJ/CeAydCjRtN7zyj OKQh21sXWDiBNwEfIcvgp7JEc/+RVoCMpvvLJbKroP7ZoGorGDbWs1BVLovD8pt3vZoP HBpO4JZUDyHPeLOA23b9p0e45qCX/aizkWlrT4AZQHDd4Wv32UlkPtO2fqlseA50/YIX zMeA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:from:content-transfer-encoding:mime-version :subject:date:references:to:in-reply-to:message-id; bh=gBXaeFfixfOdoKQlbuEPX8gCHZS8V7psZnebmRbOu7M=; b=oDRCGW3x6jW2h05Qt73x9WNBE65xOK48BqN3AUAzhzXVrsTGGNq8PkvidtpVDwn9Se rOWZdV/79clItrkPB5qy87zQERnbK+bp5ZD+fU2MheC7KrvKlTeCVWDqINYbUmKjuM/c vl2KK7a9mRoF19uwVCorAQKRLpsb2WiOLnM0To8QaWLc69+TiDWnOVb1dM1JTleH6p+k ZU0yp1GxM4lRPqV5FuX6UCUC1IYfMhaX+csJugfnG0iGpy9MKEMAv45apr5oLhouSNQq N4opPfaVeAvQPc9Jr3Z8vUdsh3ynliHoQHcXqQi8SejvwUb4WlryIa+7bHHWRZ2xLMtt 3UoA== X-Gm-Message-State: APjAAAWC3QhtzTRDVyDCAwyA3k0IZAM5eKDPUmDp67N9oyibt3vsBGBJ gpVFxAKqrRB9WXDn2jjQswV9GPnPTNk= X-Google-Smtp-Source: APXvYqxyz66phQJ17aDs0hbxFzhDYz/IQp9WPFPRj1Cx9qRvx0cwozor5s5zilrNclKi2SDzyPFkgg== X-Received: by 2002:a0c:f643:: with SMTP id s3mr22205122qvm.79.1567522116431; Tue, 03 Sep 2019 07:48:36 -0700 (PDT) Received: from [192.168.1.122] (pool-173-54-218-193.nwrknj.fios.verizon.net. [173.54.218.193]) by smtp.gmail.com with ESMTPSA id i23sm1732444qkl.107.2019.09.03.07.48.34 for (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Tue, 03 Sep 2019 07:48:34 -0700 (PDT) From: Erick Erickson Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Mime-Version: 1.0 (Mac OS X Mail 12.4 \(3445.104.11\)) Subject: Re: Query regarding Solr Cloud Setup Date: Tue, 3 Sep 2019 10:48:33 -0400 References: <6d3202b7-f222-a32e-aa32-b84b06551c58@elyograg.org> To: solr-user@lucene.apache.org In-Reply-To: <6d3202b7-f222-a32e-aa32-b84b06551c58@elyograg.org> Message-Id: <37E403F7-C342-4F05-B38C-F5C5C04511CD@gmail.com> X-Mailer: Apple Mail (2.3445.104.11) Having custom core.properties files is =E2=80=9Cfraught=E2=80=9D. First = of all, that file can be re-written. Second, the collections ADDREPLICA = command will create a new core.properties file. Third, any mistakes you = make when hand-editing the file can have grave consequences. What change exactly do you want to make to core.properties and why? Trying to reproduce =E2=80=9Cwhat a colleague has done on standalone=E2=80= =9D is not something I=E2=80=99d recommend, SolrCloud is a different = beast. Reproducing the _behavior_ is another thing, so what is the = behavior you want in SolrCloud that causes you to want to customize = core.properties? Best, Erick > On Sep 3, 2019, at 10:15 AM, Shawn Heisey wrote: >=20 > On 9/3/2019 7:22 AM, Porritt, Ian wrote: >> We have a schema which I have managed to upload to Zookeeper along = with the Solrconfig, how do I get the system to recognise both a = lib/.jar extension and a custom core.properties file? I bypassed the = issue of the core.properties by amending the update.autoCreateField in = the Solrconfig.xml to false however would like to include as a colleague = has done on Solr Standlone. >=20 > I cannot tell what you are asking here. The core.properties file = lives on the disk, not in ZK. >=20 > I was under the impression that .jar files could not be loaded into ZK = and used in a core config. Documentation saying otherwise was recently = pointed out to me on the list, but I remain skeptical that this actually = works, and I have not tried to implement it myself. >=20 > The best way to handle custom jar loading is to create a "lib" = directory under the solr home, and place all jars there. Solr will = automatically load them all before any cores are started, and no config = commands of any kind will be needed to make it happen. >=20 >> Also from a high availability aspect, if I effectivly lost 2 of the = Solr Servers due to an outage will the system still work as expected? = Would I expect any data loss? >=20 > If all three Solr servers have a complete copy of all your indexes, = then you should remain fully operational if two of those Solr servers go = down. >=20 > Note that if you have three ZK servers and you lose two, that means = that you have lost zookeeper quorum, and in that situation, SolrCloud = will transition to read only -- you will not be able to change any index = in the cloud. This is how ZK is designed and it cannot be changed. If = you want a ZK deployment to survive the loss of two servers, you must = have at least five total ZK servers, so more than 50 percent of the = total survives. >=20 > Thanks, > Shawn