Prons an Cons of Startup Lazy a Handler?

[Furkan KAMACI <fu...@gmail.com>]

I will use SolrCloud and theis main purpose will be rich document indexing.
Solr example includes that definition:

<requestHandler name="/update/extract"
startup="lazy"class="solr.extraction.ExtractingRequestHandler" >

it startups it lazy. So what is pros and cons for removing it for my
situation?

Re: Prons an Cons of Startup Lazy a Handler?

[Furkan KAMACI <fu...@gmail.com>]

Thanks for the answers.

2013/4/26 Chris Hostetter <ho...@fucit.org>

>
> : In short, whether you want to keep the handler is completely independent
> of
> : the lazy startup option.
>
> I think Jack missread your question -- my interpretation is that you are
> asking about the pros/cons of removing 'startup="lazy"' ...
>
> : <requestHandler name="/update/extract"
> : startup="lazy"class="solr.extraction.ExtractingRequestHandler" >
> :
> : it startups it lazy. So what is pros and cons for removing it for my
> : situation?
>
> ...if you know you will definitely be using this handler, then you should
> probably remove startup="lazy" -- the advantages of using lazy request
> handlers is that there is no "init cost" for having them in your config if
> you never use them, making it handy for the example configs that many
> people copy and re-use w/o modifying so that they don't pay any price in
> having features declared that htey don't use.
>
>
> -Hoss
>

Re: Prons an Cons of Startup Lazy a Handler?

[Chris Hostetter <ho...@fucit.org>]

: In short, whether you want to keep the handler is completely independent of
: the lazy startup option.

I think Jack missread your question -- my interpretation is that you are 
asking about the pros/cons of removing 'startup="lazy"' ...

: <requestHandler name="/update/extract"
: startup="lazy"class="solr.extraction.ExtractingRequestHandler" >
: 
: it startups it lazy. So what is pros and cons for removing it for my
: situation? 

...if you know you will definitely be using this handler, then you should 
probably remove startup="lazy" -- the advantages of using lazy request 
handlers is that there is no "init cost" for having them in your config if 
you never use them, making it handy for the example configs that many 
people copy and re-use w/o modifying so that they don't pay any price in 
having features declared that htey don't use.


-Hoss

Re: Prons an Cons of Startup Lazy a Handler?

[Jack Krupansky <ja...@basetechnology.com>]

Lazy startup simply means that you are willing to tolerate a slight delay on 
the first request to that request handler.

It also has the side effect that if there are any problems with starting up 
the handler, they won't be seen until that first request.

In short, whether you want to keep the handler is completely independent of 
the lazy startup option.

-- Jack Krupansky

-----Original Message----- 
From: Furkan KAMACI
Sent: Friday, April 26, 2013 4:01 AM
To: solr-user@lucene.apache.org
Subject: Prons an Cons of Startup Lazy a Handler?

I will use SolrCloud and theis main purpose will be rich document indexing.
Solr example includes that definition:

<requestHandler name="/update/extract"
startup="lazy"class="solr.extraction.ExtractingRequestHandler" >

it startups it lazy. So what is pros and cons for removing it for my
situation?