, 2011 at 3:46 PM, Maduranga Kannangara wrote:
> Hi All,
>
> We use Solr 1.4.1. Single core setup with a repeater (for QA) and a few
> slaves (for Production).
>
> Master will index many sources and make data ready. Once all data is
> "ready-for-production", optimiza
Hi All,
We use Solr 1.4.1. Single core setup with a repeater (for QA) and a few
slaves (for Production).
Master will index many sources and make data ready. Once all data is
"ready-for-production", optimization will take place. On master
"replicateAfter" is set to "optimize". (Subsequently on rep
consumption.
Regards
Aditya
http://www.findbestopensource.com
On Fri, May 14, 2010 at 11:14 AM, Maduranga Kannangara <
mkannang...@infomedia.com.au> wrote:
> But even we used a single index, we were running out of memory.
> What do you mean by "active"? No queries on t
active and loaded all
its terms in memory. Memory consumption will be certainly more.
Regards
Aditya
http://www.findbestopensource.com
On Fri, May 14, 2010 at 10:28 AM, Maduranga Kannangara <
mkannang...@infomedia.com.au> wrote:
> Hi
>
> We use separate JVMs to Index and Query.
> (Cl
Hi
We use separate JVMs to Index and Query.
(Client applications will query only slaves,
while master does only indexing)
Recently we moved a two master indexes to
a single JVM. Our memory allocation was for
each index was 512Mb and 1Gb.
Once we moved both indexes to a single VM,
we thought it w
Hi All,
Recently we noticed that some of our heavy load Solr instances are facing
memory leak kind situations.
It goes onto Full GC and as it was unable to release any memory, the broken
pripe and socket errors happen.
(This happens both in Solr 1.3 and 1.4 for us.)
Is there a good tool (prefe
n; but every site is different.
On Mon, Dec 21, 2009 at 7:54 PM, Maduranga Kannangara
wrote:
> Hi All,
>
> We're trying to replicate indexes on Solr 1.3 across from
> Dev->QA->Staging->Prod etc.
> So at each stage other than Dev and Prod, each would live as a master an
Hi All,
We're trying to replicate indexes on Solr 1.3 across from
Dev->QA->Staging->Prod etc.
So at each stage other than Dev and Prod, each would live as a master and a
slave at a given time.
We hit a bottle neck (may be?) when we try to start rsyncd-start on the master
from the slave machine
}
I believe, if this makes sense, we should add this simple line in Lucene! :-)
However, since Java Replication in Solr 1.4, an application level process,
should have already solved this issue in another way as well.
Yet to test it.
Thanks
Madu
-Original Message-
From: Maduranga
ly for NFS.
Maduranga Kannangara wrote:
> Just found out the root cause:
>
> * The segments.gen file does not get replicated to slave all the time.
>
> For some reason, this small (20bytes) file lives in memory and does not get
> updated to the master's hard disk. Therefore it i
s Otis and everyone for all your support!
Madu
-Original Message-----
From: Maduranga Kannangara
Sent: Monday, 16 November 2009 12:37 PM
To: solr-user@lucene.apache.org
Subject: RE: Segment file not found error - after replicating
Yes. We have tried Solr 1.4 and so far its been great success.
tis
--
Sematext is hiring -- http://sematext.com/about/jobs.html?mls
Lucene, Solr, Nutch, Katta, Hadoop, HBase, UIMA, NLP, NER, IR
- Original Message
> From: Maduranga Kannangara
> To: "solr-user@lucene.apache.org"
> Sent: Tue, November 10, 2009 5:42:44 PM
> Subj
index/on/slave/without/errors
du -s /path/to/index/on/slave/with/errors
Otis
--
Sematext is hiring -- http://sematext.com/about/jobs.html?mls
Lucene, Solr, Nutch, Katta, Hadoop, HBase, UIMA, NLP, NER, IR
- Original Message
> From: Maduranga Kannangara
> To: "solr-user@l
n the logs for any of the scripts involved in replication in 1.3?
Otis
--
Sematext is hiring -- http://sematext.com/about/jobs.html?mls
Lucene, Solr, Nutch, Katta, Hadoop, HBase, UIMA, NLP, NER, IR
- Original Message
> From: Maduranga Kannangara
> To: "solr-user@lucene.apache.o
Hi guys,
We use Solr 1.3 for indexing large amounts of data (50G avg) on Linux
environment and use the replication scripts to make replicas those live in load
balancing slaves.
The issue we face quite often (only in Linux servers) is that they tend to not
been able to find the segment file (se
15 matches
Mail list logo