Re: index version command
Cool. On Thu, May 28, 2009 at 11:10 PM, Otis Gospodnetic < otis_gospodne...@yahoo.com> wrote: > > View the source of that page, it should be all XML, so you can easily parse > it. > > Otis > -- > Sematext -- http://sematext.com/ -- Lucene - Solr - Nutch > > > > ----- Original Message > > From: nk 11 > > To: solr-user@lucene.apache.org > > Sent: Thursday, May 28, 2009 2:54:08 PM > > Subject: Re: index version command > > > > Thanks. So I should parse the html result? I was thinking about something > > more "machine readable". > > On Thu, May 28, 2009 at 9:01 PM, Otis Gospodnetic < > > otis_gospodne...@yahoo.com> wrote: > > > > > > > > Hello, > > > > > > You can see the version of the index in the Solr Admin page. > > > > > > Otis > > > -- > > > Sematext -- http://sematext.com/ -- Lucene - Solr - Nutch > > > > > > > > > > > > - Original Message > > > > From: nk 11 > > > > To: solr-user@lucene.apache.org > > > > Sent: Thursday, May 28, 2009 10:29:10 AM > > > > Subject: index version command > > > > > > > > Hello > > > > > > > > Can you tell me please how can I find out what is the version of the > > > index > > > > on a slave? > > > > > > > > I tried http://host:port/solr/replication?command=indexversion but I > got > > > > 0... > > > > > > > > Thanks > > > > > > > >
Re: index version command
Thanks. So I should parse the html result? I was thinking about something more "machine readable". On Thu, May 28, 2009 at 9:01 PM, Otis Gospodnetic < otis_gospodne...@yahoo.com> wrote: > > Hello, > > You can see the version of the index in the Solr Admin page. > > Otis > -- > Sematext -- http://sematext.com/ -- Lucene - Solr - Nutch > > > > - Original Message > > From: nk 11 > > To: solr-user@lucene.apache.org > > Sent: Thursday, May 28, 2009 10:29:10 AM > > Subject: index version command > > > > Hello > > > > Can you tell me please how can I find out what is the version of the > index > > on a slave? > > > > I tried http://host:port/solr/replication?command=indexversion but I got > > 0... > > > > Thanks > >
Re: How to index large set data
Hello Interesting thread. One request please, because I don't have much experience with solr, could you please use full terms and not DIH, RES etc.? Thanks :) On Mon, May 25, 2009 at 4:44 AM, Jianbin Dai wrote: > > Hi Paul, > > Hope you have a great weekend so far. > I still have a couple of questions you might help me out: > > 1. In your earlier email, you said "if possible , you can setup multiple > DIH say /dataimport1, /dataimport2 etc and split your files and can achieve > parallelism" > I am not sure if I understand it right. I put two requesHandler in > solrconfig.xml, like this > > class="org.apache.solr.handler..dataimport.DataImportHandler"> > > ./data-config.xml > > > > class="org.apache.solr.handler.dataimport.DataImportHandler"> > > ./data-config2.xml > > > > > and create data-config.xml and data-config2.xml. > then I run the command > http://host:8080/solr/dataimport?command=full-import > > But only one data set (the first one) was indexed. Did I get something > wrong? > > > 2. I noticed that after solr indexed about 8M documents (around two hours), > it gets very very slow. I use "top" command in linux, and noticed that RES > is 1g of memory. I did several experiments, every time RES reaches 1g, the > indexing process becomes extremely slow. Is this memory limit set by JVM? > And how can I set the JVM memory when I use DIH through web command > full-import? > > Thanks! > > > JB > > > > > --- On Fri, 5/22/09, Noble Paul നോബിള് नोब्ळ् > wrote: > > > From: Noble Paul നോബിള് नोब्ळ् > > Subject: Re: How to index large set data > > To: "Jianbin Dai" > > Date: Friday, May 22, 2009, 10:04 PM > > On Sat, May 23, 2009 at 10:27 AM, > > Jianbin Dai > > wrote: > > > > > > Hi Pual, but in your previous post, you said "there is > > already an issue for writing to Solr in multiple threads > > SOLR-1089". Do you think use solrj alone would be better > > than DIH? > > > > nope > > you will have to do indexing in multiple threads > > > > if possible , you can setup multiple DIH say /dataimport1, > > /dataimport2 etc and split your files and can achieve > > parallelism > > > > > > > Thanks and have a good weekend! > > > > > > --- On Fri, 5/22/09, Noble Paul നോബിള് > > नोब्ळ् > > wrote: > > > > > >> no need to use embedded Solrserver.. > > >> you can use SolrJ with streaming > > >> in multiple threads > > >> > > >> On Fri, May 22, 2009 at 8:36 PM, Jianbin Dai > > > > >> wrote: > > >> > > > >> > If I do the xml parsing by myself and use > > embedded > > >> client to do the push, would it be more efficient > > than DIH? > > >> > > > >> > > > >> > --- On Fri, 5/22/09, Grant Ingersoll > > >> wrote: > > >> > > > >> >> From: Grant Ingersoll > > >> >> Subject: Re: How to index large set data > > >> >> To: solr-user@lucene.apache.org > > >> >> Date: Friday, May 22, 2009, 5:38 AM > > >> >> Can you parallelize this? I > > >> >> don't know that the DIH can handle it, > > >> >> but having multiple threads sending docs > > to Solr > > >> is the > > >> >> best > > >> >> performance wise, so maybe you need to > > look at > > >> alternatives > > >> >> to pulling > > >> >> with DIH and instead use a client to push > > into > > >> Solr. > > >> >> > > >> >> > > >> >> On May 22, 2009, at 3:42 AM, Jianbin Dai > > wrote: > > >> >> > > >> >> > > > >> >> > about 2.8 m total docs were created. > > only the > > >> first > > >> >> run finishes. In > > >> >> > my 2nd try, it hangs there forever > > at the end > > >> of > > >> >> indexing, (I guess > > >> >> > right before commit), with cpu usage > > of 100%. > > >> Total 5G > > >> >> (2050) index > > >> >> > files are created. Now I have two > > problems: > > >> >> > 1. why it hangs there and failed? > > >> >> > 2. how can i speed up the indexing? > > >> >> > > > >> >> > > > >> >> > Here is my solrconfig.xml > > >> >> > > > >> >> > > > >> >> > > >> > > false > > >> >> > > > >> >> > > >> > > 3000 > > >> >> > > > >> >> > > 1000 > > >> >> > > > >> >> > > >> > > 2147483647 > > >> >> > > > >> >> > > >> > > 1 > > >> >> > > > >> >> > > >> > > false > > >> >> > > > >> >> > > > >> >> > > > >> >> > > > >> >> > --- On Thu, 5/21/09, Noble Paul > > >> >> നോബിള് नो > > >> >> > ब्ळ् > > >> >> wrote: > > >> >> > > > >> >> >> From: Noble Paul > > നോബിള് > > >> >> नोब्ळ् > > >> >> >> > > >> >> >> Subject: Re: How to index large > > set data > > >> >> >> To: solr-user@lucene.apache.org > > >> >> >> Date: Thursday, May 21, 2009, > > 10:39 PM > > >> >> >> what is the total no:of docs > > created > > >> >> >> ? I guess it may not be > > memory > > >> >> >> bound. indexing is mostly amn IO > > bound > > >> operation. > > >> >> You may > > >> >> >> be able to > > >> >> >> get a better perf if a SSD is > > used (solid > > >> state > > >> >> disk) > > >> >> >> > > >> >> >> On Fri, May 22, 2009 at 10:46 > > AM, Jianbin > > >> Dai > > >> >> > > >> >> >> wrote: > > >> >> >>> > > >> >> >>> Hi Paul, > > >> >> >>> > > >> >> >>> Thank you so much for > > answeri
Re: master/slave failure scenario
You are right... I just don't like the idea of stopping the indexing process if the master fails until a new one is started (more or less by hand). On Thu, May 21, 2009 at 6:49 PM, Bryan Talbot wrote: > Indexing is usually much more expensive that replication so it won't scale > well as you add more servers. Also, what would a client do if it was able > to send the update to only some of the servers because others were down (for > maintenance, etc)? > > > > -Bryan > > > > > > On May 21, 2009, at May 21, 6:04 AM, nk 11 wrote: > > Just curious. What would be the disadvantages of a no replication / multi >> master (no slave) setup? >> The client code should do the updates for evey master ofc, but if one >> machine would fail then I can imediatly continue the indexing process and >> also I can query the index on any machine for a valid result. >> I might be missing something... >> On Thu, May 14, 2009 at 4:19 PM, nk 11 wrote: >> >> wow! that was just a couple of days old! >>> thanks as lot! >>> 2009/5/14 Noble Paul നോബിള് नोब्ळ् >>> >>> yeah there is a hack >>>> >>>> >>>> https://issues.apache.org/jira/browse/SOLR-1154?focusedCommentId=12708316&page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel >>>> #action_12708316 >>>> >>>> On Thu, May 14, 2009 at 6:07 PM, nk 11 wrote: >>>> >>>>> sorry for the mail. I wanted to hit reply :( >>>>> >>>>> On Thu, May 14, 2009 at 3:37 PM, nk 11 wrote: >>>>> >>>>>> >>>>>> oh, so the configuration must be manualy changed? >>>>>> Can't something be passed at (re)start time? >>>>>> >>>>>> 2009/5/14 Noble Paul നോബിള് नोब्ळ् >>>>>> >>>>>>> >>>>>>> On Thu, May 14, 2009 at 4:07 PM, nk 11 >>>>>>> >>>>>> wrote: >>>> >>>>> Ok so the VIP will point to the new master. but what makes a slave >>>>>>>> promoted >>>>>>>> to a master? Only the fact that it will receive add/update requests? >>>>>>>> And I suppose that this "hot" promotion is possible only if the >>>>>>>> >>>>>>> slave >>>> >>>>> is >>>>>>>> convigured as master also... >>>>>>>> >>>>>>> right.. By default you can setup all slaves to be master also. It >>>>>>> does >>>>>>> not cost anything if it is not serving any requests. >>>>>>> >>>>>>> so , if you have such a setting you will have to disable that slave >>>>>>> to >>>>>>> be a slave and restart it and you will have to make the VIP point to >>>>>>> this new slave as master. >>>>>>> >>>>>>> so hot promotion is still not possible. >>>>>>> >>>>>>>> >>>>>>>> 2009/5/14 Noble Paul നോബിള് नोब्ळ् >>>>>>>> >>>>>>>>> >>>>>>>>> ideally , we don't do that. >>>>>>>>> you can just keep the master host behind a VIP so if you wish to >>>>>>>>> change the master make the VIP point to the new host >>>>>>>>> >>>>>>>>> On Wed, May 13, 2009 at 10:52 PM, nk 11 >>>>>>>>> wrote: >>>>>>>>> >>>>>>>>>> This is more interesting.Such a procedure would involve taking >>>>>>>>>> >>>>>>>>> down >>>> >>>>> and >>>>>>>>>> reconfiguring the slave? >>>>>>>>>> >>>>>>>>>> On Wed, May 13, 2009 at 7:55 PM, Bryan Talbot >>>>>>>>>> wrote: >>>>>>>>>> >>>>>>>>>> Or ... >>>>>>>>>>> >>>>>>>>>>> 1. Promote existing slave to new master >>>>>>>>>>> 2. Add new slave to cluster >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>>> >>>>>>>>>
Re: master/slave failure scenario
Just curious. What would be the disadvantages of a no replication / multi master (no slave) setup? The client code should do the updates for evey master ofc, but if one machine would fail then I can imediatly continue the indexing process and also I can query the index on any machine for a valid result. I might be missing something... On Thu, May 14, 2009 at 4:19 PM, nk 11 wrote: > wow! that was just a couple of days old! > thanks as lot! > 2009/5/14 Noble Paul നോബിള് नोब्ळ् > >> yeah there is a hack >> >> https://issues.apache.org/jira/browse/SOLR-1154?focusedCommentId=12708316&page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#action_12708316 >> >> On Thu, May 14, 2009 at 6:07 PM, nk 11 wrote: >> > sorry for the mail. I wanted to hit reply :( >> > >> > On Thu, May 14, 2009 at 3:37 PM, nk 11 wrote: >> >> >> >> oh, so the configuration must be manualy changed? >> >> Can't something be passed at (re)start time? >> >> >> >> 2009/5/14 Noble Paul നോബിള് नोब्ळ् >> >>> >> >>> On Thu, May 14, 2009 at 4:07 PM, nk 11 >> wrote: >> >>> > Ok so the VIP will point to the new master. but what makes a slave >> >>> > promoted >> >>> > to a master? Only the fact that it will receive add/update requests? >> >>> > And I suppose that this "hot" promotion is possible only if the >> slave >> >>> > is >> >>> > convigured as master also... >> >>> right.. By default you can setup all slaves to be master also. It does >> >>> not cost anything if it is not serving any requests. >> >>> >> >>> so , if you have such a setting you will have to disable that slave to >> >>> be a slave and restart it and you will have to make the VIP point to >> >>> this new slave as master. >> >>> >> >>> so hot promotion is still not possible. >> >>> > >> >>> > 2009/5/14 Noble Paul നോബിള് नोब्ळ् >> >>> >> >> >>> >> ideally , we don't do that. >> >>> >> you can just keep the master host behind a VIP so if you wish to >> >>> >> change the master make the VIP point to the new host >> >>> >> >> >>> >> On Wed, May 13, 2009 at 10:52 PM, nk 11 >> >>> >> wrote: >> >>> >> > This is more interesting.Such a procedure would involve taking >> down >> >>> >> > and >> >>> >> > reconfiguring the slave? >> >>> >> > >> >>> >> > On Wed, May 13, 2009 at 7:55 PM, Bryan Talbot >> >>> >> > wrote: >> >>> >> > >> >>> >> >> Or ... >> >>> >> >> >> >>> >> >> 1. Promote existing slave to new master >> >>> >> >> 2. Add new slave to cluster >> >>> >> >> >> >>> >> >> >> >>> >> >> >> >>> >> >> >> >>> >> >> -Bryan >> >>> >> >> >> >>> >> >> >> >>> >> >> >> >>> >> >> >> >>> >> >> >> >>> >> >> On May 13, 2009, at May 13, 9:48 AM, Jay Hill wrote: >> >>> >> >> >> >>> >> >> - Migrate configuration files from old master (or backup) to >> new >> >>> >> >> master. >> >>> >> >>> - Replicate from a slave to the new master. >> >>> >> >>> - Resume indexing to new master. >> >>> >> >>> >> >>> >> >>> -Jay >> >>> >> >>> >> >>> >> >>> On Wed, May 13, 2009 at 4:26 AM, nk 11 > > >> >>> >> >>> wrote: >> >>> >> >>> >> >>> >> >>> Nice. >> >>> >> >>>> What if the master fails permanently (like a disk crash...) >> and >> >>> >> >>>> the >> >>> >> >>>> new >> >>> >> >>>> master is a clean machine? >> >
Re: master/slave failure scenario
wow! that was just a couple of days old! thanks as lot! 2009/5/14 Noble Paul നോബിള് नोब्ळ् > yeah there is a hack > > https://issues.apache.org/jira/browse/SOLR-1154?focusedCommentId=12708316&page=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#action_12708316 > > On Thu, May 14, 2009 at 6:07 PM, nk 11 wrote: > > sorry for the mail. I wanted to hit reply :( > > > > On Thu, May 14, 2009 at 3:37 PM, nk 11 wrote: > >> > >> oh, so the configuration must be manualy changed? > >> Can't something be passed at (re)start time? > >> > >> 2009/5/14 Noble Paul നോബിള് नोब्ळ् > >>> > >>> On Thu, May 14, 2009 at 4:07 PM, nk 11 wrote: > >>> > Ok so the VIP will point to the new master. but what makes a slave > >>> > promoted > >>> > to a master? Only the fact that it will receive add/update requests? > >>> > And I suppose that this "hot" promotion is possible only if the slave > >>> > is > >>> > convigured as master also... > >>> right.. By default you can setup all slaves to be master also. It does > >>> not cost anything if it is not serving any requests. > >>> > >>> so , if you have such a setting you will have to disable that slave to > >>> be a slave and restart it and you will have to make the VIP point to > >>> this new slave as master. > >>> > >>> so hot promotion is still not possible. > >>> > > >>> > 2009/5/14 Noble Paul നോബിള് नोब्ळ् > >>> >> > >>> >> ideally , we don't do that. > >>> >> you can just keep the master host behind a VIP so if you wish to > >>> >> change the master make the VIP point to the new host > >>> >> > >>> >> On Wed, May 13, 2009 at 10:52 PM, nk 11 > >>> >> wrote: > >>> >> > This is more interesting.Such a procedure would involve taking > down > >>> >> > and > >>> >> > reconfiguring the slave? > >>> >> > > >>> >> > On Wed, May 13, 2009 at 7:55 PM, Bryan Talbot > >>> >> > wrote: > >>> >> > > >>> >> >> Or ... > >>> >> >> > >>> >> >> 1. Promote existing slave to new master > >>> >> >> 2. Add new slave to cluster > >>> >> >> > >>> >> >> > >>> >> >> > >>> >> >> > >>> >> >> -Bryan > >>> >> >> > >>> >> >> > >>> >> >> > >>> >> >> > >>> >> >> > >>> >> >> On May 13, 2009, at May 13, 9:48 AM, Jay Hill wrote: > >>> >> >> > >>> >> >> - Migrate configuration files from old master (or backup) to new > >>> >> >> master. > >>> >> >>> - Replicate from a slave to the new master. > >>> >> >>> - Resume indexing to new master. > >>> >> >>> > >>> >> >>> -Jay > >>> >> >>> > >>> >> >>> On Wed, May 13, 2009 at 4:26 AM, nk 11 > >>> >> >>> wrote: > >>> >> >>> > >>> >> >>> Nice. > >>> >> >>>> What if the master fails permanently (like a disk crash...) and > >>> >> >>>> the > >>> >> >>>> new > >>> >> >>>> master is a clean machine? > >>> >> >>>> 2009/5/13 Noble Paul നോബിള് नोब्ळ् > >>> >> >>>> > >>> >> >>>> On Wed, May 13, 2009 at 12:10 PM, nk 11 < > nick.cass...@gmail.com> > >>> >> >>>> wrote: > >>> >> >>>>> > >>> >> >>>>>> Hello > >>> >> >>>>>> > >>> >> >>>>>> I'm kind of new to Solr and I've read about replication, and > >>> >> >>>>>> the > >>> >> >>>>>> fact > >>> >> >>>>>> > >>> >> >>>>> that a > >>> >> >>>>&
Re: master/slave failure scenario
oh, so the configuration must be manualy changed? Can't something be passed at (re)start time? > > 2009/5/14 Noble Paul നോബിള് नोब्ळ् > >> On Thu, May 14, 2009 at 4:07 PM, nk 11 wrote: >> > Ok so the VIP will point to the new master. but what makes a slave >> promoted >> > to a master? Only the fact that it will receive add/update requests? >> > And I suppose that this "hot" promotion is possible only if the slave is >> > convigured as master also... >> right.. By default you can setup all slaves to be master also. It does >> not cost anything if it is not serving any requests. >> >> so , if you have such a setting you will have to disable that slave to >> be a slave and restart it and you will have to make the VIP point to >> this new slave as master. >> >> so hot promotion is still not possible. >> > >> > 2009/5/14 Noble Paul നോബിള് नोब्ळ् >> >> >> >> ideally , we don't do that. >> >> you can just keep the master host behind a VIP so if you wish to >> >> change the master make the VIP point to the new host >> >> >> >> On Wed, May 13, 2009 at 10:52 PM, nk 11 >> wrote: >> >> > This is more interesting.Such a procedure would involve taking down >> and >> >> > reconfiguring the slave? >> >> > >> >> > On Wed, May 13, 2009 at 7:55 PM, Bryan Talbot >> >> > wrote: >> >> > >> >> >> Or ... >> >> >> >> >> >> 1. Promote existing slave to new master >> >> >> 2. Add new slave to cluster >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> -Bryan >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> >> On May 13, 2009, at May 13, 9:48 AM, Jay Hill wrote: >> >> >> >> >> >> - Migrate configuration files from old master (or backup) to new >> >> >> master. >> >> >>> - Replicate from a slave to the new master. >> >> >>> - Resume indexing to new master. >> >> >>> >> >> >>> -Jay >> >> >>> >> >> >>> On Wed, May 13, 2009 at 4:26 AM, nk 11 >> wrote: >> >> >>> >> >> >>> Nice. >> >> >>>> What if the master fails permanently (like a disk crash...) and >> the >> >> >>>> new >> >> >>>> master is a clean machine? >> >> >>>> 2009/5/13 Noble Paul നോബിള് नोब्ळ् >> >> >>>> >> >> >>>> On Wed, May 13, 2009 at 12:10 PM, nk 11 >> >> >>>> wrote: >> >> >>>>> >> >> >>>>>> Hello >> >> >>>>>> >> >> >>>>>> I'm kind of new to Solr and I've read about replication, and the >> >> >>>>>> fact >> >> >>>>>> >> >> >>>>> that a >> >> >>>>> >> >> >>>>>> node can act as both master and slave. >> >> >>>>>> I a replica fails and then comes back on line I suppose that it >> >> >>>>>> will >> >> >>>>>> >> >> >>>>> resyncs >> >> >>>>> >> >> >>>>>> with the master. >> >> >>>>>> >> >> >>>>> right >> >> >>>>> >> >> >>>>>> >> >> >>>>>> But what happnes if the master fails? A slave that is configured >> as >> >> >>>>>> >> >> >>>>> master >> >> >>>>> >> >> >>>>>> will kick in? What if that slave is not yes fully sync'ed with >> the >> >> >>>>>> >> >> >>>>> failed >> >> >>>> >> >> >>>>> master and has old data? >> >> >>>>>> >> >> >>>>> if the master fails you can't index the data. but the slaves will >> >> >>>>> continue serving the requests with the last index. You an bring >> back >> >> >>>>> the master up and resume indexing. >> >> >>>>> >> >> >>>>> >> >> >>>>>> What happens when the original master comes back on line? He >> will >> >> >>>>>> >> >> >>>>> remain >> >> >>>> >> >> >>>>> a >> >> >>>>> >> >> >>>>>> slave because there is another node with the master role? >> >> >>>>>> >> >> >>>>>> Thank you! >> >> >>>>>> >> >> >>>>>> >> >> >>>>> >> >> >>>>> >> >> >>>>> -- >> >> >>>>> - >> >> >>>>> Noble Paul | Principal Engineer| AOL | http://aol.com >> >> >>>>> >> >> >>>>> >> >> >>>> >> >> >> >> >> > >> >> >> >> >> >> >> >> -- >> >> - >> >> Noble Paul | Principal Engineer| AOL | http://aol.com >> > >> > >> >> >> >> -- >> - >> Noble Paul | Principal Engineer| AOL | http://aol.com >> > >
Re: master/slave failure scenario
Ok so the VIP will point to the new master. but what makes a slave promoted to a master? Only the fact that it will receive add/update requests? And I suppose that this "hot" promotion is possible only if the slave is convigured as master also... 2009/5/14 Noble Paul നോബിള് नोब्ळ् > ideally , we don't do that. > you can just keep the master host behind a VIP so if you wish to > change the master make the VIP point to the new host > > On Wed, May 13, 2009 at 10:52 PM, nk 11 wrote: > > This is more interesting.Such a procedure would involve taking down and > > reconfiguring the slave? > > > > On Wed, May 13, 2009 at 7:55 PM, Bryan Talbot >wrote: > > > >> Or ... > >> > >> 1. Promote existing slave to new master > >> 2. Add new slave to cluster > >> > >> > >> > >> > >> -Bryan > >> > >> > >> > >> > >> > >> On May 13, 2009, at May 13, 9:48 AM, Jay Hill wrote: > >> > >> - Migrate configuration files from old master (or backup) to new > master. > >>> - Replicate from a slave to the new master. > >>> - Resume indexing to new master. > >>> > >>> -Jay > >>> > >>> On Wed, May 13, 2009 at 4:26 AM, nk 11 wrote: > >>> > >>> Nice. > >>>> What if the master fails permanently (like a disk crash...) and the > new > >>>> master is a clean machine? > >>>> 2009/5/13 Noble Paul നോബിള് नोब्ळ् > >>>> > >>>> On Wed, May 13, 2009 at 12:10 PM, nk 11 > wrote: > >>>>> > >>>>>> Hello > >>>>>> > >>>>>> I'm kind of new to Solr and I've read about replication, and the > fact > >>>>>> > >>>>> that a > >>>>> > >>>>>> node can act as both master and slave. > >>>>>> I a replica fails and then comes back on line I suppose that it will > >>>>>> > >>>>> resyncs > >>>>> > >>>>>> with the master. > >>>>>> > >>>>> right > >>>>> > >>>>>> > >>>>>> But what happnes if the master fails? A slave that is configured as > >>>>>> > >>>>> master > >>>>> > >>>>>> will kick in? What if that slave is not yes fully sync'ed with the > >>>>>> > >>>>> failed > >>>> > >>>>> master and has old data? > >>>>>> > >>>>> if the master fails you can't index the data. but the slaves will > >>>>> continue serving the requests with the last index. You an bring back > >>>>> the master up and resume indexing. > >>>>> > >>>>> > >>>>>> What happens when the original master comes back on line? He will > >>>>>> > >>>>> remain > >>>> > >>>>> a > >>>>> > >>>>>> slave because there is another node with the master role? > >>>>>> > >>>>>> Thank you! > >>>>>> > >>>>>> > >>>>> > >>>>> > >>>>> -- > >>>>> - > >>>>> Noble Paul | Principal Engineer| AOL | http://aol.com > >>>>> > >>>>> > >>>> > >> > > > > > > -- > - > Noble Paul | Principal Engineer| AOL | http://aol.com >
Re: master/slave failure scenario
This is more interesting.Such a procedure would involve taking down and reconfiguring the slave? On Wed, May 13, 2009 at 7:55 PM, Bryan Talbot wrote: > Or ... > > 1. Promote existing slave to new master > 2. Add new slave to cluster > > > > > -Bryan > > > > > > On May 13, 2009, at May 13, 9:48 AM, Jay Hill wrote: > > - Migrate configuration files from old master (or backup) to new master. >> - Replicate from a slave to the new master. >> - Resume indexing to new master. >> >> -Jay >> >> On Wed, May 13, 2009 at 4:26 AM, nk 11 wrote: >> >> Nice. >>> What if the master fails permanently (like a disk crash...) and the new >>> master is a clean machine? >>> 2009/5/13 Noble Paul നോബിള് नोब्ळ् >>> >>> On Wed, May 13, 2009 at 12:10 PM, nk 11 wrote: >>>> >>>>> Hello >>>>> >>>>> I'm kind of new to Solr and I've read about replication, and the fact >>>>> >>>> that a >>>> >>>>> node can act as both master and slave. >>>>> I a replica fails and then comes back on line I suppose that it will >>>>> >>>> resyncs >>>> >>>>> with the master. >>>>> >>>> right >>>> >>>>> >>>>> But what happnes if the master fails? A slave that is configured as >>>>> >>>> master >>>> >>>>> will kick in? What if that slave is not yes fully sync'ed with the >>>>> >>>> failed >>> >>>> master and has old data? >>>>> >>>> if the master fails you can't index the data. but the slaves will >>>> continue serving the requests with the last index. You an bring back >>>> the master up and resume indexing. >>>> >>>> >>>>> What happens when the original master comes back on line? He will >>>>> >>>> remain >>> >>>> a >>>> >>>>> slave because there is another node with the master role? >>>>> >>>>> Thank you! >>>>> >>>>> >>>> >>>> >>>> -- >>>> - >>>> Noble Paul | Principal Engineer| AOL | http://aol.com >>>> >>>> >>> >
Re: master/slave failure scenario
Nice. What if the master fails permanently (like a disk crash...) and the new master is a clean machine? 2009/5/13 Noble Paul നോബിള് नोब्ळ् > On Wed, May 13, 2009 at 12:10 PM, nk 11 wrote: > > Hello > > > > I'm kind of new to Solr and I've read about replication, and the fact > that a > > node can act as both master and slave. > > I a replica fails and then comes back on line I suppose that it will > resyncs > > with the master. > right > > > > But what happnes if the master fails? A slave that is configured as > master > > will kick in? What if that slave is not yes fully sync'ed with the failed > > master and has old data? > if the master fails you can't index the data. but the slaves will > continue serving the requests with the last index. You an bring back > the master up and resume indexing. > > > > > What happens when the original master comes back on line? He will remain > a > > slave because there is another node with the master role? > > > > Thank you! > > > > > > -- > - > Noble Paul | Principal Engineer| AOL | http://aol.com >
master/slave failure scenario
Hello I'm kind of new to Solr and I've read about replication, and the fact that a node can act as both master and slave. I a replica fails and then comes back on line I suppose that it will resyncs with the master. But what happnes if the master fails? A slave that is configured as master will kick in? What if that slave is not yes fully sync'ed with the failed master and has old data? What happens when the original master comes back on line? He will remain a slave because there is another node with the master role? Thank you!
