Hi,
we are currently facing a new problem while reindexing one of our SOLR
4.4 instances:
We are using SOLR 4.4 getting data via DIH out of a MySQL Server.
The data is constantly growing.
We have reindexed our data a lot of times without any trouble.
The problem can be reproduced.
There is an
noptimized indices; maybe someone else can answer your question.
Lucene's facet module (not yet exposed through Solr) performance
shouldn't change much for optimized vs unoptimized indices.
Mike McCandless
http://blog.mikemccandless.com
On Mon, Jan 13, 2014 at 10:09 AM, Ralf Matulat
w
/freq vector fields per doc]
test: docvalues...OK [0 total doc count; 0 docvalues fields]
No problems were detected with this index.
--
Ralf Matulat
Deutscher Bundestag
Platz der Republik 1
11011 Berlin
Referat IT 1 - Anwendungsadministration
ralf.matu...@bundestag.de
Tel.: 030 - 227
does not hit performance that bad if
the index is not optimized for a period of time. But we like to avoid
getting to much segments at once.
Today I will run one more checkIndex run against the now turned off SOLR
instance.
Maybe there will be some enlightment then.
Bet regards
Ralf Matulat
x-format that is not true anymore?
Btw: The checkIndex failed with 'java.io.FileNotFoundException:', I
guess because I did not stopped the tomcat while checking. So SOLR
created, merged and deleted some segments while checking. I will restart
the check after stoppimg SOLR.
Ki
Hi,
I am currently running into merge-issues while optimizing an index.
To give you some informations:
We are running 4 SOLR Servers with identical OS, VM-Hardware, RAM etc.
Only one Server by now is having issues, the others are fine.
We are running SOLR 4.4.0 with Tomcat 6.0
It was running si
Hi,
I'm using FieldCollapsing to group the results. Example: I search for
/:/ and group by names, like:
|http://localhost:/solr/select/?q=*:*
&group=true
&group.limit=200
&group.query=Jim
e merge process.
--
Ralf Matulat
Deutscher Bundestag
Platz der Republik 1
11011 Berlin
Referat IT 1 - Anwendungsadministration
ralf.matu...@bundestag.de
Tel.: 030 - 227 34260
ilable address space (32
bit is tiny; 64 bit is immense) and then any OS limits imposed.
Mike McCandless
http://blog.mikemccandless.com
On Thu, Sep 22, 2011 at 5:27 AM, Ralf Matulat wrote:
Good morning!
Recently we slipped into an OOME by optimizing our index. It looks like it's
regarding to
Good morning!
Recently we slipped into an OOME by optimizing our index. It looks like
it's regarding to the nio class and the memory-handling.
I'll try to describe the environment, the error and what we did to solve
the problem. Nevertheless, none of our approaches was successful.
The environm
10 matches
Mail list logo