You are viewing a plain text version of this content. The canonical link for it is here.
Posted to solr-user@lucene.apache.org by Steve Conover <sc...@gmail.com> on 2010/01/19 23:57:44 UTC
solr blocking on commit
I'm using latest solr 1.4 with java 1.6 on linux. I have a 3M
document index that's 10+GB. We currently give solr 12GB of ram to
play in and our machine has 32GB total.
We're seeing a problem where solr blocks during commit - it won't
server /select requests - in some cases for more than 15-30 seconds.
We'd like to somehow configure things such that there's no
interruption in /select service.
I've tried tweaking many parts of solrconfig (based on searches of
this mailing list): playing with the lock, with autowarming (including
shutting it off), max searchers, etc. I've tried asynchronous commits
(waitSearcher=false and waitFlush=false). The problem won't go away.
I run a fair amount of /select load at solr and even when it doesn't
take 20 seconds to commit, I definitely see pauses in the log when
commits are in progress.
I have this sense that I'm just missing something obvious (?)
Regards,
Steve
Re: solr blocking on commit
Posted by Erick Erickson <er...@gmail.com>.
Could you re-post this brand-new? You've replied to a thread over 2 years
old so it's kind of confusing.
How often are you polling? Seeing your replication settings would be
helpful...
Best
Erick
On Wed, Oct 31, 2012 at 8:25 PM, dbabits <db...@gmail.com> wrote:
> I second the original poster- all selects are blocked during commits.
> I have Master replicating to Slave.
> Indexing happens to Master, few docs/about every 30 secs
> Selects are run against Slave.
>
> This is the pattern from the Slave log:
>
> Oct 30, 2012 12:33:23 AM org.apache.solr.core.SolrDeletionPolicy
> updateCommits
> INFO: newest commit = 1349195567630
> Oct 30, 2012 12:33:42 AM org.apache.solr.core.SolrCore execute
> INFO: [core3] webapp=/solr path=/select
>
> During the 19 seconds that you see between the 2 lines, the /select is
> blocked, until the commit is done.
> This has nothing to do with jvm, I'm monitoring the memory and GC stats
> with
> jConsole and log.
> I played with all settings imaginable: commitWithin, commit=true,
> useColdSearcher, autoWarming settings from 0 on-nothing helps.
>
> The environment is: 3.6.0, RHEL Lunux 5.3.2, 64-bit, 96G RAM, 6 CPU cores,
> java 1.6.0_24, ~70 million docs.
> As soon as I suspend replication (command=disablepoll), everything becomes
> fast.
> As soon as I enable it - it pretty much becomes useless.
> Querying Master directly exibits the same problem of course.
>
> Thanks a lot for your help.
>
>
>
> --
> View this message in context:
> http://lucene.472066.n3.nabble.com/solr-blocking-on-commit-tp474874p4017416.html
> Sent from the Solr - User mailing list archive at Nabble.com.
>
Re: solr blocking on commit
Posted by Martin Koch <ma...@issuu.com>.
Are you using solr 4.0? We had some problems similar to this (not in a
master/slave setup, though), where the resolution was to disable the
transaction log, i.e. remove <updateLog> in the <updateHandler> section -
we don't need NRT get, so this isn't important to us.
Cheers,
/Martin Koch
On Thu, Nov 1, 2012 at 1:25 AM, dbabits <db...@gmail.com> wrote:
> I second the original poster- all selects are blocked during commits.
> I have Master replicating to Slave.
> Indexing happens to Master, few docs/about every 30 secs
> Selects are run against Slave.
>
> This is the pattern from the Slave log:
>
> Oct 30, 2012 12:33:23 AM org.apache.solr.core.SolrDeletionPolicy
> updateCommits
> INFO: newest commit = 1349195567630
> Oct 30, 2012 12:33:42 AM org.apache.solr.core.SolrCore execute
> INFO: [core3] webapp=/solr path=/select
>
> During the 19 seconds that you see between the 2 lines, the /select is
> blocked, until the commit is done.
> This has nothing to do with jvm, I'm monitoring the memory and GC stats
> with
> jConsole and log.
> I played with all settings imaginable: commitWithin, commit=true,
> useColdSearcher, autoWarming settings from 0 on-nothing helps.
>
> The environment is: 3.6.0, RHEL Lunux 5.3.2, 64-bit, 96G RAM, 6 CPU cores,
> java 1.6.0_24, ~70 million docs.
> As soon as I suspend replication (command=disablepoll), everything becomes
> fast.
> As soon as I enable it - it pretty much becomes useless.
> Querying Master directly exibits the same problem of course.
>
> Thanks a lot for your help.
>
>
>
> --
> View this message in context:
> http://lucene.472066.n3.nabble.com/solr-blocking-on-commit-tp474874p4017416.html
> Sent from the Solr - User mailing list archive at Nabble.com.
>
Re: solr blocking on commit
Posted by dbabits <db...@gmail.com>.
I second the original poster- all selects are blocked during commits.
I have Master replicating to Slave.
Indexing happens to Master, few docs/about every 30 secs
Selects are run against Slave.
This is the pattern from the Slave log:
Oct 30, 2012 12:33:23 AM org.apache.solr.core.SolrDeletionPolicy
updateCommits
INFO: newest commit = 1349195567630
Oct 30, 2012 12:33:42 AM org.apache.solr.core.SolrCore execute
INFO: [core3] webapp=/solr path=/select
During the 19 seconds that you see between the 2 lines, the /select is
blocked, until the commit is done.
This has nothing to do with jvm, I'm monitoring the memory and GC stats with
jConsole and log.
I played with all settings imaginable: commitWithin, commit=true,
useColdSearcher, autoWarming settings from 0 on-nothing helps.
The environment is: 3.6.0, RHEL Lunux 5.3.2, 64-bit, 96G RAM, 6 CPU cores,
java 1.6.0_24, ~70 million docs.
As soon as I suspend replication (command=disablepoll), everything becomes
fast.
As soon as I enable it - it pretty much becomes useless.
Querying Master directly exibits the same problem of course.
Thanks a lot for your help.
--
View this message in context: http://lucene.472066.n3.nabble.com/solr-blocking-on-commit-tp474874p4017416.html
Sent from the Solr - User mailing list archive at Nabble.com.
Re: solr blocking on commit
Posted by Erick Erickson <er...@gmail.com>.
Wait, wait, wait.... What about near-real-time? See:
http://issues.apache.org/jira/browse/SOLR-1606
(Integrate near real time)
<http://issues.apache.org/jira/browse/SOLR-1606>I don't think this is
production-ready yet, or if you're
willing to run patched code, but it sure seems like
you want to know about this..... And if you need this
anyway, any help getting it production ready would
be greatly appreciated.....
Erick
On Fri, Jan 22, 2010 at 10:56 AM, Jerome L Quinn <jl...@us.ibm.com> wrote:
>
>
> Otis Gospodnetic <ot...@yahoo.com> wrote on 01/22/2010 12:20:45
> AM:
> > I'm missing the bigger context of this thread here, but from the
> > snippet below - sure, commits cause in-memory index to get written
> > to disk, that causes some IO, and that *could* affect search *if*
> > queries are running on the same box. When index and/or query volume
> > is high, one typically puts indexing and searching on different servers.
>
> After some more research, I realize that what we're trying to do is
> essentially
> near-real-time processing.
>
> I have data collection that is near-real-time and I'm trying to avoid
> arbitrary delays pushing
> the data into the index so that the data collection doesn't stall. On the
> search side,
> we don't have a lot of search traffic but would like it to be responsive
> when it comes in.
>
> We also dynamically purge old data to keep the storage requirements within
> limits.
>
> So, basically I'm trying to have the system tuned so that this all works
> well :-) I'm trying
> to keep search on a single system to keep the costs down as well.
>
> One thing I'm trying now is to put an intermediary in so that updates can
> be asynchronous. Then
> my data collection processes can continue without waiting for unpredictable
> index merges.
>
> Thanks,
> Jerry
>
>
Re: solr blocking on commit
Posted by Jerome L Quinn <jl...@us.ibm.com>.
Otis Gospodnetic <ot...@yahoo.com> wrote on 01/22/2010 12:20:45
AM:
> I'm missing the bigger context of this thread here, but from the
> snippet below - sure, commits cause in-memory index to get written
> to disk, that causes some IO, and that *could* affect search *if*
> queries are running on the same box. When index and/or query volume
> is high, one typically puts indexing and searching on different servers.
After some more research, I realize that what we're trying to do is
essentially
near-real-time processing.
I have data collection that is near-real-time and I'm trying to avoid
arbitrary delays pushing
the data into the index so that the data collection doesn't stall. On the
search side,
we don't have a lot of search traffic but would like it to be responsive
when it comes in.
We also dynamically purge old data to keep the storage requirements within
limits.
So, basically I'm trying to have the system tuned so that this all works
well :-) I'm trying
to keep search on a single system to keep the costs down as well.
One thing I'm trying now is to put an intermediary in so that updates can
be asynchronous. Then
my data collection processes can continue without waiting for unpredictable
index merges.
Thanks,
Jerry
Re: solr with tomcat in cluster mode
Posted by Lance Norskog <go...@gmail.com>.
Ah, ok. There may be a load-balancer program for Windows. Also, the
SolrJ client library includes a feature to load-balance its requests.
If you write your app using this library, you're set.
On Thu, Jan 28, 2010 at 2:17 AM, ZAROGKIKAS,GIORGOS
<g....@multirama.gr> wrote:
> Windows ????
> I mention below that I user windows server 2008
>
> -----Original Message-----
> From: Lance Norskog [mailto:goksron@gmail.com]
> Sent: Thursday, January 28, 2010 3:46 AM
> To: solr-user@lucene.apache.org
> Subject: Re: solr with tomcat in cluster mode
>
> Linux includes a load-balancer program 'balance'. You set it up at a
> third port and configure it to use 'localhost:8180' and
> 'localhost:8280'.
>
> On Wed, Jan 27, 2010 at 4:06 AM, ZAROGKIKAS,GIORGOS
> <g....@multirama.gr> wrote:
>> Hi again
>> I finally setup my solr Cluster with tomcat6
>> The configuration I user is two tomcat servers on the same server in different ports(ex localhost:8180/solr and
>> Localhost:8280/solr for testing purposes) with different indexes on each server and index replication through replication handler of solr , and its working fine for me and very quick
>>
>> Now I want to use load balance for these two tomcat servers but without using apache http server
>> Is there any solution for that ???
>>
>>
>>
>>
>>
>>
>> -----Original Message-----
>> From: Matt Mitchell [mailto:goodieboy@gmail.com]
>> Sent: Friday, January 22, 2010 9:33 PM
>> To: solr-user@lucene.apache.org
>> Subject: Re: solr with tomcat in cluster mode
>>
>> Hey Otis,
>>
>> We're indexing on a separate machine because we want to keep our production
>> nodes away from processes like indexing. The indexing server also has a ton
>> of resources available, more so than the production nodes. We set it up as
>> an indexing server at one point and have decided to stick with it.
>>
>> We're not indexing the same index as the search indexes because we want to
>> be able to step back a day or two if needed. So we do the SWAP when things
>> are done and OK.
>>
>> So that last part you mentioned about the searchers needing to re-open will
>> happen with a SWAP right? Is your concern that there will be a lag time,
>> making it so the slaves will be out of sync for some small period of time?
>>
>> Would it be simpler/better to move to using Solrs native slave/master
>> feature?
>>
>> I'd love to hear any suggestions you might have.
>>
>> Thanks,
>>
>> Matt
>>
>> On Fri, Jan 22, 2010 at 1:58 PM, Otis Gospodnetic <
>> otis_gospodnetic@yahoo.com> wrote:
>>
>>> This should work fine.
>>> But why are you indexing to a separate index/core? Why not index in the
>>> very same index you are searching?
>>> Slaves won't see changes until their searchers re-open.
>>>
>>> Otis
>>> --
>>> Sematext -- http://sematext.com/ -- Solr - Lucene - Nutch
>>>
>>>
>>>
>>> ----- Original Message ----
>>> > From: Matt Mitchell <go...@gmail.com>
>>> > To: solr-user@lucene.apache.org
>>> > Sent: Fri, January 22, 2010 9:44:03 AM
>>> > Subject: Re: solr with tomcat in cluster mode
>>> >
>>> > We have a similar setup and I'd be curious to see how folks are doing
>>> this
>>> > as well.
>>> >
>>> > Our setup: A few servers and an F5 load balancer. Each Solr instance
>>> points
>>> > to a shared index. We use a separate server for indexing. When the index
>>> is
>>> > complete, we do some juggling using the Core Admin SWAP function and
>>> update
>>> > the shared index. I've wondered about having a shared index across
>>> multiple
>>> > instances of (read-only) Solr -- any problems there?
>>> >
>>> > Matt
>>> >
>>> > On Fri, Jan 22, 2010 at 9:35 AM, ZAROGKIKAS,GIORGOS <
>>> > g.zarogkikas@multirama.gr> wrote:
>>> >
>>> > > Hi
>>> > > I'm using solr 1.4 with tomcat in a single pc
>>> > > and I want to turn it in cluster mode with 2 nodes and load
>>> > > balancing
>>> > > But I can't find info how to do
>>> > > Is there any manual or a recorded procedure on the internet to
>>> > > do that
>>> > > Or is there anyone to help me ?
>>> > >
>>> > > Thanks in advance
>>> > >
>>> > >
>>> > > Ps : I use windows server 2008 for OS
>>> > >
>>> > >
>>> > >
>>> > >
>>> > >
>>>
>>>
>>
>
>
>
> --
> Lance Norskog
> goksron@gmail.com
>
--
Lance Norskog
goksron@gmail.com
RE: solr with tomcat in cluster mode
Posted by "ZAROGKIKAS,GIORGOS" <g....@multirama.gr>.
Windows ????
I mention below that I user windows server 2008
-----Original Message-----
From: Lance Norskog [mailto:goksron@gmail.com]
Sent: Thursday, January 28, 2010 3:46 AM
To: solr-user@lucene.apache.org
Subject: Re: solr with tomcat in cluster mode
Linux includes a load-balancer program 'balance'. You set it up at a
third port and configure it to use 'localhost:8180' and
'localhost:8280'.
On Wed, Jan 27, 2010 at 4:06 AM, ZAROGKIKAS,GIORGOS
<g....@multirama.gr> wrote:
> Hi again
> I finally setup my solr Cluster with tomcat6
> The configuration I user is two tomcat servers on the same server in different ports(ex localhost:8180/solr and
> Localhost:8280/solr for testing purposes) with different indexes on each server and index replication through replication handler of solr , and its working fine for me and very quick
>
> Now I want to use load balance for these two tomcat servers but without using apache http server
> Is there any solution for that ???
>
>
>
>
>
>
> -----Original Message-----
> From: Matt Mitchell [mailto:goodieboy@gmail.com]
> Sent: Friday, January 22, 2010 9:33 PM
> To: solr-user@lucene.apache.org
> Subject: Re: solr with tomcat in cluster mode
>
> Hey Otis,
>
> We're indexing on a separate machine because we want to keep our production
> nodes away from processes like indexing. The indexing server also has a ton
> of resources available, more so than the production nodes. We set it up as
> an indexing server at one point and have decided to stick with it.
>
> We're not indexing the same index as the search indexes because we want to
> be able to step back a day or two if needed. So we do the SWAP when things
> are done and OK.
>
> So that last part you mentioned about the searchers needing to re-open will
> happen with a SWAP right? Is your concern that there will be a lag time,
> making it so the slaves will be out of sync for some small period of time?
>
> Would it be simpler/better to move to using Solrs native slave/master
> feature?
>
> I'd love to hear any suggestions you might have.
>
> Thanks,
>
> Matt
>
> On Fri, Jan 22, 2010 at 1:58 PM, Otis Gospodnetic <
> otis_gospodnetic@yahoo.com> wrote:
>
>> This should work fine.
>> But why are you indexing to a separate index/core? Why not index in the
>> very same index you are searching?
>> Slaves won't see changes until their searchers re-open.
>>
>> Otis
>> --
>> Sematext -- http://sematext.com/ -- Solr - Lucene - Nutch
>>
>>
>>
>> ----- Original Message ----
>> > From: Matt Mitchell <go...@gmail.com>
>> > To: solr-user@lucene.apache.org
>> > Sent: Fri, January 22, 2010 9:44:03 AM
>> > Subject: Re: solr with tomcat in cluster mode
>> >
>> > We have a similar setup and I'd be curious to see how folks are doing
>> this
>> > as well.
>> >
>> > Our setup: A few servers and an F5 load balancer. Each Solr instance
>> points
>> > to a shared index. We use a separate server for indexing. When the index
>> is
>> > complete, we do some juggling using the Core Admin SWAP function and
>> update
>> > the shared index. I've wondered about having a shared index across
>> multiple
>> > instances of (read-only) Solr -- any problems there?
>> >
>> > Matt
>> >
>> > On Fri, Jan 22, 2010 at 9:35 AM, ZAROGKIKAS,GIORGOS <
>> > g.zarogkikas@multirama.gr> wrote:
>> >
>> > > Hi
>> > > I'm using solr 1.4 with tomcat in a single pc
>> > > and I want to turn it in cluster mode with 2 nodes and load
>> > > balancing
>> > > But I can't find info how to do
>> > > Is there any manual or a recorded procedure on the internet to
>> > > do that
>> > > Or is there anyone to help me ?
>> > >
>> > > Thanks in advance
>> > >
>> > >
>> > > Ps : I use windows server 2008 for OS
>> > >
>> > >
>> > >
>> > >
>> > >
>>
>>
>
--
Lance Norskog
goksron@gmail.com
Re: solr with tomcat in cluster mode
Posted by Lance Norskog <go...@gmail.com>.
Linux includes a load-balancer program 'balance'. You set it up at a
third port and configure it to use 'localhost:8180' and
'localhost:8280'.
On Wed, Jan 27, 2010 at 4:06 AM, ZAROGKIKAS,GIORGOS
<g....@multirama.gr> wrote:
> Hi again
> I finally setup my solr Cluster with tomcat6
> The configuration I user is two tomcat servers on the same server in different ports(ex localhost:8180/solr and
> Localhost:8280/solr for testing purposes) with different indexes on each server and index replication through replication handler of solr , and its working fine for me and very quick
>
> Now I want to use load balance for these two tomcat servers but without using apache http server
> Is there any solution for that ???
>
>
>
>
>
>
> -----Original Message-----
> From: Matt Mitchell [mailto:goodieboy@gmail.com]
> Sent: Friday, January 22, 2010 9:33 PM
> To: solr-user@lucene.apache.org
> Subject: Re: solr with tomcat in cluster mode
>
> Hey Otis,
>
> We're indexing on a separate machine because we want to keep our production
> nodes away from processes like indexing. The indexing server also has a ton
> of resources available, more so than the production nodes. We set it up as
> an indexing server at one point and have decided to stick with it.
>
> We're not indexing the same index as the search indexes because we want to
> be able to step back a day or two if needed. So we do the SWAP when things
> are done and OK.
>
> So that last part you mentioned about the searchers needing to re-open will
> happen with a SWAP right? Is your concern that there will be a lag time,
> making it so the slaves will be out of sync for some small period of time?
>
> Would it be simpler/better to move to using Solrs native slave/master
> feature?
>
> I'd love to hear any suggestions you might have.
>
> Thanks,
>
> Matt
>
> On Fri, Jan 22, 2010 at 1:58 PM, Otis Gospodnetic <
> otis_gospodnetic@yahoo.com> wrote:
>
>> This should work fine.
>> But why are you indexing to a separate index/core? Why not index in the
>> very same index you are searching?
>> Slaves won't see changes until their searchers re-open.
>>
>> Otis
>> --
>> Sematext -- http://sematext.com/ -- Solr - Lucene - Nutch
>>
>>
>>
>> ----- Original Message ----
>> > From: Matt Mitchell <go...@gmail.com>
>> > To: solr-user@lucene.apache.org
>> > Sent: Fri, January 22, 2010 9:44:03 AM
>> > Subject: Re: solr with tomcat in cluster mode
>> >
>> > We have a similar setup and I'd be curious to see how folks are doing
>> this
>> > as well.
>> >
>> > Our setup: A few servers and an F5 load balancer. Each Solr instance
>> points
>> > to a shared index. We use a separate server for indexing. When the index
>> is
>> > complete, we do some juggling using the Core Admin SWAP function and
>> update
>> > the shared index. I've wondered about having a shared index across
>> multiple
>> > instances of (read-only) Solr -- any problems there?
>> >
>> > Matt
>> >
>> > On Fri, Jan 22, 2010 at 9:35 AM, ZAROGKIKAS,GIORGOS <
>> > g.zarogkikas@multirama.gr> wrote:
>> >
>> > > Hi
>> > > I'm using solr 1.4 with tomcat in a single pc
>> > > and I want to turn it in cluster mode with 2 nodes and load
>> > > balancing
>> > > But I can't find info how to do
>> > > Is there any manual or a recorded procedure on the internet to
>> > > do that
>> > > Or is there anyone to help me ?
>> > >
>> > > Thanks in advance
>> > >
>> > >
>> > > Ps : I use windows server 2008 for OS
>> > >
>> > >
>> > >
>> > >
>> > >
>>
>>
>
--
Lance Norskog
goksron@gmail.com
RE: solr with tomcat in cluster mode
Posted by "ZAROGKIKAS,GIORGOS" <g....@multirama.gr>.
Hi again
I finally setup my solr Cluster with tomcat6
The configuration I user is two tomcat servers on the same server in different ports(ex localhost:8180/solr and
Localhost:8280/solr for testing purposes) with different indexes on each server and index replication through replication handler of solr , and its working fine for me and very quick
Now I want to use load balance for these two tomcat servers but without using apache http server
Is there any solution for that ???
-----Original Message-----
From: Matt Mitchell [mailto:goodieboy@gmail.com]
Sent: Friday, January 22, 2010 9:33 PM
To: solr-user@lucene.apache.org
Subject: Re: solr with tomcat in cluster mode
Hey Otis,
We're indexing on a separate machine because we want to keep our production
nodes away from processes like indexing. The indexing server also has a ton
of resources available, more so than the production nodes. We set it up as
an indexing server at one point and have decided to stick with it.
We're not indexing the same index as the search indexes because we want to
be able to step back a day or two if needed. So we do the SWAP when things
are done and OK.
So that last part you mentioned about the searchers needing to re-open will
happen with a SWAP right? Is your concern that there will be a lag time,
making it so the slaves will be out of sync for some small period of time?
Would it be simpler/better to move to using Solrs native slave/master
feature?
I'd love to hear any suggestions you might have.
Thanks,
Matt
On Fri, Jan 22, 2010 at 1:58 PM, Otis Gospodnetic <
otis_gospodnetic@yahoo.com> wrote:
> This should work fine.
> But why are you indexing to a separate index/core? Why not index in the
> very same index you are searching?
> Slaves won't see changes until their searchers re-open.
>
> Otis
> --
> Sematext -- http://sematext.com/ -- Solr - Lucene - Nutch
>
>
>
> ----- Original Message ----
> > From: Matt Mitchell <go...@gmail.com>
> > To: solr-user@lucene.apache.org
> > Sent: Fri, January 22, 2010 9:44:03 AM
> > Subject: Re: solr with tomcat in cluster mode
> >
> > We have a similar setup and I'd be curious to see how folks are doing
> this
> > as well.
> >
> > Our setup: A few servers and an F5 load balancer. Each Solr instance
> points
> > to a shared index. We use a separate server for indexing. When the index
> is
> > complete, we do some juggling using the Core Admin SWAP function and
> update
> > the shared index. I've wondered about having a shared index across
> multiple
> > instances of (read-only) Solr -- any problems there?
> >
> > Matt
> >
> > On Fri, Jan 22, 2010 at 9:35 AM, ZAROGKIKAS,GIORGOS <
> > g.zarogkikas@multirama.gr> wrote:
> >
> > > Hi
> > > I'm using solr 1.4 with tomcat in a single pc
> > > and I want to turn it in cluster mode with 2 nodes and load
> > > balancing
> > > But I can't find info how to do
> > > Is there any manual or a recorded procedure on the internet to
> > > do that
> > > Or is there anyone to help me ?
> > >
> > > Thanks in advance
> > >
> > >
> > > Ps : I use windows server 2008 for OS
> > >
> > >
> > >
> > >
> > >
>
>
Re: solr with tomcat in cluster mode
Posted by Matt Mitchell <go...@gmail.com>.
Hey Otis,
We're indexing on a separate machine because we want to keep our production
nodes away from processes like indexing. The indexing server also has a ton
of resources available, more so than the production nodes. We set it up as
an indexing server at one point and have decided to stick with it.
We're not indexing the same index as the search indexes because we want to
be able to step back a day or two if needed. So we do the SWAP when things
are done and OK.
So that last part you mentioned about the searchers needing to re-open will
happen with a SWAP right? Is your concern that there will be a lag time,
making it so the slaves will be out of sync for some small period of time?
Would it be simpler/better to move to using Solrs native slave/master
feature?
I'd love to hear any suggestions you might have.
Thanks,
Matt
On Fri, Jan 22, 2010 at 1:58 PM, Otis Gospodnetic <
otis_gospodnetic@yahoo.com> wrote:
> This should work fine.
> But why are you indexing to a separate index/core? Why not index in the
> very same index you are searching?
> Slaves won't see changes until their searchers re-open.
>
> Otis
> --
> Sematext -- http://sematext.com/ -- Solr - Lucene - Nutch
>
>
>
> ----- Original Message ----
> > From: Matt Mitchell <go...@gmail.com>
> > To: solr-user@lucene.apache.org
> > Sent: Fri, January 22, 2010 9:44:03 AM
> > Subject: Re: solr with tomcat in cluster mode
> >
> > We have a similar setup and I'd be curious to see how folks are doing
> this
> > as well.
> >
> > Our setup: A few servers and an F5 load balancer. Each Solr instance
> points
> > to a shared index. We use a separate server for indexing. When the index
> is
> > complete, we do some juggling using the Core Admin SWAP function and
> update
> > the shared index. I've wondered about having a shared index across
> multiple
> > instances of (read-only) Solr -- any problems there?
> >
> > Matt
> >
> > On Fri, Jan 22, 2010 at 9:35 AM, ZAROGKIKAS,GIORGOS <
> > g.zarogkikas@multirama.gr> wrote:
> >
> > > Hi
> > > I'm using solr 1.4 with tomcat in a single pc
> > > and I want to turn it in cluster mode with 2 nodes and load
> > > balancing
> > > But I can't find info how to do
> > > Is there any manual or a recorded procedure on the internet to
> > > do that
> > > Or is there anyone to help me ?
> > >
> > > Thanks in advance
> > >
> > >
> > > Ps : I use windows server 2008 for OS
> > >
> > >
> > >
> > >
> > >
>
>
Re: solr with tomcat in cluster mode
Posted by Otis Gospodnetic <ot...@yahoo.com>.
This should work fine.
But why are you indexing to a separate index/core? Why not index in the very same index you are searching?
Slaves won't see changes until their searchers re-open.
Otis
--
Sematext -- http://sematext.com/ -- Solr - Lucene - Nutch
----- Original Message ----
> From: Matt Mitchell <go...@gmail.com>
> To: solr-user@lucene.apache.org
> Sent: Fri, January 22, 2010 9:44:03 AM
> Subject: Re: solr with tomcat in cluster mode
>
> We have a similar setup and I'd be curious to see how folks are doing this
> as well.
>
> Our setup: A few servers and an F5 load balancer. Each Solr instance points
> to a shared index. We use a separate server for indexing. When the index is
> complete, we do some juggling using the Core Admin SWAP function and update
> the shared index. I've wondered about having a shared index across multiple
> instances of (read-only) Solr -- any problems there?
>
> Matt
>
> On Fri, Jan 22, 2010 at 9:35 AM, ZAROGKIKAS,GIORGOS <
> g.zarogkikas@multirama.gr> wrote:
>
> > Hi
> > I'm using solr 1.4 with tomcat in a single pc
> > and I want to turn it in cluster mode with 2 nodes and load
> > balancing
> > But I can't find info how to do
> > Is there any manual or a recorded procedure on the internet to
> > do that
> > Or is there anyone to help me ?
> >
> > Thanks in advance
> >
> >
> > Ps : I use windows server 2008 for OS
> >
> >
> >
> >
> >
Re: solr with tomcat in cluster mode
Posted by Matt Mitchell <go...@gmail.com>.
We have a similar setup and I'd be curious to see how folks are doing this
as well.
Our setup: A few servers and an F5 load balancer. Each Solr instance points
to a shared index. We use a separate server for indexing. When the index is
complete, we do some juggling using the Core Admin SWAP function and update
the shared index. I've wondered about having a shared index across multiple
instances of (read-only) Solr -- any problems there?
Matt
On Fri, Jan 22, 2010 at 9:35 AM, ZAROGKIKAS,GIORGOS <
g.zarogkikas@multirama.gr> wrote:
> Hi
> I'm using solr 1.4 with tomcat in a single pc
> and I want to turn it in cluster mode with 2 nodes and load
> balancing
> But I can't find info how to do
> Is there any manual or a recorded procedure on the internet to
> do that
> Or is there anyone to help me ?
>
> Thanks in advance
>
>
> Ps : I use windows server 2008 for OS
>
>
>
>
>
solr with tomcat in cluster mode
Posted by "ZAROGKIKAS,GIORGOS" <g....@multirama.gr>.
Hi
I'm using solr 1.4 with tomcat in a single pc
and I want to turn it in cluster mode with 2 nodes and load
balancing
But I can't find info how to do
Is there any manual or a recorded procedure on the internet to
do that
Or is there anyone to help me ?
Thanks in advance
Ps : I use windows server 2008 for OS
Re: solr blocking on commit
Posted by Otis Gospodnetic <ot...@yahoo.com>.
Hi,
I'm missing the bigger context of this thread here, but from the snippet below - sure, commits cause in-memory index to get written to disk, that causes some IO, and that *could* affect search *if* queries are running on the same box. When index and/or query volume is high, one typically puts indexing and searching on different servers.
Otis
--
Sematext -- http://sematext.com/ -- Solr - Lucene - Nutch
----- Original Message ----
> From: Steve Conover <sc...@gmail.com>
> To: solr-user@lucene.apache.org
> Sent: Thu, January 21, 2010 1:00:05 AM
> Subject: Re: solr blocking on commit
>
> > How solr organized so that search can continue when a commit has closed the
> > index?
> > Also, looking at lucene docs, commit causes a system fsync(). Won't search
> > also
> > get blocked by the IO traffic generated?
>
>
> ...I'll run iostat too and see if there's anything interesting to report
Re: solr blocking on commit
Posted by Steve Conover <sc...@gmail.com>.
> How solr organized so that search can continue when a commit has closed the
> index?
> Also, looking at lucene docs, commit causes a system fsync(). Won't search
> also
> get blocked by the IO traffic generated?
...I'll run iostat too and see if there's anything interesting to report
Re: solr blocking on commit
Posted by Jerome L Quinn <jl...@us.ibm.com>.
yseeley@gmail.com wrote on 01/20/2010 02:24:04 PM:
> On Wed, Jan 20, 2010 at 2:18 PM, Jerome L Quinn <jl...@us.ibm.com>
wrote:
> > This is essentially the same problem I'm fighting with. Once in a
while,
> > commit
> > causes everything to freeze, causing add commands to timeout.
>
> This could be a bit different. Commits do currently block other
> update operations such as adds, but not searches.
How solr organized so that search can continue when a commit has closed the
index?
Also, looking at lucene docs, commit causes a system fsync(). Won't search
also
get blocked by the IO traffic generated?
Thanks,
Jerry
Re: solr blocking on commit
Posted by Jerome L Quinn <jl...@us.ibm.com>.
yseeley@gmail.com wrote on 01/20/2010 02:24:04 PM:
> On Wed, Jan 20, 2010 at 2:18 PM, Jerome L Quinn <jl...@us.ibm.com>
wrote:
> > This is essentially the same problem I'm fighting with. Once in a
while,
> > commit
> > causes everything to freeze, causing add commands to timeout.
>
> This could be a bit different. Commits do currently block other
> update operations such as adds, but not searches.
Ah, this is good to know. Is there any logging in solr 1.3 I could turn on
to verify that this is indeed what's happening for me?
Thanks,
Jerry
Re: solr blocking on commit
Posted by Yonik Seeley <yo...@lucidimagination.com>.
On Wed, Jan 20, 2010 at 2:18 PM, Jerome L Quinn <jl...@us.ibm.com> wrote:
> This is essentially the same problem I'm fighting with. Once in a while,
> commit
> causes everything to freeze, causing add commands to timeout.
This could be a bit different. Commits do currently block other
update operations such as adds, but not searches.
-Yonik
http://www.lucidimagination.com
Re: solr blocking on commit
Posted by Jerome L Quinn <jl...@us.ibm.com>.
yseeley@gmail.com wrote on 01/19/2010 06:05:45 PM:
> On Tue, Jan 19, 2010 at 5:57 PM, Steve Conover <sc...@gmail.com>
wrote:
> > I'm using latest solr 1.4 with java 1.6 on linux. I have a 3M
> > document index that's 10+GB. We currently give solr 12GB of ram to
> > play in and our machine has 32GB total.
> >
> > We're seeing a problem where solr blocks during commit - it won't
> > server /select requests - in some cases for more than 15-30 seconds.
> > We'd like to somehow configure things such that there's no
> > interruption in /select service.
>
> A commit shouldn't cause searches to block.
> Could this perhaps be a stop-the-word GC pause that coincides with the
commit?
This is essentially the same problem I'm fighting with. Once in a while,
commit
causes everything to freeze, causing add commands to timeout.
My large index sees pauses on the order of 50 seconds once every day or
two. I
have a small index of 700M on disk that sees 20 second pauses once in a
while.
I'm using the IBM 1.6 jvm on linux.
Jerry
Re: solr blocking on commit
Posted by Jay Hill <ja...@gmail.com>.
A couple of follow up questions:
- What type of garbage collector is in use?
- How often are you optimizing the index?
- In solrconfig.xml what is the setting for <mainIndex><ramBufferSizeMB>?
- Right before and after you see this pause, check the output of
http://<host>:<port>/solr/admin/system,
specifically the output of <jvm><memory> and send this to the list.
If possible definitely watch memory usage with something like JConsole, or
start the JVM with some of these params:
–XX:+PrintGCDetails
–XX:+PrintGCTimeStamps
-Jay
On Tue, Jan 19, 2010 at 5:16 PM, Steve Conover <sc...@gmail.com> wrote:
> I'll play with the GC settings and watch memory usage (I've done a
> little bit of this already), but I have a sense that this isn't the
> problem.
>
> I should also note that in order to create the really long pauses I
> need to post xml files full of documents that haven't been added in a
> long time / ever. Once a set of documents is posted to /update, if I
> re-post it solr behaves pretty well - and that's true even if I
> restart solr.
>
> On Tue, Jan 19, 2010 at 3:05 PM, Yonik Seeley
> <yo...@lucidimagination.com> wrote:
> > On Tue, Jan 19, 2010 at 5:57 PM, Steve Conover <sc...@gmail.com>
> wrote:
> >> I'm using latest solr 1.4 with java 1.6 on linux. I have a 3M
> >> document index that's 10+GB. We currently give solr 12GB of ram to
> >> play in and our machine has 32GB total.
> >>
> >> We're seeing a problem where solr blocks during commit - it won't
> >> server /select requests - in some cases for more than 15-30 seconds.
> >> We'd like to somehow configure things such that there's no
> >> interruption in /select service.
> >
> > A commit shouldn't cause searches to block.
> > Could this perhaps be a stop-the-word GC pause that coincides with the
> commit?
> >
> > -Yonik
> > http://www.lucidimagination.com
> >
>
Re: solr blocking on commit
Posted by Steve Conover <sc...@gmail.com>.
I'll play with the GC settings and watch memory usage (I've done a
little bit of this already), but I have a sense that this isn't the
problem.
I should also note that in order to create the really long pauses I
need to post xml files full of documents that haven't been added in a
long time / ever. Once a set of documents is posted to /update, if I
re-post it solr behaves pretty well - and that's true even if I
restart solr.
On Tue, Jan 19, 2010 at 3:05 PM, Yonik Seeley
<yo...@lucidimagination.com> wrote:
> On Tue, Jan 19, 2010 at 5:57 PM, Steve Conover <sc...@gmail.com> wrote:
>> I'm using latest solr 1.4 with java 1.6 on linux. I have a 3M
>> document index that's 10+GB. We currently give solr 12GB of ram to
>> play in and our machine has 32GB total.
>>
>> We're seeing a problem where solr blocks during commit - it won't
>> server /select requests - in some cases for more than 15-30 seconds.
>> We'd like to somehow configure things such that there's no
>> interruption in /select service.
>
> A commit shouldn't cause searches to block.
> Could this perhaps be a stop-the-word GC pause that coincides with the commit?
>
> -Yonik
> http://www.lucidimagination.com
>
Re: solr blocking on commit
Posted by Yonik Seeley <yo...@lucidimagination.com>.
On Tue, Jan 19, 2010 at 5:57 PM, Steve Conover <sc...@gmail.com> wrote:
> I'm using latest solr 1.4 with java 1.6 on linux. I have a 3M
> document index that's 10+GB. We currently give solr 12GB of ram to
> play in and our machine has 32GB total.
>
> We're seeing a problem where solr blocks during commit - it won't
> server /select requests - in some cases for more than 15-30 seconds.
> We'd like to somehow configure things such that there's no
> interruption in /select service.
A commit shouldn't cause searches to block.
Could this perhaps be a stop-the-word GC pause that coincides with the commit?
-Yonik
http://www.lucidimagination.com