Return-Path: Delivered-To: apmail-lucene-solr-user-archive@minotaur.apache.org Received: (qmail 1247 invoked from network); 28 Aug 2009 05:04:13 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 28 Aug 2009 05:04:13 -0000 Received: (qmail 57057 invoked by uid 500); 28 Aug 2009 05:04:11 -0000 Delivered-To: apmail-lucene-solr-user-archive@lucene.apache.org Received: (qmail 56940 invoked by uid 500); 28 Aug 2009 05:04:11 -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 56930 invoked by uid 99); 28 Aug 2009 05:04:11 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 28 Aug 2009 05:04:11 +0000 X-ASF-Spam-Status: No, hits=1.2 required=10.0 tests=FS_REPLICA,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of noble.paul@gmail.com designates 209.85.216.202 as permitted sender) Received: from [209.85.216.202] (HELO mail-px0-f202.google.com) (209.85.216.202) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 28 Aug 2009 05:03:59 +0000 Received: by pxi40 with SMTP id 40so1605285pxi.5 for ; Thu, 27 Aug 2009 22:03:38 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:sender:reply-to:received :in-reply-to:references:from:date:x-google-sender-auth:message-id :subject:to:content-type:content-transfer-encoding; bh=f/mRNDCG3iZj26FB2xpnl1HFHK2iS39UyLNWUDKlk7k=; b=vChkN2RLgTY0lIdLspHhh9MmvzBeGYvBBRtJrTQZIplZ4xzyEeHruMz4ZQDPi0Lx0P KjyFa47FmdY3J9YDIyMsxADhYjbSOilNkrn6vxVR3cKr3ZLlUpLXgWAALufzd8q2+OT2 Q2VTOvcREkHw8Wq9DTmIFfwxGoF1SNwvDmmsg= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:sender:reply-to:in-reply-to:references:from:date :x-google-sender-auth:message-id:subject:to:content-type :content-transfer-encoding; b=QA6CkJ2Xy8doc1CtsvRTi1IUeyHDlSIADlvTRzNvyWDghyFofJajEKCjgL0rHOG8Jw CmxpZAKcPs0DDIbnvvsk09RHONaI0Qy9FPMuznVZv1C/CmqxcjuLyeBRy1NKQADjPuIg bKIpETJtLQxiDwTX2lVLLKBjWt78BltGB59v0= MIME-Version: 1.0 Sender: noble.paul@gmail.com Reply-To: noble.paul@gmail.com Received: by 10.140.194.3 with SMTP id r3mr382621rvf.200.1251435818081; Thu, 27 Aug 2009 22:03:38 -0700 (PDT) In-Reply-To: References: <5e76b0ad0908252235y1cb838d8v17d84cc2806a18a1@mail.gmail.com> <5e76b0ad0908270034s6ac9ae3dob8dd0ec14504004a@mail.gmail.com> From: =?UTF-8?B?Tm9ibGUgUGF1bCDgtKjgtYvgtKzgtL/gtLPgtY3igI0gIOCkqOCli+CkrOCljeCks+CljQ==?= Date: Fri, 28 Aug 2009 10:33:18 +0530 X-Google-Sender-Auth: f7f15144080ceee9 Message-ID: <5e76b0ad0908272203m1038fddbr9b7fc026fb6d966c@mail.gmail.com> Subject: Re: Solr Replication To: solr-user@lucene.apache.org Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable X-Virus-Checked: Checked by ClamAV on apache.org Each instance has its own ReplicationHandler instance/MBean. I guess the problem is with the jmx implementation. both MBeans may be registered with the same name On Fri, Aug 28, 2009 at 2:04 AM, J G wrote: > > We have multiple solr webapps all running from the same WAR file. Each we= bapp is running under the same Tomcat container and I consider each webapp = the same thing as a "slice" (or "instance"). I've configured the Tomcat con= tainer to enable JMX and when I connect using JConsole I only see the repli= cation handler for one of the webapps in the server. I was under the impres= sion each webapp gets its own replication handler. Is this not true? > > It would be nice to be able to have a JMX MBean for each replication hand= ler in the container so we can get all the same replication information usi= ng JMX as in using the replication admin page for each web app. > > Thanks. > > > > > >> From: noble.paul@corp.aol.com >> Date: Thu, 27 Aug 2009 13:04:38 +0530 >> Subject: Re: Solr Replication >> To: solr-user@lucene.apache.org >> >> when you say a slice you mean one instance of solr? So your JMX >> console is connecting to only one solr? >> >> On Thu, Aug 27, 2009 at 3:19 AM, J G wrote: >> > >> > Thanks for the response. >> > >> > It's interesting because when I run jconsole all I can see is one Repl= icationHandler jmx mbean. It looks like it is defaulting to the first slice= it finds on its path. Is there anyway to have multiple replication handler= s or at least obtain replication on a per "slice"/"instance" via JMX like h= ow you can see attributes for each "slice"/"instance" via each replication = admin jsp page? >> > >> > Thanks again. >> > >> >> From: noble.paul@corp.aol.com >> >> Date: Wed, 26 Aug 2009 11:05:34 +0530 >> >> Subject: Re: Solr Replication >> >> To: solr-user@lucene.apache.org >> >> >> >> The ReplicationHandler is not enforced as a singleton , but for all >> >> practical purposes it is a singleton for one core. >> >> >> >> If an instance =A0(a slice as you say) is setup as a repeater, It can >> >> act as both a master and slave >> >> >> >> in the repeater the configuration should be as follows >> >> >> >> MASTER >> >> =A0 |_____________SLAVE (I am a slave of MASTER) >> >> =A0 | >> >> REPEATER (I am a slave of MASTER and master to my slaves ) >> >> =A0| >> >> =A0| >> >> REPEATER_SLAVE( of REPEATER) >> >> >> >> >> >> the point is that REPEATER will have a slave section has a masterUrl >> >> which points to master and REPEATER_SLAVE will have a slave section >> >> which has a masterurl pointing to repeater >> >> >> >> >> >> >> >> >> >> >> >> >> >> On Wed, Aug 26, 2009 at 12:40 AM, J G wrot= e: >> >> > >> >> > Hello, >> >> > >> >> > We are running multiple slices in our environment. I have enabled J= MX and I am inspecting the replication handler mbean to obtain some informa= tion about the master/slave configuration for replication. Is the replicati= on handler mbean a singleton? I only see one mbean for the entire server an= d it's picking an arbitrary slice to report on. So I'm curious if every sli= ce gets its own replication handler mbean? This is important because I have= no way of knowing in this specific server any information about the other = slices, in particular, information about the master/slave value for the oth= er slices. >> >> > >> >> > Reading through the Solr 1.4 replication strategy, I saw that a sli= ce can be configured to be a master and a slave, i.e. a repeater. I'm wonde= ring how repeaters work because let's say I have a slice named 'A' and the = master is on server 1 and the slave is on server 2 then how are these two s= ervers communicating to replicate? Looking at the jmx information I have in= the MBean both the isSlave and isMaster is set to true for my repeater so = how does this solr slice know if it's the master or slave? I'm a bit confus= ed. >> >> > >> >> > Thanks. >> >> > >> >> > >> >> > >> >> > >> >> > _________________________________________________________________ >> >> > With Windows Live, you can organize, edit, and share your photos. >> >> > http://www.windowslive.com/Desktop/PhotoGallery >> >> >> >> >> >> >> >> -- >> >> ----------------------------------------------------- >> >> Noble Paul | Principal Engineer| AOL | http://aol.com >> > >> > _________________________________________________________________ >> > Hotmail=AE is up to 70% faster. Now good news travels really fast. >> > http://windowslive.com/online/hotmail?ocid=3DPID23391::T:WLMTAGL:ON:WL= :en-US:WM_HYGN_faster:082009 >> >> >> >> -- >> ----------------------------------------------------- >> Noble Paul | Principal Engineer| AOL | http://aol.com > > _________________________________________________________________ > With Windows Live, you can organize, edit, and share your photos. > http://www.windowslive.com/Desktop/PhotoGallery --=20 ----------------------------------------------------- Noble Paul | Principal Engineer| AOL | http://aol.com