: We will take this approach in our production environment but meanwhile I am
: curious if this issue will be addressed: it seems the new/first searchers do
: not really buy any performance benefits because it uses so much memory,
: especially at core loading time.
There's nothing inheriently wro
just a blind shot (didn't read the full thread):
what is your maxWarmingSearchers settings? For large indices we set it
to 2 (maximum)
Regards,
Peter.
> just update on this issue...
>
> we turned off the new/first searchers (upgrade to Solr 1.4.1), and ran
> benchmark tests, there is no noticeabl
just update on this issue...
we turned off the new/first searchers (upgrade to Solr 1.4.1), and ran
benchmark tests, there is no noticeable performance impact on the queries we
perform comparing with Solr 1.3 benchmark tests WITH new/first searchers.
Also the memory usage reduced by 5.5 GB after
Hi Yonik,
I tried the fix suggested in your comments (using "solr.TrieDateField" ),
and it loaded up 130 cores in 1 minute, 1.3GB memory (a little more than 1GB
when turning off static warm cache, and much less than 6.5GB when use
'solr.DateField').
Will this have any impact on first query or per
Could Solr just load cores one at a time, waiting for loader events to
finish? Or continuously stage 2 or three simultaneously?
On Sat, Oct 2, 2010 at 7:08 AM, Yonik Seeley wrote:
> On Fri, Oct 1, 2010 at 5:42 PM, Renee Sun wrote:
>> Hi Yonik,
>>
>> I attached the solrconfig.xml to you in previo
On Fri, Oct 1, 2010 at 5:42 PM, Renee Sun wrote:
> Hi Yonik,
>
> I attached the solrconfig.xml to you in previous post, and we do have
> firstSearch and newSearch hook ups.
>
> I commented them out, all 130 cores loaded up in 1 minute, same as in solr
> 1.3. total memory took about 1GB. Whereas i
e:
> From: Renee Sun
> Subject: Re: Upgrade to Solr 1.4, very slow at start up when loading all cores
> To: solr-user@lucene.apache.org
> Date: Friday, October 1, 2010, 2:42 PM
>
> Hi Yonik,
>
> I attached the solrconfig.xml to you in previous post, and
> we do have
> fi
http://lucene.472066.n3.nabble.com/file/n1617135/solrconfig.xml
solrconfig.xml
Hi Yonik,
I have uploaded our solrconfig.xml file for your reference.
we also tried 1.4.1, for same index data, it took about 30-55 minutes to
load up all 130 cores, it did not help at all.
There is no query running
Hi Yonik,
I attached the solrconfig.xml to you in previous post, and we do have
firstSearch and newSearch hook ups.
I commented them out, all 130 cores loaded up in 1 minute, same as in solr
1.3. total memory took about 1GB. Whereas in 1.3, with hook ups, it took
about 6.5GB for same amount of
On Thu, Sep 30, 2010 at 4:52 PM, Renee Sun wrote:
> - do you have any warming queries configured?
> > no, all autowarmingcount are set to 0 for all caches
Any static warming requests though (newSearcher / firstSearcher hooks
in solrconfig.xml)?
Is anything at all querying these cores while y
Hi Yonik,
thanks for your reply.
I entered a bug for this at :
https://issues.apache.org/jira/browse/SOLR-2138
to answer your questions here:
- do you have any warming queries configured?
> no, all autowarmingcount are set to 0 for all caches
- do the cores have documents already, and i
On Thu, Sep 30, 2010 at 10:41 AM, Renee Sun wrote:
>
> Hi -
> I posted this problem but no response, I guess I need to post this in the
> Solr-User forum. Hopefully you will help me on this.
>
> We were running Solr 1.3 for long time, with 130 cores. Just upgrade to Solr
> 1.
Hi -
I posted this problem but no response, I guess I need to post this in the
Solr-User forum. Hopefully you will help me on this.
We were running Solr 1.3 for long time, with 130 cores. Just upgrade to Solr
1.4, then when we start the Solr, it took about 45 minutes. The catalina.log
shows Solr
Hi all,
I had DataImportHandler working perfectly on Solr 1.4 nightly build from
June 2009. I upgraded the Solr to 1.4 release and started getting errors:
Caused by: com.mysql.jdbc.exceptions.MySQLNonTransientConnectionException:
Server connection failure during transaction. Due to underlying
On Fri, Nov 20, 2009 at 10:26 AM, kalidoss
wrote:
> In version 1.3 EventDate field type is date, In 1.4 also its date But we are
> getting the following error.
Use the schema you had with 1.3 and it should work. The example
schemas are not backward compatible with an index built with the
previou
In version 1.3 EventDate field type is date, In 1.4 also its date But we
are getting the following error.
name="EventDate">ERROR:SCHEMA-INDEX-MISMATCH,stringValue=2008-05-16T07:19:28
-kalidoss.m,
kalidoss wrote:
Even i want to upgrade from v1.3 to 1.4
I did 1.3 index directory replace with
Even i want to upgrade from v1.3 to 1.4
I did 1.3 index directory replace with 1.4 and associated schema changes
in that. Its throwing lot of exception like datatype mismatch with
Integer, String, Date, etc. Even the results are coming with some error
example: "name="Alias">ERROR:SCHEMA-INDEX
0530
> To:
> Subject: Re: Upgrade to solr 1.4
>
> On Fri, Jun 26, 2009 at 9:11 PM, Walter Underwood
> wrote:
>
>> Netflix is running a nightly build from May in production. We did our
>> normal QA on it, then ran it on one of our five servers for two weeks.
>> No problem
We are using the script replication. I have no interest in spending time
configuring and QA'ing a different method when the scripts work fine.
We are running the nightly from 2009-05-11.
wunder
On 6/26/09 8:51 AM, "Shalin Shekhar Mangar" wrote:
> On Fri, Jun 26, 2009 at 9:11 PM, Walter Underwo
On Fri, Jun 26, 2009 at 9:11 PM, Walter Underwood wrote:
> Netflix is running a nightly build from May in production. We did our
> normal QA on it, then ran it on one of our five servers for two weeks.
> No problems. It is handling about 10% more traffic with 10% less CPU.
>
Wow, that is good new
Netflix is running a nightly build from May in production. We did our
normal QA on it, then ran it on one of our five servers for two weeks.
No problems. It is handling about 10% more traffic with 10% less CPU.
We deployed 1.4 to all our servers yesterday.
wunder
On 6/26/09 7:58 AM, "Julian Davc
Solr in general is fairly stable in trunk. That isn't to say that a
critical error can't get through, because that does happen, but the
test suite is pretty comprehensive. With Solr 1.4 getting closer and
closer, I think you'll see the pace of change dropping off.
I think it's one of tho
David Baker wrote:
> Hi,
>
> I need to upgrade from solr 1.3 to solr 1.4. I was wondering if there
> is a particular revision of 1.4 that I should use that is considered
> very stable for a production environment?
Well it it's not pronounced stable and given in download page I don't
think you can
Hi,
I need to upgrade from solr 1.3 to solr 1.4. I was wondering if there
is a particular revision of 1.4 that I should use that is considered
very stable for a production environment?
24 matches
Mail list logo
