Hi Prabu,
It's difficult to tell what's going wrong without the full exception stack
trace, including what the exception is.
If you can provide the specific input that triggers the exception, that might
also help.
Steve
On Sep 12, 2013, at 4:14 AM, prabu palanisamy wrote:
> Hi
>
> I tried
Hi
I tried to reindex the solr. I get the regular expression problem. The
steps I followed are
I started the java -jar start.jar
http://localhost:8983/solr/update?stream.body=
*:*
http://localhost:8983/solr/update?stream.body=
I stopped the solr server
I changed indexed and stored tags as false
Be a little careful when extrapolating from disk to memory.
Any fields where you've set stored="true" will put data in
segment files with extensions .fdt and .fdx, see
These are the compressed verbatim copy of the data
for stored fields and have very little impact on
memory required for searching.
@Shawn: Correctly I am trying to reduce the index size. I am working on
reindex the solr with some of the features as indexed and not stored
@Jean: I tried with different caches. It did not show much improvement.
On Fri, Sep 6, 2013 at 3:17 PM, Shawn Heisey wrote:
> On 9/6/2013 2:54 AM, prabu
On 9/6/2013 2:54 AM, prabu palanisamy wrote:
> I am currently using solr -3.5.0, indexed wikipedia dump (50 gb) with
> java 1.6.
> I am searching the solr with text (which is actually twitter tweets) .
> Currently it takes average time of 210 millisecond for each post, out of
> which 200 millisec
anything that is not necessary.
> -Original Message-
> From: prabu palanisamy [mailto:pr...@serendio.com]
> Sent: September-06-13 4:55 AM
> To: solr-user@lucene.apache.org
> Subject: Regarding improving performance of the solr
>
> Hi
>
> I am currently using solr
Hi
I am currently using solr -3.5.0, indexed wikipedia dump (50 gb) with
java 1.6.
I am searching the solr with text (which is actually twitter tweets) .
Currently it takes average time of 210 millisecond for each post, out of
which 200 millisecond is consumed by solr server (QTime). I used th
