Return-Path: X-Original-To: apmail-lucene-solr-commits-archive@minotaur.apache.org Delivered-To: apmail-lucene-solr-commits-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 57B767202 for ; Wed, 31 Aug 2011 20:28:01 +0000 (UTC) Received: (qmail 94354 invoked by uid 500); 31 Aug 2011 20:28:01 -0000 Delivered-To: apmail-lucene-solr-commits-archive@lucene.apache.org Received: (qmail 94335 invoked by uid 500); 31 Aug 2011 20:28:00 -0000 Mailing-List: contact solr-commits-help@lucene.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: solr-dev@lucene.apache.org Delivered-To: mailing list solr-commits@lucene.apache.org Received: (qmail 94327 invoked by uid 99); 31 Aug 2011 20:28:00 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 31 Aug 2011 20:27:59 +0000 X-ASF-Spam-Status: No, hits=-2000.0 required=5.0 tests=ALL_TRUSTED X-Spam-Check-By: apache.org Received: from [140.211.11.131] (HELO eos.apache.org) (140.211.11.131) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 31 Aug 2011 20:27:57 +0000 Received: from eos.apache.org (localhost [127.0.0.1]) by eos.apache.org (Postfix) with ESMTP id 63991430; Wed, 31 Aug 2011 20:27:36 +0000 (UTC) MIME-Version: 1.0 Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable From: Apache Wiki To: Apache Wiki Date: Wed, 31 Aug 2011 20:27:36 -0000 Message-ID: <20110831202736.63396.4496@eos.apache.org> Subject: =?utf-8?q?=5BSolr_Wiki=5D_Update_of_=22SolrConfigXml=22_by_EricPugh?= Auto-Submitted: auto-generated X-Virus-Checked: Checked by ClamAV on apache.org Dear Wiki user, You have subscribed to a wiki page or wiki category on "Solr Wiki" for chan= ge notification. The "SolrConfigXml" page has been changed by EricPugh: http://wiki.apache.org/solr/SolrConfigXml?action=3Ddiff&rev1=3D40&rev2=3D41 Comment: It was not obvious to me how to take advantage of the healthcheck enable/di= sable, that using the /admin/ping did this! <> = =3D=3D lib =3D=3D - = `` directives can be specified in your solrconfig.xml to specify whe= re Solr should look to load SolrPlugins. The [[http://svn.apache.org/repos= /asf/lucene/dev/trunk/solr/example/solr/conf/solrconfig.xml|example solrcon= fig.xml]] contains main examples of the syntax. = =3D=3D dataDir parameter =3D=3D @@ -340, +339 @@ }}} - = [[Solr3.1]] NOTE: Prior to Solr3.1 you need to use update.processor i= nstead of update.chain = =3D=3D The Highlighter plugin configuration section =3D=3D @@ -377, +375 @@ }}} - = =3D=3D=3D Providing a Custom Highlighter =3D=3D=3D - = [[Solr1.3]] = Since Solr 1.3, applications can provide their own highlighting code. To= take advantage of this, configure the !HighlightComponent as above, but, i= n the {{{` defines what the "ping" query should be for monitoring = the health of the Solr server. The URL of the "ping" query is '''/admin/pi= ng'''. It can be used by a load balancer in front of a set of Solr servers= to check response time of all the Solr servers in order to do response tim= e based load balancing. = - Including the optional `` will add a '''ENABLE= '''/'''DISABLE''' link on the administration web page which can be used to = create/remove a file at the path defined by the value of ``. = A load balancer in front of a set of Solr servers can then query an URL map= ped to this file to determine when it should keep/add/remove a server from = rotation. + Including the optional `` will add a '''ENABLE= '''/'''DISABLE''' link on the administration web page which can be used to = create/remove a file at the path defined by the value of ``. = When the file is removed then the "ping" query will automatically fail. A = load balancer in front of a set of Solr servers can then determine when it = should keep/add/remove a server from rotation by pinging the server. = {{{