Re: Solr cloud production set up

[Paras Lehana]

Hi Rajdeep,


   1. I assume you had enabled docValues for the facet fields, right?
   2. What does your GC logs tell? Do you get freezes and CPU spikes during
   intervals?
   3. Caching will help in querying. I'll need to see a sample query of
   yours to recommend what you can tweak.


On Tue, 28 Jan 2020 at 19:09, Jason Gerlowski  wrote:

> Hi Rajdeep,
>
> Unfortunately it's near impossible for anyone here to tell you what
> parameters to tweak.  People might take guesses based on their
> individual past experience, but ultimately those are just guesses.
>
> There are just too many variables affecting Solr performance for
> anyone to have a good guess without access to the cluster itself and
> the time and will to dig into it.
>
> Are there GC params that need tweaking?  Very possible, but you'll
> have to look into your gc logs to see how much time is being spent in
> gc.  Are there query params you could be changing?  Very possible, but
> you'll have to identify the types of queries you're submitting and see
> whether the ref-guide offers any information on how to tweak
> performance for those particular qparsers, facets, etc.  Is the number
> of facets the reason for slow queries?  Very possible, but you'll have
> to turn faceting off or run debug=timing and see how what that tells
> you about the QTime's.
>
> Tuning Solr performance is a tough, time consuming process.  I wish
> there was an easier answer for you, but there's not.
>
> Best,
>
> Jason
>
> On Mon, Jan 20, 2020 at 12:06 PM Rajdeep Sahoo
>  wrote:
> >
> > Please suggest anyone
> >
> > On Sun, 19 Jan, 2020, 9:43 AM Rajdeep Sahoo,  >
> > wrote:
> >
> > > Apart from reducing no of facets in the query, is there any other query
> > > params or gc params or heap space or anything else that we need to
> tweak
> > > for improving search response time.
> > >
> > > On Sun, 19 Jan, 2020, 3:15 AM Erick Erickson,  >
> > > wrote:
> > >
> > >> Add =timing to the query and it’ll show you the time each
> component
> > >> takes.
> > >>
> > >> > On Jan 18, 2020, at 1:50 PM, Rajdeep Sahoo <
> rajdeepsahoo2...@gmail.com>
> > >> wrote:
> > >> >
> > >> > Thanks for the suggestion,
> > >> >
> > >> > Is there any way to get the info which operation or which query
> params
> > >> are
> > >> > increasing the response time.
> > >> >
> > >> >
> > >> > On Sat, 18 Jan, 2020, 11:59 PM Dave, 
> > >> wrote:
> > >> >
> > >> >> If you’re not getting values, don’t ask for the facet. Facets are
> > >> >> expensive as hell, maybe you should think more about your query’s
> than
> > >> your
> > >> >> infrastructure, solr cloud won’t help you at all especially if your
> > >> asking
> > >> >> for things you don’t need
> > >> >>
> > >> >>> On Jan 18, 2020, at 1:25 PM, Rajdeep Sahoo <
> > >> rajdeepsahoo2...@gmail.com>
> > >> >> wrote:
> > >> >>>
> > >> >>> We have assigned 16 gb out of 24gb for heap .
> > >> >>> No other process is running on that node.
> > >> >>>
> > >> >>> 200 facets fields are there in the query but we will not be
> getting
> > >> the
> > >> >>> values for each facets for every search.
> > >> >>> There can be max of 50-60 facets for which we will be getting
> values.
> > >> >>>
> > >> >>> We are using caching,is it not going to help.
> > >> >>>
> > >> >>>
> > >> >>>
> > >>  On Sat, 18 Jan, 2020, 11:36 PM Shawn Heisey, <
> apa...@elyograg.org>
> > >> >> wrote:
> > >> 
> > >> > On 1/18/2020 10:09 AM, Rajdeep Sahoo wrote:
> > >> > We are having 2.3 million documents and size is 2.5 gb.
> > >> >  10 core cpu and 24 gb ram . 16 slave nodes.
> > >> >
> > >> >  Still some of the queries are taking 50 sec at solr end.
> > >> > As we are using solr 4.6 .
> > >> >  Other thing is we are having 200 (avg) facet fields  in a
> query.
> > >> > And 30 searchable fields.
> > >> > Is there any way to identify why it is taking 50 sec for a
> query.
> > >> >Multiple concurrent requests are there.
> > >> 
> > >>  Searching 30 fields and computing 200 facets is never going to be
> > >> super
> > >>  fast.  Switching to cloud will not help, and might make it
> slower.
> > >> 
> > >>  Your index is pretty small to a lot of us.  There are people
> running
> > >>  indexes with billions of documents that take terabytes of disk
> space.
> > >> 
> > >>  As Walter mentioned, computing 200 facets is going to require a
> fair
> > >>  amount of heap memory.  One *possible* problem here is that the
> Solr
> > >>  heap size is too small, so a lot of GC is required.  How much of
> the
> > >>  24GB have you assigned to the heap?  Is there any software other
> than
> > >>  Solr running on these nodes?
> > >> 
> > >>  Thanks,
> > >>  Shawn
> > >> 
> > >> >>
> > >>
> > >>
>


-- 
-- 
Regards,

*Paras Lehana* [65871]
Development Engineer, *Auto-Suggest*,
IndiaMART InterMESH Ltd,

11th Floor, Tower 2, Assotech Business Cresterra,
Plot No. 22, Sector 135, Noida, Uttar Pradesh, India 

Re: Solr cloud production set up

[Jason Gerlowski]

Hi Rajdeep,

Unfortunately it's near impossible for anyone here to tell you what
parameters to tweak.  People might take guesses based on their
individual past experience, but ultimately those are just guesses.

There are just too many variables affecting Solr performance for
anyone to have a good guess without access to the cluster itself and
the time and will to dig into it.

Are there GC params that need tweaking?  Very possible, but you'll
have to look into your gc logs to see how much time is being spent in
gc.  Are there query params you could be changing?  Very possible, but
you'll have to identify the types of queries you're submitting and see
whether the ref-guide offers any information on how to tweak
performance for those particular qparsers, facets, etc.  Is the number
of facets the reason for slow queries?  Very possible, but you'll have
to turn faceting off or run debug=timing and see how what that tells
you about the QTime's.

Tuning Solr performance is a tough, time consuming process.  I wish
there was an easier answer for you, but there's not.

Best,

Jason

On Mon, Jan 20, 2020 at 12:06 PM Rajdeep Sahoo
 wrote:
>
> Please suggest anyone
>
> On Sun, 19 Jan, 2020, 9:43 AM Rajdeep Sahoo, 
> wrote:
>
> > Apart from reducing no of facets in the query, is there any other query
> > params or gc params or heap space or anything else that we need to tweak
> > for improving search response time.
> >
> > On Sun, 19 Jan, 2020, 3:15 AM Erick Erickson, 
> > wrote:
> >
> >> Add =timing to the query and it’ll show you the time each component
> >> takes.
> >>
> >> > On Jan 18, 2020, at 1:50 PM, Rajdeep Sahoo 
> >> wrote:
> >> >
> >> > Thanks for the suggestion,
> >> >
> >> > Is there any way to get the info which operation or which query params
> >> are
> >> > increasing the response time.
> >> >
> >> >
> >> > On Sat, 18 Jan, 2020, 11:59 PM Dave, 
> >> wrote:
> >> >
> >> >> If you’re not getting values, don’t ask for the facet. Facets are
> >> >> expensive as hell, maybe you should think more about your query’s than
> >> your
> >> >> infrastructure, solr cloud won’t help you at all especially if your
> >> asking
> >> >> for things you don’t need
> >> >>
> >> >>> On Jan 18, 2020, at 1:25 PM, Rajdeep Sahoo <
> >> rajdeepsahoo2...@gmail.com>
> >> >> wrote:
> >> >>>
> >> >>> We have assigned 16 gb out of 24gb for heap .
> >> >>> No other process is running on that node.
> >> >>>
> >> >>> 200 facets fields are there in the query but we will not be getting
> >> the
> >> >>> values for each facets for every search.
> >> >>> There can be max of 50-60 facets for which we will be getting values.
> >> >>>
> >> >>> We are using caching,is it not going to help.
> >> >>>
> >> >>>
> >> >>>
> >>  On Sat, 18 Jan, 2020, 11:36 PM Shawn Heisey, 
> >> >> wrote:
> >> 
> >> > On 1/18/2020 10:09 AM, Rajdeep Sahoo wrote:
> >> > We are having 2.3 million documents and size is 2.5 gb.
> >> >  10 core cpu and 24 gb ram . 16 slave nodes.
> >> >
> >> >  Still some of the queries are taking 50 sec at solr end.
> >> > As we are using solr 4.6 .
> >> >  Other thing is we are having 200 (avg) facet fields  in a query.
> >> > And 30 searchable fields.
> >> > Is there any way to identify why it is taking 50 sec for a query.
> >> >Multiple concurrent requests are there.
> >> 
> >>  Searching 30 fields and computing 200 facets is never going to be
> >> super
> >>  fast.  Switching to cloud will not help, and might make it slower.
> >> 
> >>  Your index is pretty small to a lot of us.  There are people running
> >>  indexes with billions of documents that take terabytes of disk space.
> >> 
> >>  As Walter mentioned, computing 200 facets is going to require a fair
> >>  amount of heap memory.  One *possible* problem here is that the Solr
> >>  heap size is too small, so a lot of GC is required.  How much of the
> >>  24GB have you assigned to the heap?  Is there any software other than
> >>  Solr running on these nodes?
> >> 
> >>  Thanks,
> >>  Shawn
> >> 
> >> >>
> >>
> >>

Re: Solr cloud production set up

[Rajdeep Sahoo]

Please suggest anyone

On Sun, 19 Jan, 2020, 9:43 AM Rajdeep Sahoo, 
wrote:

> Apart from reducing no of facets in the query, is there any other query
> params or gc params or heap space or anything else that we need to tweak
> for improving search response time.
>
> On Sun, 19 Jan, 2020, 3:15 AM Erick Erickson, 
> wrote:
>
>> Add =timing to the query and it’ll show you the time each component
>> takes.
>>
>> > On Jan 18, 2020, at 1:50 PM, Rajdeep Sahoo 
>> wrote:
>> >
>> > Thanks for the suggestion,
>> >
>> > Is there any way to get the info which operation or which query params
>> are
>> > increasing the response time.
>> >
>> >
>> > On Sat, 18 Jan, 2020, 11:59 PM Dave, 
>> wrote:
>> >
>> >> If you’re not getting values, don’t ask for the facet. Facets are
>> >> expensive as hell, maybe you should think more about your query’s than
>> your
>> >> infrastructure, solr cloud won’t help you at all especially if your
>> asking
>> >> for things you don’t need
>> >>
>> >>> On Jan 18, 2020, at 1:25 PM, Rajdeep Sahoo <
>> rajdeepsahoo2...@gmail.com>
>> >> wrote:
>> >>>
>> >>> We have assigned 16 gb out of 24gb for heap .
>> >>> No other process is running on that node.
>> >>>
>> >>> 200 facets fields are there in the query but we will not be getting
>> the
>> >>> values for each facets for every search.
>> >>> There can be max of 50-60 facets for which we will be getting values.
>> >>>
>> >>> We are using caching,is it not going to help.
>> >>>
>> >>>
>> >>>
>>  On Sat, 18 Jan, 2020, 11:36 PM Shawn Heisey, 
>> >> wrote:
>> 
>> > On 1/18/2020 10:09 AM, Rajdeep Sahoo wrote:
>> > We are having 2.3 million documents and size is 2.5 gb.
>> >  10 core cpu and 24 gb ram . 16 slave nodes.
>> >
>> >  Still some of the queries are taking 50 sec at solr end.
>> > As we are using solr 4.6 .
>> >  Other thing is we are having 200 (avg) facet fields  in a query.
>> > And 30 searchable fields.
>> > Is there any way to identify why it is taking 50 sec for a query.
>> >Multiple concurrent requests are there.
>> 
>>  Searching 30 fields and computing 200 facets is never going to be
>> super
>>  fast.  Switching to cloud will not help, and might make it slower.
>> 
>>  Your index is pretty small to a lot of us.  There are people running
>>  indexes with billions of documents that take terabytes of disk space.
>> 
>>  As Walter mentioned, computing 200 facets is going to require a fair
>>  amount of heap memory.  One *possible* problem here is that the Solr
>>  heap size is too small, so a lot of GC is required.  How much of the
>>  24GB have you assigned to the heap?  Is there any software other than
>>  Solr running on these nodes?
>> 
>>  Thanks,
>>  Shawn
>> 
>> >>
>>
>>

Re: Solr cloud production set up

[Rajdeep Sahoo]

Apart from reducing no of facets in the query, is there any other query
params or gc params or heap space or anything else that we need to tweak
for improving search response time.

On Sun, 19 Jan, 2020, 3:15 AM Erick Erickson, 
wrote:

> Add =timing to the query and it’ll show you the time each component
> takes.
>
> > On Jan 18, 2020, at 1:50 PM, Rajdeep Sahoo 
> wrote:
> >
> > Thanks for the suggestion,
> >
> > Is there any way to get the info which operation or which query params
> are
> > increasing the response time.
> >
> >
> > On Sat, 18 Jan, 2020, 11:59 PM Dave, 
> wrote:
> >
> >> If you’re not getting values, don’t ask for the facet. Facets are
> >> expensive as hell, maybe you should think more about your query’s than
> your
> >> infrastructure, solr cloud won’t help you at all especially if your
> asking
> >> for things you don’t need
> >>
> >>> On Jan 18, 2020, at 1:25 PM, Rajdeep Sahoo  >
> >> wrote:
> >>>
> >>> We have assigned 16 gb out of 24gb for heap .
> >>> No other process is running on that node.
> >>>
> >>> 200 facets fields are there in the query but we will not be getting the
> >>> values for each facets for every search.
> >>> There can be max of 50-60 facets for which we will be getting values.
> >>>
> >>> We are using caching,is it not going to help.
> >>>
> >>>
> >>>
>  On Sat, 18 Jan, 2020, 11:36 PM Shawn Heisey, 
> >> wrote:
> 
> > On 1/18/2020 10:09 AM, Rajdeep Sahoo wrote:
> > We are having 2.3 million documents and size is 2.5 gb.
> >  10 core cpu and 24 gb ram . 16 slave nodes.
> >
> >  Still some of the queries are taking 50 sec at solr end.
> > As we are using solr 4.6 .
> >  Other thing is we are having 200 (avg) facet fields  in a query.
> > And 30 searchable fields.
> > Is there any way to identify why it is taking 50 sec for a query.
> >Multiple concurrent requests are there.
> 
>  Searching 30 fields and computing 200 facets is never going to be
> super
>  fast.  Switching to cloud will not help, and might make it slower.
> 
>  Your index is pretty small to a lot of us.  There are people running
>  indexes with billions of documents that take terabytes of disk space.
> 
>  As Walter mentioned, computing 200 facets is going to require a fair
>  amount of heap memory.  One *possible* problem here is that the Solr
>  heap size is too small, so a lot of GC is required.  How much of the
>  24GB have you assigned to the heap?  Is there any software other than
>  Solr running on these nodes?
> 
>  Thanks,
>  Shawn
> 
> >>
>
>

Re: Solr cloud production set up

[Erick Erickson]

Add =timing to the query and it’ll show you the time each component takes.

> On Jan 18, 2020, at 1:50 PM, Rajdeep Sahoo  wrote:
> 
> Thanks for the suggestion,
> 
> Is there any way to get the info which operation or which query params are
> increasing the response time.
> 
> 
> On Sat, 18 Jan, 2020, 11:59 PM Dave,  wrote:
> 
>> If you’re not getting values, don’t ask for the facet. Facets are
>> expensive as hell, maybe you should think more about your query’s than your
>> infrastructure, solr cloud won’t help you at all especially if your asking
>> for things you don’t need
>> 
>>> On Jan 18, 2020, at 1:25 PM, Rajdeep Sahoo 
>> wrote:
>>> 
>>> We have assigned 16 gb out of 24gb for heap .
>>> No other process is running on that node.
>>> 
>>> 200 facets fields are there in the query but we will not be getting the
>>> values for each facets for every search.
>>> There can be max of 50-60 facets for which we will be getting values.
>>> 
>>> We are using caching,is it not going to help.
>>> 
>>> 
>>> 
 On Sat, 18 Jan, 2020, 11:36 PM Shawn Heisey, 
>> wrote:
 
> On 1/18/2020 10:09 AM, Rajdeep Sahoo wrote:
> We are having 2.3 million documents and size is 2.5 gb.
>  10 core cpu and 24 gb ram . 16 slave nodes.
> 
>  Still some of the queries are taking 50 sec at solr end.
> As we are using solr 4.6 .
>  Other thing is we are having 200 (avg) facet fields  in a query.
> And 30 searchable fields.
> Is there any way to identify why it is taking 50 sec for a query.
>Multiple concurrent requests are there.
 
 Searching 30 fields and computing 200 facets is never going to be super
 fast.  Switching to cloud will not help, and might make it slower.
 
 Your index is pretty small to a lot of us.  There are people running
 indexes with billions of documents that take terabytes of disk space.
 
 As Walter mentioned, computing 200 facets is going to require a fair
 amount of heap memory.  One *possible* problem here is that the Solr
 heap size is too small, so a lot of GC is required.  How much of the
 24GB have you assigned to the heap?  Is there any software other than
 Solr running on these nodes?
 
 Thanks,
 Shawn
 
>> 

Re: Solr cloud production set up

[Rajdeep Sahoo]

Thanks for the suggestion,

 Is there any way to get the info which operation or which query params are
increasing the response time.


On Sat, 18 Jan, 2020, 11:59 PM Dave,  wrote:

> If you’re not getting values, don’t ask for the facet. Facets are
> expensive as hell, maybe you should think more about your query’s than your
> infrastructure, solr cloud won’t help you at all especially if your asking
> for things you don’t need
>
> > On Jan 18, 2020, at 1:25 PM, Rajdeep Sahoo 
> wrote:
> >
> > We have assigned 16 gb out of 24gb for heap .
> > No other process is running on that node.
> >
> > 200 facets fields are there in the query but we will not be getting the
> > values for each facets for every search.
> > There can be max of 50-60 facets for which we will be getting values.
> >
> > We are using caching,is it not going to help.
> >
> >
> >
> >> On Sat, 18 Jan, 2020, 11:36 PM Shawn Heisey, 
> wrote:
> >>
> >>> On 1/18/2020 10:09 AM, Rajdeep Sahoo wrote:
> >>> We are having 2.3 million documents and size is 2.5 gb.
> >>>   10 core cpu and 24 gb ram . 16 slave nodes.
> >>>
> >>>   Still some of the queries are taking 50 sec at solr end.
> >>> As we are using solr 4.6 .
> >>>   Other thing is we are having 200 (avg) facet fields  in a query.
> >>>  And 30 searchable fields.
> >>>  Is there any way to identify why it is taking 50 sec for a query.
> >>> Multiple concurrent requests are there.
> >>
> >> Searching 30 fields and computing 200 facets is never going to be super
> >> fast.  Switching to cloud will not help, and might make it slower.
> >>
> >> Your index is pretty small to a lot of us.  There are people running
> >> indexes with billions of documents that take terabytes of disk space.
> >>
> >> As Walter mentioned, computing 200 facets is going to require a fair
> >> amount of heap memory.  One *possible* problem here is that the Solr
> >> heap size is too small, so a lot of GC is required.  How much of the
> >> 24GB have you assigned to the heap?  Is there any software other than
> >> Solr running on these nodes?
> >>
> >> Thanks,
> >> Shawn
> >>
>

Re: Solr cloud production set up

[Dave]

If you’re not getting values, don’t ask for the facet. Facets are expensive as 
hell, maybe you should think more about your query’s than your infrastructure, 
solr cloud won’t help you at all especially if your asking for things you don’t 
need

> On Jan 18, 2020, at 1:25 PM, Rajdeep Sahoo  wrote:
> 
> We have assigned 16 gb out of 24gb for heap .
> No other process is running on that node.
> 
> 200 facets fields are there in the query but we will not be getting the
> values for each facets for every search.
> There can be max of 50-60 facets for which we will be getting values.
> 
> We are using caching,is it not going to help.
> 
> 
> 
>> On Sat, 18 Jan, 2020, 11:36 PM Shawn Heisey,  wrote:
>> 
>>> On 1/18/2020 10:09 AM, Rajdeep Sahoo wrote:
>>> We are having 2.3 million documents and size is 2.5 gb.
>>>   10 core cpu and 24 gb ram . 16 slave nodes.
>>> 
>>>   Still some of the queries are taking 50 sec at solr end.
>>> As we are using solr 4.6 .
>>>   Other thing is we are having 200 (avg) facet fields  in a query.
>>>  And 30 searchable fields.
>>>  Is there any way to identify why it is taking 50 sec for a query.
>>> Multiple concurrent requests are there.
>> 
>> Searching 30 fields and computing 200 facets is never going to be super
>> fast.  Switching to cloud will not help, and might make it slower.
>> 
>> Your index is pretty small to a lot of us.  There are people running
>> indexes with billions of documents that take terabytes of disk space.
>> 
>> As Walter mentioned, computing 200 facets is going to require a fair
>> amount of heap memory.  One *possible* problem here is that the Solr
>> heap size is too small, so a lot of GC is required.  How much of the
>> 24GB have you assigned to the heap?  Is there any software other than
>> Solr running on these nodes?
>> 
>> Thanks,
>> Shawn
>> 

Re: Solr cloud production set up

[Rajdeep Sahoo]

We have assigned 16 gb out of 24gb for heap .
 No other process is running on that node.

200 facets fields are there in the query but we will not be getting the
values for each facets for every search.
There can be max of 50-60 facets for which we will be getting values.

 We are using caching,is it not going to help.



On Sat, 18 Jan, 2020, 11:36 PM Shawn Heisey,  wrote:

> On 1/18/2020 10:09 AM, Rajdeep Sahoo wrote:
> > We are having 2.3 million documents and size is 2.5 gb.
> >10 core cpu and 24 gb ram . 16 slave nodes.
> >
> >Still some of the queries are taking 50 sec at solr end.
> > As we are using solr 4.6 .
> >Other thing is we are having 200 (avg) facet fields  in a query.
> >   And 30 searchable fields.
> >   Is there any way to identify why it is taking 50 sec for a query.
> >  Multiple concurrent requests are there.
>
> Searching 30 fields and computing 200 facets is never going to be super
> fast.  Switching to cloud will not help, and might make it slower.
>
> Your index is pretty small to a lot of us.  There are people running
> indexes with billions of documents that take terabytes of disk space.
>
> As Walter mentioned, computing 200 facets is going to require a fair
> amount of heap memory.  One *possible* problem here is that the Solr
> heap size is too small, so a lot of GC is required.  How much of the
> 24GB have you assigned to the heap?  Is there any software other than
> Solr running on these nodes?
>
> Thanks,
> Shawn
>

Re: Solr cloud production set up

[Shawn Heisey]

On 1/18/2020 10:09 AM, Rajdeep Sahoo wrote:

We are having 2.3 million documents and size is 2.5 gb.
   10 core cpu and 24 gb ram . 16 slave nodes.

   Still some of the queries are taking 50 sec at solr end.
As we are using solr 4.6 .
   Other thing is we are having 200 (avg) facet fields  in a query.
  And 30 searchable fields.
  Is there any way to identify why it is taking 50 sec for a query.
 Multiple concurrent requests are there.


Searching 30 fields and computing 200 facets is never going to be super 
fast.  Switching to cloud will not help, and might make it slower.


Your index is pretty small to a lot of us.  There are people running 
indexes with billions of documents that take terabytes of disk space.


As Walter mentioned, computing 200 facets is going to require a fair 
amount of heap memory.  One *possible* problem here is that the Solr 
heap size is too small, so a lot of GC is required.  How much of the 
24GB have you assigned to the heap?  Is there any software other than 
Solr running on these nodes?


Thanks,
Shawn

Re: Solr cloud production set up

[Rajdeep Sahoo]

Although we are having a avg of 200 facet fields in the search request all
of them will not be having values in each request.
Max of 50-60 facet fields will be having some value.
  And we are using function query,is it having some performance impact.


On Sat, 18 Jan, 2020, 11:10 PM Walter Underwood, 
wrote:

> For indexing, is the master node CPU around 90%? If not, you aren’t
> sending requests fast enough or your disk is slow.
>
> For querying, 200 facet fields is HUGE. That will take a lot of Java heap
> memory and will be slow. Each facet fields requires large in-memory arrays
> and sorting.
>
> wunder
> Walter Underwood
> wun...@wunderwood.org
> http://observer.wunderwood.org/  (my blog)
>
> > On Jan 18, 2020, at 9:29 AM, Rajdeep Sahoo 
> wrote:
> >
> > Hi shawn,
> >  Thanks for this info,
> > Could you Please address my below query,
> >
> >
> > We are having 2.3 million documents and size is 2.5 gb.
> > With this data do we need solr cloud.
> >
> >  10 core cpu and 24 gb ram . 16 slave nodes.
> >
> >  Still some of the queries are taking 50 sec at solr end.
> > As we are using solr 4.6 .
> >  Other thing is we are having 200 (avg) facet fields  in a query.
> > And 30 searchable fields.
> > Is there any way to identify why it is taking 50 sec for a query.
> >Multiple concurrent requests are there.
> >
> > And how to optimize the search response time as it is almost 1 mins for
> > some request.
> >
> >
> > On Sat, 18 Jan, 2020, 10:52 PM Shawn Heisey, 
> wrote:
> >
> >> On 1/18/2020 9:55 AM, Rajdeep Sahoo wrote:
> >>> We do parallel indexing in production,
> >>>
> >>>  What about search performance in solr cloud in comparison with master
> >>> slave.
> >>>And what about  block join performance in solr cloud.
> >>>Do we need to increase the infra for solr cloud as we would be
> >>> maintaining multiple shard and replica.
> >>>   Is there any co relation with master slave set up.
> >>
> >> As I said before, SolrCloud is not a magic bullet that solves
> >> performance issues.  If the index characteristics are the same (number
> >> of docs, total size), performance in SolrCloud will be nearly identical
> >> to non-cloud.
> >>
> >> Thanks,
> >> Shawn
> >>
>
>

Re: Solr cloud production set up

[Walter Underwood]

For indexing, is the master node CPU around 90%? If not, you aren’t sending 
requests fast enough or your disk is slow.

For querying, 200 facet fields is HUGE. That will take a lot of Java heap 
memory and will be slow. Each facet fields requires large in-memory arrays and 
sorting.

wunder
Walter Underwood
wun...@wunderwood.org
http://observer.wunderwood.org/  (my blog)

> On Jan 18, 2020, at 9:29 AM, Rajdeep Sahoo  wrote:
> 
> Hi shawn,
>  Thanks for this info,
> Could you Please address my below query,
> 
> 
> We are having 2.3 million documents and size is 2.5 gb.
> With this data do we need solr cloud.
> 
>  10 core cpu and 24 gb ram . 16 slave nodes.
> 
>  Still some of the queries are taking 50 sec at solr end.
> As we are using solr 4.6 .
>  Other thing is we are having 200 (avg) facet fields  in a query.
> And 30 searchable fields.
> Is there any way to identify why it is taking 50 sec for a query.
>Multiple concurrent requests are there.
> 
> And how to optimize the search response time as it is almost 1 mins for
> some request.
> 
> 
> On Sat, 18 Jan, 2020, 10:52 PM Shawn Heisey,  wrote:
> 
>> On 1/18/2020 9:55 AM, Rajdeep Sahoo wrote:
>>> We do parallel indexing in production,
>>> 
>>>  What about search performance in solr cloud in comparison with master
>>> slave.
>>>And what about  block join performance in solr cloud.
>>>Do we need to increase the infra for solr cloud as we would be
>>> maintaining multiple shard and replica.
>>>   Is there any co relation with master slave set up.
>> 
>> As I said before, SolrCloud is not a magic bullet that solves
>> performance issues.  If the index characteristics are the same (number
>> of docs, total size), performance in SolrCloud will be nearly identical
>> to non-cloud.
>> 
>> Thanks,
>> Shawn
>> 

Re: Solr cloud production set up

[Rajdeep Sahoo]

Hi shawn,
  Thanks for this info,
Could you Please address my below query,


We are having 2.3 million documents and size is 2.5 gb.
 With this data do we need solr cloud.

  10 core cpu and 24 gb ram . 16 slave nodes.

  Still some of the queries are taking 50 sec at solr end.
As we are using solr 4.6 .
  Other thing is we are having 200 (avg) facet fields  in a query.
 And 30 searchable fields.
 Is there any way to identify why it is taking 50 sec for a query.
Multiple concurrent requests are there.

And how to optimize the search response time as it is almost 1 mins for
some request.


On Sat, 18 Jan, 2020, 10:52 PM Shawn Heisey,  wrote:

> On 1/18/2020 9:55 AM, Rajdeep Sahoo wrote:
> > We do parallel indexing in production,
> >
> >   What about search performance in solr cloud in comparison with master
> > slave.
> > And what about  block join performance in solr cloud.
> > Do we need to increase the infra for solr cloud as we would be
> > maintaining multiple shard and replica.
> >Is there any co relation with master slave set up.
>
> As I said before, SolrCloud is not a magic bullet that solves
> performance issues.  If the index characteristics are the same (number
> of docs, total size), performance in SolrCloud will be nearly identical
> to non-cloud.
>
> Thanks,
> Shawn
>

Re: Solr cloud production set up

[Shawn Heisey]

On 1/18/2020 9:55 AM, Rajdeep Sahoo wrote:

We do parallel indexing in production,

  What about search performance in solr cloud in comparison with master
slave.
And what about  block join performance in solr cloud.
Do we need to increase the infra for solr cloud as we would be
maintaining multiple shard and replica.
   Is there any co relation with master slave set up.


As I said before, SolrCloud is not a magic bullet that solves 
performance issues.  If the index characteristics are the same (number 
of docs, total size), performance in SolrCloud will be nearly identical 
to non-cloud.


Thanks,
Shawn

Re: Solr cloud production set up

[Rajdeep Sahoo]

We are having 2.3 million documents and size is 2.5 gb.
  10 core cpu and 24 gb ram . 16 slave nodes.

  Still some of the queries are taking 50 sec at solr end.
As we are using solr 4.6 .
  Other thing is we are having 200 (avg) facet fields  in a query.
 And 30 searchable fields.
 Is there any way to identify why it is taking 50 sec for a query.
Multiple concurrent requests are there.



On Sat, 18 Jan, 2020, 10:32 PM Dave,  wrote:

> Agreed with the above. what’s your idea of “huge”? I have 600 ish gb in
> one core plus another 250x2 in two more on the same standalone solr
> instance and it runs more than fine
>
> > On Jan 18, 2020, at 11:31 AM, Shawn Heisey  wrote:
> >
> > On 1/18/2020 1:05 AM, Rajdeep Sahoo wrote:
> >> Our Index size is huge and in master slave the full indexing time is
> almost
> >> 24 hrs.
> >>In future the no of documents will increase.
> >> So,please some one recommend about the no of nodes and configuration
> like
> >> ram and cpu core for solr cloud.
> >
> > Indexing is not going to be any faster in SolrCloud.  It would probably
> be a little bit slower.  The best way to speed up indexing, whether running
> SolrCloud or not, is to make your indexing processes run in parallel, so
> that multiple batches of documents are being indexed at the same time.
> >
> > SolrCloud is not a magic bullet that solves all problems.  It's just a
> different way of managing indexes that has more automation, and makes
> initial setup of a distributed index a lot easier.  It doesn't do the job
> any faster than running without SolrCloud.  The legacy master/slave mode is
> likely to be a little bit faster.
> >
> > You haven't provided any of the information required for us to guess
> about the system requirements.  And it will be a guess ... we could be
> completely wrong.
> >
> >
> https://lucidworks.com/post/sizing-hardware-in-the-abstract-why-we-dont-have-a-definitive-answer/
> >
> > Thanks,
> > Shawn
>

Re: Solr cloud production set up

[Dave]

Agreed with the above. what’s your idea of “huge”? I have 600 ish gb in one 
core plus another 250x2 in two more on the same standalone solr instance and it 
runs more than fine

> On Jan 18, 2020, at 11:31 AM, Shawn Heisey  wrote:
> 
> On 1/18/2020 1:05 AM, Rajdeep Sahoo wrote:
>> Our Index size is huge and in master slave the full indexing time is almost
>> 24 hrs.
>>In future the no of documents will increase.
>> So,please some one recommend about the no of nodes and configuration like
>> ram and cpu core for solr cloud.
> 
> Indexing is not going to be any faster in SolrCloud.  It would probably be a 
> little bit slower.  The best way to speed up indexing, whether running 
> SolrCloud or not, is to make your indexing processes run in parallel, so that 
> multiple batches of documents are being indexed at the same time.
> 
> SolrCloud is not a magic bullet that solves all problems.  It's just a 
> different way of managing indexes that has more automation, and makes initial 
> setup of a distributed index a lot easier.  It doesn't do the job any faster 
> than running without SolrCloud.  The legacy master/slave mode is likely to be 
> a little bit faster.
> 
> You haven't provided any of the information required for us to guess about 
> the system requirements.  And it will be a guess ... we could be completely 
> wrong.
> 
> https://lucidworks.com/post/sizing-hardware-in-the-abstract-why-we-dont-have-a-definitive-answer/
> 
> Thanks,
> Shawn

Re: Solr cloud production set up

[Rajdeep Sahoo]

Hi shawn,
 Thanks for your reply

We do parallel indexing in production,

 What about search performance in solr cloud in comparison with master
slave.
   And what about  block join performance in solr cloud.
   Do we need to increase the infra for solr cloud as we would be
maintaining multiple shard and replica.
  Is there any co relation with master slave set up.




On Sat, 18 Jan, 2020, 10:01 PM Shawn Heisey,  wrote:

> On 1/18/2020 1:05 AM, Rajdeep Sahoo wrote:
> > Our Index size is huge and in master slave the full indexing time is
> almost
> > 24 hrs.
> > In future the no of documents will increase.
> > So,please some one recommend about the no of nodes and configuration like
> > ram and cpu core for solr cloud.
>
> Indexing is not going to be any faster in SolrCloud.  It would probably
> be a little bit slower.  The best way to speed up indexing, whether
> running SolrCloud or not, is to make your indexing processes run in
> parallel, so that multiple batches of documents are being indexed at the
> same time.
>
> SolrCloud is not a magic bullet that solves all problems.  It's just a
> different way of managing indexes that has more automation, and makes
> initial setup of a distributed index a lot easier.  It doesn't do the
> job any faster than running without SolrCloud.  The legacy master/slave
> mode is likely to be a little bit faster.
>
> You haven't provided any of the information required for us to guess
> about the system requirements.  And it will be a guess ... we could be
> completely wrong.
>
>
> https://lucidworks.com/post/sizing-hardware-in-the-abstract-why-we-dont-have-a-definitive-answer/
>
> Thanks,
> Shawn
>

Re: Solr cloud production set up

[Shawn Heisey]

On 1/18/2020 1:05 AM, Rajdeep Sahoo wrote:

Our Index size is huge and in master slave the full indexing time is almost
24 hrs.
In future the no of documents will increase.
So,please some one recommend about the no of nodes and configuration like
ram and cpu core for solr cloud.


Indexing is not going to be any faster in SolrCloud.  It would probably 
be a little bit slower.  The best way to speed up indexing, whether 
running SolrCloud or not, is to make your indexing processes run in 
parallel, so that multiple batches of documents are being indexed at the 
same time.


SolrCloud is not a magic bullet that solves all problems.  It's just a 
different way of managing indexes that has more automation, and makes 
initial setup of a distributed index a lot easier.  It doesn't do the 
job any faster than running without SolrCloud.  The legacy master/slave 
mode is likely to be a little bit faster.


You haven't provided any of the information required for us to guess 
about the system requirements.  And it will be a guess ... we could be 
completely wrong.


https://lucidworks.com/post/sizing-hardware-in-the-abstract-why-we-dont-have-a-definitive-answer/

Thanks,
Shawn

Re: Solr cloud production set up

[Rajdeep Sahoo]

Got your point.
  If we think about the infra, then in cloud do we need more infra in
comparison to master slave.



On Sat, 18 Jan, 2020, 2:24 PM Jörn Franke,  wrote:

> I think you should do your own measurements. This is very document and
> processing specific.
> You can run a test with a simple setup for let’s say 1 mio document and
> interpolate from this. It could be also that your ETL is the bottleneck and
> not Solr.
> At the same time you can simulate user queries using Jmeter or similar.
>
> > Am 18.01.2020 um 09:05 schrieb Rajdeep Sahoo  >:
> >
> > Our Index size is huge and in master slave the full indexing time is
> almost
> > 24 hrs.
> >   In future the no of documents will increase.
> > So,please some one recommend about the no of nodes and configuration like
> > ram and cpu core for solr cloud.
> >
> >> On Sat, 18 Jan, 2020, 8:05 AM Walter Underwood, 
> >> wrote:
> >>
> >> Why do you want to change to Solr Cloud? Master/slave is a great, stable
> >> cluster architecture.
> >>
> >> wunder
> >> Walter Underwood
> >> wun...@wunderwood.org
> >> http://observer.wunderwood.org/  (my blog)
> >>
> >>> On Jan 17, 2020, at 6:19 PM, Rajdeep Sahoo  >
> >> wrote:
> >>>
> >>> Please reply anyone
> >>>
> >>> On Sat, 18 Jan, 2020, 12:13 AM Rajdeep Sahoo, <
> >> rajdeepsahoo2...@gmail.com>
> >>> wrote:
> >>>
>  Hi all,
>  We are using solr cloud 7.7.1
>  In a live production environment how many solr cloud server do we
> need,
>  Currently ,we are using master slave set up with 16 slave server with
>  solr 4.6.
>  In solr cloud do we need to scale it up or 16 server will suffice the
>  purpose.
> 
> 
> >>
> >>
>

Re: Solr cloud production set up

[Jörn Franke]

I think you should do your own measurements. This is very document and 
processing specific.
You can run a test with a simple setup for let’s say 1 mio document and 
interpolate from this. It could be also that your ETL is the bottleneck and not 
Solr.
At the same time you can simulate user queries using Jmeter or similar.

> Am 18.01.2020 um 09:05 schrieb Rajdeep Sahoo :
> 
> Our Index size is huge and in master slave the full indexing time is almost
> 24 hrs.
>   In future the no of documents will increase.
> So,please some one recommend about the no of nodes and configuration like
> ram and cpu core for solr cloud.
> 
>> On Sat, 18 Jan, 2020, 8:05 AM Walter Underwood, 
>> wrote:
>> 
>> Why do you want to change to Solr Cloud? Master/slave is a great, stable
>> cluster architecture.
>> 
>> wunder
>> Walter Underwood
>> wun...@wunderwood.org
>> http://observer.wunderwood.org/  (my blog)
>> 
>>> On Jan 17, 2020, at 6:19 PM, Rajdeep Sahoo 
>> wrote:
>>> 
>>> Please reply anyone
>>> 
>>> On Sat, 18 Jan, 2020, 12:13 AM Rajdeep Sahoo, <
>> rajdeepsahoo2...@gmail.com>
>>> wrote:
>>> 
 Hi all,
 We are using solr cloud 7.7.1
 In a live production environment how many solr cloud server do we need,
 Currently ,we are using master slave set up with 16 slave server with
 solr 4.6.
 In solr cloud do we need to scale it up or 16 server will suffice the
 purpose.
 
 
>> 
>> 

Re: Solr cloud production set up

[Walter Underwood]

How big? We index 35 million documents in about 6 hours.

wunder
Walter Underwood
wun...@wunderwood.org
http://observer.wunderwood.org/  (my blog)

> On Jan 18, 2020, at 12:05 AM, Rajdeep Sahoo  
> wrote:
> 
> Our Index size is huge and in master slave the full indexing time is almost
> 24 hrs.
>   In future the no of documents will increase.
> So,please some one recommend about the no of nodes and configuration like
> ram and cpu core for solr cloud.
> 
> On Sat, 18 Jan, 2020, 8:05 AM Walter Underwood, 
> wrote:
> 
>> Why do you want to change to Solr Cloud? Master/slave is a great, stable
>> cluster architecture.
>> 
>> wunder
>> Walter Underwood
>> wun...@wunderwood.org
>> http://observer.wunderwood.org/  (my blog)
>> 
>>> On Jan 17, 2020, at 6:19 PM, Rajdeep Sahoo 
>> wrote:
>>> 
>>> Please reply anyone
>>> 
>>> On Sat, 18 Jan, 2020, 12:13 AM Rajdeep Sahoo, <
>> rajdeepsahoo2...@gmail.com>
>>> wrote:
>>> 
 Hi all,
 We are using solr cloud 7.7.1
 In a live production environment how many solr cloud server do we need,
 Currently ,we are using master slave set up with 16 slave server with
 solr 4.6.
 In solr cloud do we need to scale it up or 16 server will suffice the
 purpose.
 
 
>> 
>> 

Re: Solr cloud production set up

[Rajdeep Sahoo]

Our Index size is huge and in master slave the full indexing time is almost
24 hrs.
   In future the no of documents will increase.
So,please some one recommend about the no of nodes and configuration like
ram and cpu core for solr cloud.

On Sat, 18 Jan, 2020, 8:05 AM Walter Underwood, 
wrote:

> Why do you want to change to Solr Cloud? Master/slave is a great, stable
> cluster architecture.
>
> wunder
> Walter Underwood
> wun...@wunderwood.org
> http://observer.wunderwood.org/  (my blog)
>
> > On Jan 17, 2020, at 6:19 PM, Rajdeep Sahoo 
> wrote:
> >
> > Please reply anyone
> >
> > On Sat, 18 Jan, 2020, 12:13 AM Rajdeep Sahoo, <
> rajdeepsahoo2...@gmail.com>
> > wrote:
> >
> >> Hi all,
> >> We are using solr cloud 7.7.1
> >> In a live production environment how many solr cloud server do we need,
> >> Currently ,we are using master slave set up with 16 slave server with
> >> solr 4.6.
> >> In solr cloud do we need to scale it up or 16 server will suffice the
> >> purpose.
> >>
> >>
>
>

Re: Solr cloud production set up

[Walter Underwood]

Why do you want to change to Solr Cloud? Master/slave is a great, stable 
cluster architecture.

wunder
Walter Underwood
wun...@wunderwood.org
http://observer.wunderwood.org/  (my blog)

> On Jan 17, 2020, at 6:19 PM, Rajdeep Sahoo  wrote:
> 
> Please reply anyone
> 
> On Sat, 18 Jan, 2020, 12:13 AM Rajdeep Sahoo, 
> wrote:
> 
>> Hi all,
>> We are using solr cloud 7.7.1
>> In a live production environment how many solr cloud server do we need,
>> Currently ,we are using master slave set up with 16 slave server with
>> solr 4.6.
>> In solr cloud do we need to scale it up or 16 server will suffice the
>> purpose.
>> 
>> 

Re: Solr cloud production set up

[Rajdeep Sahoo]

Please reply anyone

On Sat, 18 Jan, 2020, 12:13 AM Rajdeep Sahoo, 
wrote:

> Hi all,
>  We are using solr cloud 7.7.1
> In a live production environment how many solr cloud server do we need,
>  Currently ,we are using master slave set up with 16 slave server with
> solr 4.6.
> In solr cloud do we need to scale it up or 16 server will suffice the
> purpose.
>
>

Solr cloud production set up

[Rajdeep Sahoo]

Hi all,
 We are using solr cloud 7.7.1
In a live production environment how many solr cloud server do we need,
 Currently ,we are using master slave set up with 16 slave server with solr
4.6.
In solr cloud do we need to scale it up or 16 server will suffice the
purpose.

Best practice to deploy Solr to production

[marotosg]

Hi all,

I have a Solr index which has been evolving since Solr1.4 and now is in
SolrCloud6.6. 
This cluster is composed of 4 servers, few collections and shards. 
Since first time I deployed to production in 2009 I am using the same
approach to deploy. I think it's probably the time to review and improve. I
am looking for best practices and different approaches.

Here is what I have. Everyhting is done using ant.
1. I do have solr package together with my own code. I do have some plugins
written. 
2. 8 collections with several files per collection.
3. Ant steps 
3.1 Update config files with deployment properties per environment. 
3.2 Package and copy to servers
3.3 Run  remote sh commands for installation of Solr
3.4 Run remote sh to push config files to zookeeper
3.4 Run web requests to create collections.

I have the feeling this is not the proper way to go but not sure what's the
best practice either.

Can anyone point me to  a nicer way to do this?

Thanks a lot.
Sergio




--
Sent from: http://lucene.472066.n3.nabble.com/Solr-User-f472068.html

Re: Deploy Solr to production: best practices

[Shawn Heisey]

On 10/18/2017 11:32 PM, maximka19 wrote:
> *1.* Container: from Solr 5 there is now .WAR-file provided in package. I
> couldn't deploy Solr 7.1 to Tomcat 9. None of existing tutorials or guides
> helped. No such information for newer versions.

The included Jetty is the only supported option since version 5.0.

https://wiki.apache.org/solr/WhyNoWar

> So, does this mean that officially Solr isn't support other containers like
> Tomcat? Can we use Jetty as a main container in production issues? And it's
> officially recommended by developers/maintainers? If so, how can I host Solr
> as a service in Windows Server? There are not any scripts in package for
> Windows, only for .nix machines. How to do that? What a best practices? NO
> information, tutorials, guides are provided in such question, especially for
> Windows users.

Correct, running in a user-supplied container is not a supported
option.  It *is* still possible to install Solr into a third party
container like Tomcat, but you'll be on your own.  Since version 5.3,
the webapp is no longer compressed into a WAR file, instead it is
already exploded to server/solr-webapp/webapp.  As far as I am aware,
Tomcat does have the ability to run an already-exploded webapp.

Jetty is considered an enterprise-grade platform.  You might have heard
of this product, which is built with Jetty:

https://cloud.google.com/appengine/docs/flexible/

As for the OS, you're probably getting the impression that Windows is a
second class citizen to the average Solr developer.  That would indeed
be a correct impression.  As for my own opinion, although I do consider
Windows to be technically inferior to Linux and other open source
operating systems, it's a capable platform that can run Solr just fine.

My primary objection to running Solr on Windows has little to do with
the technology, it's mostly about cost.  You wouldn't want to run
production Solr on a client OS like Windows 10.  The server operating
systems usually add a significant cost to new hardware deployments.

I think that NSSM is the program most commonly used for turning the Solr
download into a Windows service.

https://nssm.cc/

There is an issue in Jira to create a Windows service out of the box,
but work on it has stalled.

https://issues.apache.org/jira/browse/SOLR-7105

Thanks,
Shawn

Re: Deploy Solr to production: best practices

[Walter Underwood]

I recommend the “Taking Solr to Production” chapter in the official Solr 
reference guide. That was my first hit for “solr production” in Google.

https://lucene.apache.org/solr/guide/6_6/taking-solr-to-production.html 
<https://lucene.apache.org/solr/guide/6_6/taking-solr-to-production.html>

I recommend using a recent version of Java 8 and the G1 garbage collector. We 
use that with parameters suggested on this list. This is from our solr.in.sh.

SOLR_HEAP=8g
# Use G1 GC  -- wunder 2017-01-23
# Settings from https://wiki.apache.org/solr/ShawnHeisey
GC_TUNE=" \
-XX:+UseG1GC \
-XX:+ParallelRefProcEnabled \
-XX:G1HeapRegionSize=8m \
-XX:MaxGCPauseMillis=200 \
-XX:+UseLargePages \
-XX:+AggressiveOpts \
"

wunder
Walter Underwood
wun...@wunderwood.org
http://observer.wunderwood.org/  (my blog)


> On Oct 18, 2017, at 10:32 PM, maximka19 <moldabeko...@gmail.com> wrote:
> 
> Hi everyone!
> 
> I started learning full-text search engines and chosen Solr. I'm introduced
> with Solr, but now I'v having troubles to move Solr to production. 
> 
> 
> 
> *1.* Container: from Solr 5 there is now .WAR-file provided in package. I
> couldn't deploy Solr 7.1 to Tomcat 9. None of existing tutorials or guides
> helped. No such information for newer versions.
> 
> So, does this mean that officially Solr isn't support other containers like
> Tomcat? Can we use Jetty as a main container in production issues? And it's
> officially recommended by developers/maintainers? If so, how can I host Solr
> as a service in Windows Server? There are not any scripts in package for
> Windows, only for .nix machines. How to do that? What a best practices? NO
> information, tutorials, guides are provided in such question, especially for
> Windows users.
> 
> *2.* Other things that should be known in deploying Solr to production:
> which? Anything else that Solr users should know?
> 
> 
> Sirs, guys, I've searched to whole Web, bought and read 4 books about Solr,
> but none of them helped me. Everything is based in older version <5 and much
> more for .nix-OS users than Windows users. No relevant information. Even the
> official documentation contains a small information and doesn't answer such
> questions.
> 
> Please, help me, give some advices, tutorials, opinions and show the right
> way.
> 
> Thank You
> 
> 
> 
> --
> Sent from: http://lucene.472066.n3.nabble.com/Solr-User-f472068.html

Re: Deploy Solr to Production: guides, best practices

[Erick Erickson]

https://wiki.apache.org/solr/WhyNoWar

Also, recent versions just don't build a war _for_ you. If you insist
you can build your own war file by bundling up "the right stuff".
However, there's no guarantee that you'll be able to do that going
forward. I have to confess that I can't guarantee you can make your
own war in 7.x, and I only _think_ you can in 6x. You can probably
tell I don't recommend it BTW.

A quick google search turns up a bunch of hits, I can't vouch for
any of them. If you'd care to add something to the Wiki above
that'd be great, or even a section in the reference guide.

Best,
Erick

On Thu, Oct 19, 2017 at 7:57 AM, GW  wrote:
> Not a Windows user but you should be able to just install it and surf port
> 8983. Once installed it should show in services
>
> https://www.norconex.com/how-to-run-solr5-as-a-service-on-windows/
>
> On 19 October 2017 at 07:18, maximka19  wrote:
>
>> Rick Leir-2 wrote
>> > Maximka
>> > The app server is bundled in Solr, so you do not install Tomcat or JEtty
>> > separately.
>> > Cheers -- Rick
>>
>> Hi! So, what should I do to host it in Windows Server as service? In
>> production.
>>
>> Thanks
>>
>>
>>
>> --
>> Sent from: http://lucene.472066.n3.nabble.com/Solr-User-f472068.html
>>

Re: Deploy Solr to Production: guides, best practices

[GW]

Not a Windows user but you should be able to just install it and surf port
8983. Once installed it should show in services

https://www.norconex.com/how-to-run-solr5-as-a-service-on-windows/

On 19 October 2017 at 07:18, maximka19  wrote:

> Rick Leir-2 wrote
> > Maximka
> > The app server is bundled in Solr, so you do not install Tomcat or JEtty
> > separately.
> > Cheers -- Rick
>
> Hi! So, what should I do to host it in Windows Server as service? In
> production.
>
> Thanks
>
>
>
> --
> Sent from: http://lucene.472066.n3.nabble.com/Solr-User-f472068.html
>

Re: Deploy Solr to Production: guides, best practices

[maximka19]

Rick Leir-2 wrote
> Maximka
> The app server is bundled in Solr, so you do not install Tomcat or JEtty
> separately. 
> Cheers -- Rick

Hi! So, what should I do to host it in Windows Server as service? In
production.

Thanks



--
Sent from: http://lucene.472066.n3.nabble.com/Solr-User-f472068.html

Re: Deploy Solr to Production: guides, best practices

[Rick Leir]

Maximka
The app server is bundled in Solr, so you do not install Tomcat or JEtty 
separately. 
Cheers -- Rick

On October 19, 2017 2:01:30 AM EDT, maximka19 <moldabeko...@gmail.com> wrote:
>Hi everyone!
>
>I was looking for full-text search engine and chosen Solr. Quickly
>introduced with Solr. Now I'm having troubles with taking Solr to
>Production
>under Windows Server.
>
>As You know, from Solr 5 there is no .WAR-file in package; I couldn't
>deploy
>Solr 7.1 to Tomcat 9. Didn't found any information, tutorials, guides
>relevantly to new versions of both Solr and Tomcat.
>
>So, the first question that comes: do I need to use default Jetty
>container
>in production? Or Tomcat is more preferable in production ways? If so,
>why?
>For what reasons? In older (and the only) books about Solr I've read
>the
>Tomcat is more efficient in production that default Jetty. Book were
>considering Solr 3 and Tomcat 6. Nowadays versions are much higher. If
>we
>can use Jetty in production, how to deploy Solr with Jetty as a service
>in
>Windows Server? There are no scripts provided for Windows users, only
>for
>.NIX-users.
>
>Troubling with this question for two weeks, really. There are NO
>relevant
>information in such questions, even in official documentation. And the
>other
>thing: do Solr users to know smth else about deployin Solr to
>production?
>Any bugs, recommendations, best practices? Or everything goes
>out-of-the-box? 
>
>
>I really need help, advices and guides in this question.
>Thank You
>
>
>
>
>--
>Sent from: http://lucene.472066.n3.nabble.com/Solr-User-f472068.html

-- 
Sorry for being brief. Alternate email is rickleir at yahoo dot com 

Deploy Solr to production: best practices

[maximka19]

Hi everyone!

I started learning full-text search engines and chosen Solr. I'm introduced
with Solr, but now I'v having troubles to move Solr to production. 



*1.* Container: from Solr 5 there is now .WAR-file provided in package. I
couldn't deploy Solr 7.1 to Tomcat 9. None of existing tutorials or guides
helped. No such information for newer versions.

So, does this mean that officially Solr isn't support other containers like
Tomcat? Can we use Jetty as a main container in production issues? And it's
officially recommended by developers/maintainers? If so, how can I host Solr
as a service in Windows Server? There are not any scripts in package for
Windows, only for .nix machines. How to do that? What a best practices? NO
information, tutorials, guides are provided in such question, especially for
Windows users.

*2.* Other things that should be known in deploying Solr to production:
which? Anything else that Solr users should know?


Sirs, guys, I've searched to whole Web, bought and read 4 books about Solr,
but none of them helped me. Everything is based in older version <5 and much
more for .nix-OS users than Windows users. No relevant information. Even the
official documentation contains a small information and doesn't answer such
questions.

Please, help me, give some advices, tutorials, opinions and show the right
way.

Thank You



--
Sent from: http://lucene.472066.n3.nabble.com/Solr-User-f472068.html

Deploy Solr to Production: guides, best practices

[maximka19]

Hi everyone!

I was looking for full-text search engine and chosen Solr. Quickly
introduced with Solr. Now I'm having troubles with taking Solr to Production
under Windows Server.

As You know, from Solr 5 there is no .WAR-file in package; I couldn't deploy
Solr 7.1 to Tomcat 9. Didn't found any information, tutorials, guides
relevantly to new versions of both Solr and Tomcat.

So, the first question that comes: do I need to use default Jetty container
in production? Or Tomcat is more preferable in production ways? If so, why?
For what reasons? In older (and the only) books about Solr I've read the
Tomcat is more efficient in production that default Jetty. Book were
considering Solr 3 and Tomcat 6. Nowadays versions are much higher. If we
can use Jetty in production, how to deploy Solr with Jetty as a service in
Windows Server? There are no scripts provided for Windows users, only for
.NIX-users.

Troubling with this question for two weeks, really. There are NO relevant
information in such questions, even in official documentation. And the other
thing: do Solr users to know smth else about deployin Solr to production?
Any bugs, recommendations, best practices? Or everything goes
out-of-the-box? 


I really need help, advices and guides in this question.
Thank You




--
Sent from: http://lucene.472066.n3.nabble.com/Solr-User-f472068.html

Re: Solr to Production

[Erik Hatcher]

Now back up and start troubleshooting with curl outside of java, netbesns, etc

> On Mar 27, 2016, at 07:24, Adel Mohamed Khalifa <a.moha...@saudisoft.com> 
> wrote:
> 
> Hello,
> 
> I checked the port and it is not blocked.
> When I click the search button there is nothing.
> 
> I try to debug my netbeans on Ubuntu and the same problem is existing it 
> cannot call the server and stop at this statement :-
> -- SolrServer server = new HttpSolrServer(ip:port/solr/core);
> 
> Regards,
> Adel Khalifa 
> 
> -Original Message-
> From: Reth RM [mailto:reth.ik...@gmail.com] 
> Sent: Sunday, March 27, 2016 12:53 PM
> To: solr-user@lucene.apache.org
> Subject: Re: Solr to Production
> 
> Is that website deployed on same machine where solr is running? If not, check 
> whether the port is being blocked due to firewall protection.  What is the 
> response message that you are receiving?
> 
> 
> 
>> On Sun, Mar 27, 2016 at 3:16 PM, Adel Mohamed Khalifa < 
>> a.moha...@saudisoft.com> wrote:
>> 
>> Hello All,
>> 
>> 
>> 
>> I installed solr server on my Ubuntu and  when I use it directly it  
>> runs good, but when I use it remotely using my website it doesnot run 
>> and I don't know what the reason, can you  help me please.
>> 
>> 
>> 
>> Regards,
>> Adel Khalifa
>> 
>> 
>> 
>> 
> 
> 

RE: Solr to Production

[Adel Mohamed Khalifa]

Hello,

I checked the port and it is not blocked.
When I click the search button there is nothing.

I try to debug my netbeans on Ubuntu and the same problem is existing it cannot 
call the server and stop at this statement :-
-- SolrServer server = new HttpSolrServer(ip:port/solr/core);

Regards,
Adel Khalifa 

-Original Message-
From: Reth RM [mailto:reth.ik...@gmail.com] 
Sent: Sunday, March 27, 2016 12:53 PM
To: solr-user@lucene.apache.org
Subject: Re: Solr to Production

Is that website deployed on same machine where solr is running? If not, check 
whether the port is being blocked due to firewall protection.  What is the 
response message that you are receiving?



On Sun, Mar 27, 2016 at 3:16 PM, Adel Mohamed Khalifa < 
a.moha...@saudisoft.com> wrote:

> Hello All,
>
>
>
> I installed solr server on my Ubuntu and  when I use it directly it  
> runs good, but when I use it remotely using my website it doesnot run 
> and I don't know what the reason, can you  help me please.
>
>
>
> Regards,
> Adel Khalifa
>
>
>
>

Re: Solr to Production

[Reth RM]

Is that website deployed on same machine where solr is running? If not,
check whether the port is being blocked due to firewall protection.  What
is the response message that you are receiving?



On Sun, Mar 27, 2016 at 3:16 PM, Adel Mohamed Khalifa <
a.moha...@saudisoft.com> wrote:

> Hello All,
>
>
>
> I installed solr server on my Ubuntu and  when I use it directly it  runs
> good, but when I use it remotely using my website it doesnot run and I
> don't
> know what the reason, can you  help me please.
>
>
>
> Regards,
> Adel Khalifa
>
>
>
>

Solr to Production

[Adel Mohamed Khalifa]

Hello All,

 

I installed solr server on my Ubuntu and  when I use it directly it  runs
good, but when I use it remotely using my website it doesnot run and I don't
know what the reason, can you  help me please.

 

Regards,
Adel Khalifa 

 

Re: Send solr to Production

[Shawn Heisey]

On 3/20/2016 5:39 AM, Adel Mohamed Khalifa wrote:
> How I need to do or config for sending solr to production.

This is an extremely vague question.  When you say "config", this could
mean the solr config, the core/collection config, the OS config, or
possibly even something else.  Provide a lot more detail, please.

https://wiki.apache.org/solr/UsingMailingLists

There *is* a section of the documentation all about taking Solr to
production:

https://cwiki.apache.org/confluence/display/solr/Taking+Solr+to+Production

If you have already read this and other parts of the documentation, then
please let us know what part you find confusing, or exactly what you
would like to know that is not covered.  The documentation definitely
needs more work, especially for less experienced users.

Thanks,
Shawn

Send solr to Production

[Adel Mohamed Khalifa]

Hello All,

 

How I need to do or config for sending solr to production.

 

Regards,
Adel Khalifa

 

Taking Solr to production

[Aswath Srinivasan (TMS)]

If below is the situation,


* 4 Virtual machines with 64 GB RAM - 64bit machines, 512 GB storage 
for each VM

* Totally about 2.5 million documents to  be indexed

* Documents average size is 512 KB - pdfs and htmls

* Expected QPS is 150

* Incremental indexing is once per day at around 50,000 documents per 
day (update & delete combined)

This being said I was thinking I would take the Solr to production with,


* 2 shards, 1 Leader & 3 Replicas

* 2 solr instance per VM

* 3 Zookeepers on the same machines as that of Solr (3 out of 4 VMs 
will have external zookeeper)

* Solr 5.3.1 version

Do you all think this set up will work? Will this server me 150 QPS?

I know that nobody can give a definite answer and the only way is to do a 
performance testing and tweak it from there but there is another proposal to 
have 4 shards, 1 Leader and 1 Replica which I'm not in favor off. So, posting 
it here, just trying to get some peer opinion!!

Thank you,
Aswath NS

Re: Taking Solr to production

[Walter Underwood]

I agree, sharding may hurt more than it helps. And estimate the text size after 
the documents are processed.

We all love Solr Cloud, but this could be a good application for traditional 
master/slave Solr. That means no Zookeeper nodes and it is really easy to add a 
new query slave, just clone the instance.

We run an index with homework questions which seems similar to yours.

* 7 million documents.
* 50 Gbyte index.
* Request rates of 5000 to 10,000 q/minute per server.
* No facets or highlighting (highlighting soon, we store term vectors).
* Amazon EC2 instances with 16 cores, 30 Gbytes RAM, index is in ephemeral SSD.
* Index updates once per day.
* Master/slave.
* Solr 4.10.4.

During peak traffic, the 95th percentile response time was about three seconds, 
but that is because the queries are entire homework questions, up to 1000 
words, pasted into the query box. Yes, we have very unusual queries. Median 
response time was much better, about 50 milliseconds.

wunder
Walter Underwood
wun...@wunderwood.org
http://observer.wunderwood.org/  (my blog)


> On Jan 22, 2016, at 2:45 PM, Toke Eskildsen <t...@statsbiblioteket.dk> wrote:
> 
> Aswath Srinivasan (TMS) <aswath.sriniva...@toyota.com> wrote:
>> * Totally about 2.5 million documents to  be indexed
>> * Documents average size is 512 KB - pdfs and htmls
> 
>> This being said I was thinking I would take the Solr to production with,
>> * 2 shards, 1 Leader & 3 Replicas
> 
>> Do you all think this set up will work? Will this server me 150 QPS?
> 
> It certainly helps that you are batch updating. What is missing in this 
> estimation is how large the documents are when indexed, as I guess the ½MB 
> average is for the raw files? If they are your everyday short PDFs with 
> images, meaning not a lot of text, handling 2M+ of them is easy. If they are 
> all full-length books, it is another matter.
> 
> Your document count is relatively low and if your index data end up being 
> not-too-big (let's say 100GB), then you ought to consider having just a 
> single shard with 4 replicas: There is a non-trivial overhead going from 1 
> shard to more than one, especially if you are doing faceting.
> 
> - Toke Eskildsen

Re: Taking Solr to production

[Jack Krupansky]

"1 Leader & 3 Replicas"

SolrCloud does not distinguish leaders from replicas - that's old
master-slave terminology. The leader is just one of the replicas.

So, are you really talking about 2 shards with 4 replicas each or 2 shards
with 2 replicas each?

Putting multiple replica instances on each machine isn't buying you
anything, just making it more complicated to manage.

Number of shards is determined by amount of data and whether query latency
can be achieved - use more shards if the query latency is too high.

2.5 million (2,500,000) documents is rather small, so unless your queries
are running really slow, it's not clear you even need sharding, but we
don't know your document and query complexity. Heavy faceting or complex
function queries?

Number of replicas is determined by query load - number of simultaneous
query requests, as well as HA availability requirements.




-- Jack Krupansky

On Fri, Jan 22, 2016 at 5:45 PM, Toke Eskildsen <t...@statsbiblioteket.dk>
wrote:

> Aswath Srinivasan (TMS) <aswath.sriniva...@toyota.com> wrote:
> > * Totally about 2.5 million documents to  be indexed
> > * Documents average size is 512 KB - pdfs and htmls
>
> > This being said I was thinking I would take the Solr to production with,
> > * 2 shards, 1 Leader & 3 Replicas
>
> > Do you all think this set up will work? Will this server me 150 QPS?
>
> It certainly helps that you are batch updating. What is missing in this
> estimation is how large the documents are when indexed, as I guess the ½MB
> average is for the raw files? If they are your everyday short PDFs with
> images, meaning not a lot of text, handling 2M+ of them is easy. If they
> are all full-length books, it is another matter.
>
> Your document count is relatively low and if your index data end up being
> not-too-big (let's say 100GB), then you ought to consider having just a
> single shard with 4 replicas: There is a non-trivial overhead going from 1
> shard to more than one, especially if you are doing faceting.
>
> - Toke Eskildsen
>

Re: Taking Solr to production

[Toke Eskildsen]

Aswath Srinivasan (TMS) <aswath.sriniva...@toyota.com> wrote:
> * Totally about 2.5 million documents to  be indexed
> * Documents average size is 512 KB - pdfs and htmls

> This being said I was thinking I would take the Solr to production with,
> * 2 shards, 1 Leader & 3 Replicas

> Do you all think this set up will work? Will this server me 150 QPS?

It certainly helps that you are batch updating. What is missing in this 
estimation is how large the documents are when indexed, as I guess the ½MB 
average is for the raw files? If they are your everyday short PDFs with images, 
meaning not a lot of text, handling 2M+ of them is easy. If they are all 
full-length books, it is another matter.

Your document count is relatively low and if your index data end up being 
not-too-big (let's say 100GB), then you ought to consider having just a single 
shard with 4 replicas: There is a non-trivial overhead going from 1 shard to 
more than one, especially if you are doing faceting.

- Toke Eskildsen

RE: Taking Solr to production

[Aswath Srinivasan (TMS)]

Thanks guys for all the responses.

True. What I wanted to convey is  2 shards with 4 replicas.

>> use more shards if the query latency is too high.

Shouldn't we go for more replicas if query latency is too high? You can go for 
more shard if you have number of indexing documents and at a much frequent 
rate. Do you disagree with my point of view?

There are no facets but complex queries exist. A safe bet is to have 2 shards 
is what I was thinking so I give enough breathing space for the indexing jobs 
and 4 replicas to address the high QPS request. Am I thinking correctly?

I cannot thank you enough you guys!!

Thank you,
Aswath NS


-Original Message-
From: Jack Krupansky [mailto:jack.krupan...@gmail.com]
Sent: Friday, January 22, 2016 3:06 PM
To: solr-user@lucene.apache.org
Subject: Re: Taking Solr to production

"1 Leader & 3 Replicas"

SolrCloud does not distinguish leaders from replicas - that's old master-slave 
terminology. The leader is just one of the replicas.

So, are you really talking about 2 shards with 4 replicas each or 2 shards with 
2 replicas each?

Putting multiple replica instances on each machine isn't buying you anything, 
just making it more complicated to manage.

Number of shards is determined by amount of data and whether query latency can 
be achieved - use more shards if the query latency is too high.

2.5 million (2,500,000) documents is rather small, so unless your queries are 
running really slow, it's not clear you even need sharding, but we don't know 
your document and query complexity. Heavy faceting or complex function queries?

Number of replicas is determined by query load - number of simultaneous query 
requests, as well as HA availability requirements.




-- Jack Krupansky

On Fri, Jan 22, 2016 at 5:45 PM, Toke Eskildsen
wrote:

> Aswath Srinivasan (TMS) wrote:
> > * Totally about 2.5 million documents to be indexed
> > * Documents average size is 512 KB - pdfs and htmls
>
> > This being said I was thinking I would take the Solr to production with,
> > * 2 shards, 1 Leader & 3 Replicas
>
> > Do you all think this set up will work? Will this server me 150 QPS?
>
> It certainly helps that you are batch updating. What is missing in
> this estimation is how large the documents are when indexed, as I
> guess the ½MB average is for the raw files? If they are your everyday
> short PDFs with images, meaning not a lot of text, handling 2M+ of
> them is easy. If they are all full-length books, it is another matter.
>
> Your document count is relatively low and if your index data end up
> being not-too-big (let's say 100GB), then you ought to consider having
> just a single shard with 4 replicas: There is a non-trivial overhead
> going from 1 shard to more than one, especially if you are doing faceting.
>
> - Toke Eskildsen
>

Re: Taking Solr to production

[Erick Erickson]

It boils down to whether the response rate when you query a single
shard is "acceptable", plus some overhead for sharding.

So, if you need 100QPS and all you can get after tuning on a single
shard (which you can test with =false)
is 10QPS, you need 10 replicas.

But if a single shard can only get you responses back in 10 seconds,
you need more shards.

And so on

Best,
Erick



On Fri, Jan 22, 2016 at 3:30 PM, Aswath Srinivasan (TMS)
<aswath.sriniva...@toyota.com> wrote:
> Thanks guys for all the responses.
>
> True. What I wanted to convey is  2 shards with 4 replicas.
>
>>> use more shards if the query latency is too high.
>
> Shouldn't we go for more replicas if query latency is too high? You can go 
> for more shard if you have number of indexing documents and at a much 
> frequent rate. Do you disagree with my point of view?
>
> There are no facets but complex queries exist. A safe bet is to have 2 shards 
> is what I was thinking so I give enough breathing space for the indexing jobs 
> and 4 replicas to address the high QPS request. Am I thinking correctly?
>
> I cannot thank you enough you guys!!
>
> Thank you,
> Aswath NS
>
>
> -Original Message-
> From: Jack Krupansky [mailto:jack.krupan...@gmail.com]
> Sent: Friday, January 22, 2016 3:06 PM
> To: solr-user@lucene.apache.org
> Subject: Re: Taking Solr to production
>
> "1 Leader & 3 Replicas"
>
> SolrCloud does not distinguish leaders from replicas - that's old 
> master-slave terminology. The leader is just one of the replicas.
>
> So, are you really talking about 2 shards with 4 replicas each or 2 shards 
> with 2 replicas each?
>
> Putting multiple replica instances on each machine isn't buying you anything, 
> just making it more complicated to manage.
>
> Number of shards is determined by amount of data and whether query latency 
> can be achieved - use more shards if the query latency is too high.
>
> 2.5 million (2,500,000) documents is rather small, so unless your queries are 
> running really slow, it's not clear you even need sharding, but we don't know 
> your document and query complexity. Heavy faceting or complex function 
> queries?
>
> Number of replicas is determined by query load - number of simultaneous query 
> requests, as well as HA availability requirements.
>
>
>
>
> -- Jack Krupansky
>
> On Fri, Jan 22, 2016 at 5:45 PM, Toke Eskildsen
> wrote:
>
>> Aswath Srinivasan (TMS) wrote:
>> > * Totally about 2.5 million documents to be indexed
>> > * Documents average size is 512 KB - pdfs and htmls
>>
>> > This being said I was thinking I would take the Solr to production with,
>> > * 2 shards, 1 Leader & 3 Replicas
>>
>> > Do you all think this set up will work? Will this server me 150 QPS?
>>
>> It certainly helps that you are batch updating. What is missing in
>> this estimation is how large the documents are when indexed, as I
>> guess the ½MB average is for the raw files? If they are your everyday
>> short PDFs with images, meaning not a lot of text, handling 2M+ of
>> them is easy. If they are all full-length books, it is another matter.
>>
>> Your document count is relatively low and if your index data end up
>> being not-too-big (let's say 100GB), then you ought to consider having
>> just a single shard with 4 replicas: There is a non-trivial overhead
>> going from 1 shard to more than one, especially if you are doing faceting.
>>
>> - Toke Eskildsen
>>

Re: Indexing Solr in production

[Zheng Lin Edwin Yeo]

Thank you Alessandro and Erick.

Will try out the SolrJ methond.

Regards,
Edwin


On 14 October 2015 at 00:00, Erick Erickson <erickerick...@gmail.com> wrote:

> Here's a sample:
> https://lucidworks.com/blog/2012/02/14/indexing-with-solrj/
>
> On Tue, Oct 13, 2015 at 4:18 AM, Alessandro Benedetti
> <benedetti.ale...@gmail.com> wrote:
> > The most robust and simple way to go is building your own Indexer.
> > You can decide the platform you want, Solr has plenty of client API
> > libraries.
> >
> > For example if you want to write your Indexer app in Java, you can use
> > SolrJ..
> > Each client library will give you all the flexibility you need to index
> > solr in a robust way.
> >
> > [1] https://cwiki.apache.org/confluence/display/solr/Client+APIs
> > Cheers
> >
> > On 13 October 2015 at 09:35, Zheng Lin Edwin Yeo <edwinye...@gmail.com>
> > wrote:
> >
> >> Hi,
> >>
> >> What is the best practice to do indexing in Solr for production
> system.I'm
> >> using Solr 5.3.0.
> >>
> >> I understand that post.jar does not have things like robustness checks
> and
> >> retires, which is important in production, as sometimes certain records
> >> might failed during the indexing, and we need to re-try the indexing for
> >> those records that fails.
> >>
> >> Normally, do we need to write a new custom handler in order to achieve
> all
> >> these?
> >> Want to find out what most people did before I decide on a method and
> >> proceed on to the next step.
> >>
> >> Thank you.
> >>
> >> Regards,
> >> Edwin
> >>
> >
> >
> >
> > --
> > --
> >
> > Benedetti Alessandro
> > Visiting card - http://about.me/alessandro_benedetti
> > Blog - http://alexbenedetti.blogspot.co.uk
> >
> > "Tyger, tyger burning bright
> > In the forests of the night,
> > What immortal hand or eye
> > Could frame thy fearful symmetry?"
> >
> > William Blake - Songs of Experience -1794 England
>

Indexing Solr in production

[Zheng Lin Edwin Yeo]

Hi,

What is the best practice to do indexing in Solr for production system.I'm
using Solr 5.3.0.

I understand that post.jar does not have things like robustness checks and
retires, which is important in production, as sometimes certain records
might failed during the indexing, and we need to re-try the indexing for
those records that fails.

Normally, do we need to write a new custom handler in order to achieve all
these?
Want to find out what most people did before I decide on a method and
proceed on to the next step.

Thank you.

Regards,
Edwin

Re: Indexing Solr in production

[Alessandro Benedetti]

The most robust and simple way to go is building your own Indexer.
You can decide the platform you want, Solr has plenty of client API
libraries.

For example if you want to write your Indexer app in Java, you can use
SolrJ..
Each client library will give you all the flexibility you need to index
solr in a robust way.

[1] https://cwiki.apache.org/confluence/display/solr/Client+APIs
Cheers

On 13 October 2015 at 09:35, Zheng Lin Edwin Yeo <edwinye...@gmail.com>
wrote:

> Hi,
>
> What is the best practice to do indexing in Solr for production system.I'm
> using Solr 5.3.0.
>
> I understand that post.jar does not have things like robustness checks and
> retires, which is important in production, as sometimes certain records
> might failed during the indexing, and we need to re-try the indexing for
> those records that fails.
>
> Normally, do we need to write a new custom handler in order to achieve all
> these?
> Want to find out what most people did before I decide on a method and
> proceed on to the next step.
>
> Thank you.
>
> Regards,
> Edwin
>



-- 
--

Benedetti Alessandro
Visiting card - http://about.me/alessandro_benedetti
Blog - http://alexbenedetti.blogspot.co.uk

"Tyger, tyger burning bright
In the forests of the night,
What immortal hand or eye
Could frame thy fearful symmetry?"

William Blake - Songs of Experience -1794 England

Re: Indexing Solr in production

[Erick Erickson]

Here's a sample:
https://lucidworks.com/blog/2012/02/14/indexing-with-solrj/

On Tue, Oct 13, 2015 at 4:18 AM, Alessandro Benedetti
<benedetti.ale...@gmail.com> wrote:
> The most robust and simple way to go is building your own Indexer.
> You can decide the platform you want, Solr has plenty of client API
> libraries.
>
> For example if you want to write your Indexer app in Java, you can use
> SolrJ..
> Each client library will give you all the flexibility you need to index
> solr in a robust way.
>
> [1] https://cwiki.apache.org/confluence/display/solr/Client+APIs
> Cheers
>
> On 13 October 2015 at 09:35, Zheng Lin Edwin Yeo <edwinye...@gmail.com>
> wrote:
>
>> Hi,
>>
>> What is the best practice to do indexing in Solr for production system.I'm
>> using Solr 5.3.0.
>>
>> I understand that post.jar does not have things like robustness checks and
>> retires, which is important in production, as sometimes certain records
>> might failed during the indexing, and we need to re-try the indexing for
>> those records that fails.
>>
>> Normally, do we need to write a new custom handler in order to achieve all
>> these?
>> Want to find out what most people did before I decide on a method and
>> proceed on to the next step.
>>
>> Thank you.
>>
>> Regards,
>> Edwin
>>
>
>
>
> --
> --
>
> Benedetti Alessandro
> Visiting card - http://about.me/alessandro_benedetti
> Blog - http://alexbenedetti.blogspot.co.uk
>
> "Tyger, tyger burning bright
> In the forests of the night,
> What immortal hand or eye
> Could frame thy fearful symmetry?"
>
> William Blake - Songs of Experience -1794 England

Re: Taking Solr to production with docker

[Ugo Matrangolo]

Hi,

still don't get it :)

With Solr 5 it auto-installs itself as a supervised service and works
really nice in an AWS CloudFormation template.

Best
Ugo


On Wed, Sep 23, 2015 at 10:01 PM, Joe Lawson <
jlaw...@opensourceconnections.com> wrote:

> we get to run commands like, docker run solr and have solr working!
>
> containers make new application deployments a breeze.
>
> On Wed, Sep 23, 2015 at 4:35 PM, Ugo Matrangolo <ugo.matrang...@gmail.com>
> wrote:
>
> > Hi,
> >
> > just curious: what you get by running Solr into a Docker container ?
> >
> > Best
> > Ugo
> >
> > On Wed, Sep 23, 2015 at 5:39 PM, Vincenzo D'Amore <v.dam...@gmail.com>
> > wrote:
> >
> > > Hi Doug,
> > >
> > > I have ported solrcloud to docker too, I hope you can found something
> > > interesting here:
> > >
> > > https://github.com/freedev/solrcloud-zookeeper-docker
> > >
> > > This project runs an zookeeper ensemble and a sorlcloud cluster within
> > many
> > > containers.
> > >
> > > Now, in my spare time, I'm trying to port this project to kubernetes, I
> > > would like to split all these containers to many nodes.
> > >
> > > Cheers,
> > > Vincenzo
> > >
> > >
> > > On Wed, Sep 23, 2015 at 6:15 PM, Christopher Bradford <
> > > cbradf...@opensourceconnections.com> wrote:
> > >
> > > > Hi Doug,
> > > >
> > > > The Dockerfiles we use have been pushed up to a GitHub repo
> > > > https://github.com/o19s/solr-docker. I'm happy to answer any
> questions
> > > > about them.
> > > >
> > > > ~Chris
> > > >
> > > > On Wed, Sep 23, 2015 at 8:47 AM Doug Turnbull <
> > > > dturnb...@opensourceconnections.com> wrote:
> > > >
> > > > > Our test Solr and Elasticsearch instances for Quepid(
> > http://quepid.com
> > > )
> > > > are
> > > > > now hosted on docker (specifically kubernetes)
> > > > >
> > > > > It's worked pretty well. I'd suggest if you're curious to speak to
> my
> > > > > devops focussed colleague Chris Bradford that has a great deal of
> > > > > experience here. I haven't encountered any issues that would lead
> me
> > to
> > > > > describe it as "not ready for production"
> > > > >
> > > > > Doug
> > > > >
> > > > >
> > > > > On Wednesday, September 23, 2015, Upayavira <u...@odoko.co.uk>
> wrote:
> > > > >
> > > > >>
> > > > >>
> > > > >> On Wed, Sep 23, 2015, at 02:00 PM,
> aurelien.mazo...@francelabs.com
> > > > >> wrote:
> > > > >> > Hi Solr community,
> > > > >> >
> > > > >> > I can find many blog posts on how to deploy Solr with docker
> but I
> > > am
> > > > >> > wondering if Solr/Docker is really ready for production.
> > > > >> > Has anybody ever ran Solr in production with Docker?
> > > > >>
> > > > >> Hi Aurelien,
> > > > >>
> > > > >> I'm wondering if there's anything specific that is needed to run
> > Solr
> > > > >> inside Docker? Is there something you have in mind?
> > > > >>
> > > > >> Upayavira
> > > > >>
> > > > >
> > > > >
> > > > > --
> > > > > *Doug Turnbull **| *Search Relevance Consultant | OpenSource
> > > Connections
> > > > > <http://opensourceconnections.com>, LLC | 240.476.9983
> > > > > Author: Relevant Search <http://manning.com/turnbull>
> > > > > This e-mail and all contents, including attachments, is considered
> to
> > > be
> > > > > Company Confidential unless explicitly stated otherwise, regardless
> > > > > of whether attachments are marked as such.
> > > > >
> > > > >
> > > >
> > >
> > >
> > >
> > > --
> > > Vincenzo D'Amore
> > > email: v.dam...@gmail.com
> > > skype: free.dev
> > > mobile: +39 349 8513251
> > >
> >
>

Re: Taking Solr to production with docker

[Joe Lawson]

I think this sums up "what is docker":
https://youtu.be/F44GtxHO2MI
On Sep 24, 2015 4:37 AM, "Ugo Matrangolo" <ugo.matrang...@gmail.com> wrote:

> Hi,
>
> still don't get it :)
>
> With Solr 5 it auto-installs itself as a supervised service and works
> really nice in an AWS CloudFormation template.
>
> Best
> Ugo
>
>
> On Wed, Sep 23, 2015 at 10:01 PM, Joe Lawson <
> jlaw...@opensourceconnections.com> wrote:
>
> > we get to run commands like, docker run solr and have solr working!
> >
> > containers make new application deployments a breeze.
> >
> > On Wed, Sep 23, 2015 at 4:35 PM, Ugo Matrangolo <
> ugo.matrang...@gmail.com>
> > wrote:
> >
> > > Hi,
> > >
> > > just curious: what you get by running Solr into a Docker container ?
> > >
> > > Best
> > > Ugo
> > >
> > > On Wed, Sep 23, 2015 at 5:39 PM, Vincenzo D'Amore <v.dam...@gmail.com>
> > > wrote:
> > >
> > > > Hi Doug,
> > > >
> > > > I have ported solrcloud to docker too, I hope you can found something
> > > > interesting here:
> > > >
> > > > https://github.com/freedev/solrcloud-zookeeper-docker
> > > >
> > > > This project runs an zookeeper ensemble and a sorlcloud cluster
> within
> > > many
> > > > containers.
> > > >
> > > > Now, in my spare time, I'm trying to port this project to
> kubernetes, I
> > > > would like to split all these containers to many nodes.
> > > >
> > > > Cheers,
> > > > Vincenzo
> > > >
> > > >
> > > > On Wed, Sep 23, 2015 at 6:15 PM, Christopher Bradford <
> > > > cbradf...@opensourceconnections.com> wrote:
> > > >
> > > > > Hi Doug,
> > > > >
> > > > > The Dockerfiles we use have been pushed up to a GitHub repo
> > > > > https://github.com/o19s/solr-docker. I'm happy to answer any
> > questions
> > > > > about them.
> > > > >
> > > > > ~Chris
> > > > >
> > > > > On Wed, Sep 23, 2015 at 8:47 AM Doug Turnbull <
> > > > > dturnb...@opensourceconnections.com> wrote:
> > > > >
> > > > > > Our test Solr and Elasticsearch instances for Quepid(
> > > http://quepid.com
> > > > )
> > > > > are
> > > > > > now hosted on docker (specifically kubernetes)
> > > > > >
> > > > > > It's worked pretty well. I'd suggest if you're curious to speak
> to
> > my
> > > > > > devops focussed colleague Chris Bradford that has a great deal of
> > > > > > experience here. I haven't encountered any issues that would lead
> > me
> > > to
> > > > > > describe it as "not ready for production"
> > > > > >
> > > > > > Doug
> > > > > >
> > > > > >
> > > > > > On Wednesday, September 23, 2015, Upayavira <u...@odoko.co.uk>
> > wrote:
> > > > > >
> > > > > >>
> > > > > >>
> > > > > >> On Wed, Sep 23, 2015, at 02:00 PM,
> > aurelien.mazo...@francelabs.com
> > > > > >> wrote:
> > > > > >> > Hi Solr community,
> > > > > >> >
> > > > > >> > I can find many blog posts on how to deploy Solr with docker
> > but I
> > > > am
> > > > > >> > wondering if Solr/Docker is really ready for production.
> > > > > >> > Has anybody ever ran Solr in production with Docker?
> > > > > >>
> > > > > >> Hi Aurelien,
> > > > > >>
> > > > > >> I'm wondering if there's anything specific that is needed to run
> > > Solr
> > > > > >> inside Docker? Is there something you have in mind?
> > > > > >>
> > > > > >> Upayavira
> > > > > >>
> > > > > >
> > > > > >
> > > > > > --
> > > > > > *Doug Turnbull **| *Search Relevance Consultant | OpenSource
> > > > Connections
> > > > > > <http://opensourceconnections.com>, LLC | 240.476.9983
> > > > > > Author: Relevant Search <http://manning.com/turnbull>
> > > > > > This e-mail and all contents, including attachments, is
> considered
> > to
> > > > be
> > > > > > Company Confidential unless explicitly stated otherwise,
> regardless
> > > > > > of whether attachments are marked as such.
> > > > > >
> > > > > >
> > > > >
> > > >
> > > >
> > > >
> > > > --
> > > > Vincenzo D'Amore
> > > > email: v.dam...@gmail.com
> > > > skype: free.dev
> > > > mobile: +39 349 8513251
> > > >
> > >
> >
>

Re: Taking Solr to production with docker

[Epo Jemba]

Ugo

Don't get me wrong I know Solr is already scaling by itself ,
But in some cases, Solr in order to be fully usable has to be
 integrated/extended with a bunch of other apps : Your own,
load-balancers, frontends , etc
In order ALL of those work together the right way, you come up
with a higher solution, that will organize stuff altogether,
 in my case kubernetes  (it could have been others rancher.io, tectonic,
panama, etc )




2015-09-24 10:37 GMT+02:00 Ugo Matrangolo <ugo.matrang...@gmail.com>:

> Hi,
>
> still don't get it :)
>
> With Solr 5 it auto-installs itself as a supervised service and works
> really nice in an AWS CloudFormation template.
>
> Best
> Ugo
>
>
> On Wed, Sep 23, 2015 at 10:01 PM, Joe Lawson <
> jlaw...@opensourceconnections.com> wrote:
>
> > we get to run commands like, docker run solr and have solr working!
> >
> > containers make new application deployments a breeze.
> >
> > On Wed, Sep 23, 2015 at 4:35 PM, Ugo Matrangolo <
> ugo.matrang...@gmail.com>
> > wrote:
> >
> > > Hi,
> > >
> > > just curious: what you get by running Solr into a Docker container ?
> > >
> > > Best
> > > Ugo
> > >
> > > On Wed, Sep 23, 2015 at 5:39 PM, Vincenzo D'Amore <v.dam...@gmail.com>
> > > wrote:
> > >
> > > > Hi Doug,
> > > >
> > > > I have ported solrcloud to docker too, I hope you can found something
> > > > interesting here:
> > > >
> > > > https://github.com/freedev/solrcloud-zookeeper-docker
> > > >
> > > > This project runs an zookeeper ensemble and a sorlcloud cluster
> within
> > > many
> > > > containers.
> > > >
> > > > Now, in my spare time, I'm trying to port this project to
> kubernetes, I
> > > > would like to split all these containers to many nodes.
> > > >
> > > > Cheers,
> > > > Vincenzo
> > > >
> > > >
> > > > On Wed, Sep 23, 2015 at 6:15 PM, Christopher Bradford <
> > > > cbradf...@opensourceconnections.com> wrote:
> > > >
> > > > > Hi Doug,
> > > > >
> > > > > The Dockerfiles we use have been pushed up to a GitHub repo
> > > > > https://github.com/o19s/solr-docker. I'm happy to answer any
> > questions
> > > > > about them.
> > > > >
> > > > > ~Chris
> > > > >
> > > > > On Wed, Sep 23, 2015 at 8:47 AM Doug Turnbull <
> > > > > dturnb...@opensourceconnections.com> wrote:
> > > > >
> > > > > > Our test Solr and Elasticsearch instances for Quepid(
> > > http://quepid.com
> > > > )
> > > > > are
> > > > > > now hosted on docker (specifically kubernetes)
> > > > > >
> > > > > > It's worked pretty well. I'd suggest if you're curious to speak
> to
> > my
> > > > > > devops focussed colleague Chris Bradford that has a great deal of
> > > > > > experience here. I haven't encountered any issues that would lead
> > me
> > > to
> > > > > > describe it as "not ready for production"
> > > > > >
> > > > > > Doug
> > > > > >
> > > > > >
> > > > > > On Wednesday, September 23, 2015, Upayavira <u...@odoko.co.uk>
> > wrote:
> > > > > >
> > > > > >>
> > > > > >>
> > > > > >> On Wed, Sep 23, 2015, at 02:00 PM,
> > aurelien.mazo...@francelabs.com
> > > > > >> wrote:
> > > > > >> > Hi Solr community,
> > > > > >> >
> > > > > >> > I can find many blog posts on how to deploy Solr with docker
> > but I
> > > > am
> > > > > >> > wondering if Solr/Docker is really ready for production.
> > > > > >> > Has anybody ever ran Solr in production with Docker?
> > > > > >>
> > > > > >> Hi Aurelien,
> > > > > >>
> > > > > >> I'm wondering if there's anything specific that is needed to run
> > > Solr
> > > > > >> inside Docker? Is there something you have in mind?
> > > > > >>
> > > > > >> Upayavira
> > > > > >>
> > > > > >
> > > > > >
> > > > > > --
> > > > > > *Doug Turnbull **| *Search Relevance Consultant | OpenSource
> > > > Connections
> > > > > > <http://opensourceconnections.com>, LLC | 240.476.9983
> > > > > > Author: Relevant Search <http://manning.com/turnbull>
> > > > > > This e-mail and all contents, including attachments, is
> considered
> > to
> > > > be
> > > > > > Company Confidential unless explicitly stated otherwise,
> regardless
> > > > > > of whether attachments are marked as such.
> > > > > >
> > > > > >
> > > > >
> > > >
> > > >
> > > >
> > > > --
> > > > Vincenzo D'Amore
> > > > email: v.dam...@gmail.com
> > > > skype: free.dev
> > > > mobile: +39 349 8513251
> > > >
> > >
> >
>

Re: Taking Solr to production with docker

[Martijn Koster]

> On 23 Sep 2015, at 15:13, Upayavira  wrote:
> 
> I'm wondering if there's anything specific that is needed to run Solr
> inside Docker? Is there something you have in mind?

There isn't really. See https://hub.docker.com/r/makuk66/docker-solr/ 
 for an example.

I'm working on turning that into an official Docker Hub image 
(https://github.com/docker-solr/docker-solr 
), so that you will be able to just 
"docker run solr" and have Solr up and running. That is currently under review 
by Docker Inc on https://github.com/docker-library/official-images/pull/107 
. If you add a +1 
there it might speed the process up.

-- Martijn

Taking Solr to production with docker

[aurelien . mazoyer]

Hi Solr community,

I can find many blog posts on how to deploy Solr with docker but I am 
wondering if Solr/Docker is really ready for production.

Has anybody ever ran Solr in production with Docker?

Thank you for your feedback,

Aurélien

Re: Taking Solr to production with docker

[Upayavira]

On Wed, Sep 23, 2015, at 02:00 PM, aurelien.mazo...@francelabs.com
wrote:
> Hi Solr community,
> 
> I can find many blog posts on how to deploy Solr with docker but I am 
> wondering if Solr/Docker is really ready for production.
> Has anybody ever ran Solr in production with Docker?

Hi Aurelien,

I'm wondering if there's anything specific that is needed to run Solr
inside Docker? Is there something you have in mind?

Upayavira

Re: Taking Solr to production with docker

[Doug Turnbull]

Our test Solr and Elasticsearch instances for Quepid(http://quepid.com) are
now hosted on docker (specifically kubernetes)

It's worked pretty well. I'd suggest if you're curious to speak to my
devops focussed colleague Chris Bradford that has a great deal of
experience here. I haven't encountered any issues that would lead me to
describe it as "not ready for production"

Doug


On Wednesday, September 23, 2015, Upayavira <u...@odoko.co.uk> wrote:

>
>
> On Wed, Sep 23, 2015, at 02:00 PM, aurelien.mazo...@francelabs.com
> <javascript:;>
> wrote:
> > Hi Solr community,
> >
> > I can find many blog posts on how to deploy Solr with docker but I am
> > wondering if Solr/Docker is really ready for production.
> > Has anybody ever ran Solr in production with Docker?
>
> Hi Aurelien,
>
> I'm wondering if there's anything specific that is needed to run Solr
> inside Docker? Is there something you have in mind?
>
> Upayavira
>


-- 
*Doug Turnbull **| *Search Relevance Consultant | OpenSource Connections
<http://opensourceconnections.com>, LLC | 240.476.9983
Author: Relevant Search <http://manning.com/turnbull>
This e-mail and all contents, including attachments, is considered to be
Company Confidential unless explicitly stated otherwise, regardless
of whether attachments are marked as such.

Re: Taking Solr to production with docker

[Doug Turnbull]

Nice! starred. We'll keep that in mind should we go to docker beyond one
instance.

Cheers
-Doug

On Wed, Sep 23, 2015 at 12:39 PM, Vincenzo D'Amore <v.dam...@gmail.com>
wrote:

> Hi Doug,
>
> I have ported solrcloud to docker too, I hope you can found something
> interesting here:
>
> https://github.com/freedev/solrcloud-zookeeper-docker
>
> This project runs an zookeeper ensemble and a sorlcloud cluster within
> many containers.
>
> Now, in my spare time, I'm trying to port this project to kubernetes, I
> would like to split all these containers to many nodes.
>
> Cheers,
> Vincenzo
>
>
> On Wed, Sep 23, 2015 at 6:15 PM, Christopher Bradford <
> cbradf...@opensourceconnections.com> wrote:
>
>> Hi Doug,
>>
>> The Dockerfiles we use have been pushed up to a GitHub repo
>> https://github.com/o19s/solr-docker. I'm happy to answer any questions
>> about them.
>>
>> ~Chris
>>
>> On Wed, Sep 23, 2015 at 8:47 AM Doug Turnbull <
>> dturnb...@opensourceconnections.com> wrote:
>>
>> > Our test Solr and Elasticsearch instances for Quepid(http://quepid.com)
>> are
>> > now hosted on docker (specifically kubernetes)
>> >
>> > It's worked pretty well. I'd suggest if you're curious to speak to my
>> > devops focussed colleague Chris Bradford that has a great deal of
>> > experience here. I haven't encountered any issues that would lead me to
>> > describe it as "not ready for production"
>> >
>> > Doug
>> >
>> >
>> > On Wednesday, September 23, 2015, Upayavira <u...@odoko.co.uk> wrote:
>> >
>> >>
>> >>
>> >> On Wed, Sep 23, 2015, at 02:00 PM, aurelien.mazo...@francelabs.com
>> >> wrote:
>> >> > Hi Solr community,
>> >> >
>> >> > I can find many blog posts on how to deploy Solr with docker but I am
>> >> > wondering if Solr/Docker is really ready for production.
>> >> > Has anybody ever ran Solr in production with Docker?
>> >>
>> >> Hi Aurelien,
>> >>
>> >> I'm wondering if there's anything specific that is needed to run Solr
>> >> inside Docker? Is there something you have in mind?
>> >>
>> >> Upayavira
>> >>
>> >
>> >
>> > --
>> > *Doug Turnbull **| *Search Relevance Consultant | OpenSource Connections
>> > <http://opensourceconnections.com>, LLC | 240.476.9983
>> > Author: Relevant Search <http://manning.com/turnbull>
>> > This e-mail and all contents, including attachments, is considered to be
>> > Company Confidential unless explicitly stated otherwise, regardless
>> > of whether attachments are marked as such.
>> >
>> >
>>
>
>
>
> --
> Vincenzo D'Amore
> email: v.dam...@gmail.com
> skype: free.dev
> mobile: +39 349 8513251
>



-- 
*Doug Turnbull **| *Search Relevance Consultant | OpenSource Connections
<http://opensourceconnections.com>, LLC | 240.476.9983
Author: Relevant Search <http://manning.com/turnbull>
This e-mail and all contents, including attachments, is considered to be
Company Confidential unless explicitly stated otherwise, regardless
of whether attachments are marked as such.

Re: Taking Solr to production with docker

[Christopher Bradford]

Hi Doug,

The Dockerfiles we use have been pushed up to a GitHub repo
https://github.com/o19s/solr-docker. I'm happy to answer any questions
about them.

~Chris

On Wed, Sep 23, 2015 at 8:47 AM Doug Turnbull <
dturnb...@opensourceconnections.com> wrote:

> Our test Solr and Elasticsearch instances for Quepid(http://quepid.com) are
> now hosted on docker (specifically kubernetes)
>
> It's worked pretty well. I'd suggest if you're curious to speak to my
> devops focussed colleague Chris Bradford that has a great deal of
> experience here. I haven't encountered any issues that would lead me to
> describe it as "not ready for production"
>
> Doug
>
>
> On Wednesday, September 23, 2015, Upayavira <u...@odoko.co.uk> wrote:
>
>>
>>
>> On Wed, Sep 23, 2015, at 02:00 PM, aurelien.mazo...@francelabs.com
>> wrote:
>> > Hi Solr community,
>> >
>> > I can find many blog posts on how to deploy Solr with docker but I am
>> > wondering if Solr/Docker is really ready for production.
>> > Has anybody ever ran Solr in production with Docker?
>>
>> Hi Aurelien,
>>
>> I'm wondering if there's anything specific that is needed to run Solr
>> inside Docker? Is there something you have in mind?
>>
>> Upayavira
>>
>
>
> --
> *Doug Turnbull **| *Search Relevance Consultant | OpenSource Connections
> <http://opensourceconnections.com>, LLC | 240.476.9983
> Author: Relevant Search <http://manning.com/turnbull>
> This e-mail and all contents, including attachments, is considered to be
> Company Confidential unless explicitly stated otherwise, regardless
> of whether attachments are marked as such.
>
>

Re: Taking Solr to production with docker

[Vincenzo D'Amore]

Hi Doug,

I have ported solrcloud to docker too, I hope you can found something
interesting here:

https://github.com/freedev/solrcloud-zookeeper-docker

This project runs an zookeeper ensemble and a sorlcloud cluster within many
containers.

Now, in my spare time, I'm trying to port this project to kubernetes, I
would like to split all these containers to many nodes.

Cheers,
Vincenzo


On Wed, Sep 23, 2015 at 6:15 PM, Christopher Bradford <
cbradf...@opensourceconnections.com> wrote:

> Hi Doug,
>
> The Dockerfiles we use have been pushed up to a GitHub repo
> https://github.com/o19s/solr-docker. I'm happy to answer any questions
> about them.
>
> ~Chris
>
> On Wed, Sep 23, 2015 at 8:47 AM Doug Turnbull <
> dturnb...@opensourceconnections.com> wrote:
>
> > Our test Solr and Elasticsearch instances for Quepid(http://quepid.com)
> are
> > now hosted on docker (specifically kubernetes)
> >
> > It's worked pretty well. I'd suggest if you're curious to speak to my
> > devops focussed colleague Chris Bradford that has a great deal of
> > experience here. I haven't encountered any issues that would lead me to
> > describe it as "not ready for production"
> >
> > Doug
> >
> >
> > On Wednesday, September 23, 2015, Upayavira <u...@odoko.co.uk> wrote:
> >
> >>
> >>
> >> On Wed, Sep 23, 2015, at 02:00 PM, aurelien.mazo...@francelabs.com
> >> wrote:
> >> > Hi Solr community,
> >> >
> >> > I can find many blog posts on how to deploy Solr with docker but I am
> >> > wondering if Solr/Docker is really ready for production.
> >> > Has anybody ever ran Solr in production with Docker?
> >>
> >> Hi Aurelien,
> >>
> >> I'm wondering if there's anything specific that is needed to run Solr
> >> inside Docker? Is there something you have in mind?
> >>
> >> Upayavira
> >>
> >
> >
> > --
> > *Doug Turnbull **| *Search Relevance Consultant | OpenSource Connections
> > <http://opensourceconnections.com>, LLC | 240.476.9983
> > Author: Relevant Search <http://manning.com/turnbull>
> > This e-mail and all contents, including attachments, is considered to be
> > Company Confidential unless explicitly stated otherwise, regardless
> > of whether attachments are marked as such.
> >
> >
>



-- 
Vincenzo D'Amore
email: v.dam...@gmail.com
skype: free.dev
mobile: +39 349 8513251

Re: Taking Solr to production with docker

[Epo Jemba]

Hi Doug,

thank you for your git repo. I am planning a kubernetes + solr integration
as well,
can you tell us how do you organize your pods and services (or else)
regarding zookeeper
management. How do you organize your pods/services/etc along with solr
instances, ZK nodes etc ..

Thanks in advance

Epo J.

2015-09-23 18:15 GMT+02:00 Christopher Bradford <
cbradf...@opensourceconnections.com>:

> Hi Doug,
>
> The Dockerfiles we use have been pushed up to a GitHub repo
> https://github.com/o19s/solr-docker. I'm happy to answer any questions
> about them.
>
> ~Chris
>
> On Wed, Sep 23, 2015 at 8:47 AM Doug Turnbull <
> dturnb...@opensourceconnections.com> wrote:
>
> > Our test Solr and Elasticsearch instances for Quepid(http://quepid.com)
> are
> > now hosted on docker (specifically kubernetes)
> >
> > It's worked pretty well. I'd suggest if you're curious to speak to my
> > devops focussed colleague Chris Bradford that has a great deal of
> > experience here. I haven't encountered any issues that would lead me to
> > describe it as "not ready for production"
> >
> > Doug
> >
> >
> > On Wednesday, September 23, 2015, Upayavira <u...@odoko.co.uk> wrote:
> >
> >>
> >>
> >> On Wed, Sep 23, 2015, at 02:00 PM, aurelien.mazo...@francelabs.com
> >> wrote:
> >> > Hi Solr community,
> >> >
> >> > I can find many blog posts on how to deploy Solr with docker but I am
> >> > wondering if Solr/Docker is really ready for production.
> >> > Has anybody ever ran Solr in production with Docker?
> >>
> >> Hi Aurelien,
> >>
> >> I'm wondering if there's anything specific that is needed to run Solr
> >> inside Docker? Is there something you have in mind?
> >>
> >> Upayavira
> >>
> >
> >
> > --
> > *Doug Turnbull **| *Search Relevance Consultant | OpenSource Connections
> > <http://opensourceconnections.com>, LLC | 240.476.9983
> > Author: Relevant Search <http://manning.com/turnbull>
> > This e-mail and all contents, including attachments, is considered to be
> > Company Confidential unless explicitly stated otherwise, regardless
> > of whether attachments are marked as such.
> >
> >
>

Re: Taking Solr to production with docker

[Epo Jemba]

Hi Ugo,

I do not yet use Solr in docker, but for my case docker is not enough here,
used in conjunction with kubernetes what I'am reaching is elasticity,
I mean, adding removing nodes and leave scaling and fault tolerancy to
kubernetes oob.
All you have to do is well defined your blueprint, templates.

Putting Solr in docker, just for the sake of putting Solr in docker was not
a goal.

2015-09-23 22:35 GMT+02:00 Ugo Matrangolo <ugo.matrang...@gmail.com>:

> Hi,
>
> just curious: what you get by running Solr into a Docker container ?
>
> Best
> Ugo
>
> On Wed, Sep 23, 2015 at 5:39 PM, Vincenzo D'Amore <v.dam...@gmail.com>
> wrote:
>
> > Hi Doug,
> >
> > I have ported solrcloud to docker too, I hope you can found something
> > interesting here:
> >
> > https://github.com/freedev/solrcloud-zookeeper-docker
> >
> > This project runs an zookeeper ensemble and a sorlcloud cluster within
> many
> > containers.
> >
> > Now, in my spare time, I'm trying to port this project to kubernetes, I
> > would like to split all these containers to many nodes.
> >
> > Cheers,
> > Vincenzo
> >
> >
> > On Wed, Sep 23, 2015 at 6:15 PM, Christopher Bradford <
> > cbradf...@opensourceconnections.com> wrote:
> >
> > > Hi Doug,
> > >
> > > The Dockerfiles we use have been pushed up to a GitHub repo
> > > https://github.com/o19s/solr-docker. I'm happy to answer any questions
> > > about them.
> > >
> > > ~Chris
> > >
> > > On Wed, Sep 23, 2015 at 8:47 AM Doug Turnbull <
> > > dturnb...@opensourceconnections.com> wrote:
> > >
> > > > Our test Solr and Elasticsearch instances for Quepid(
> http://quepid.com
> > )
> > > are
> > > > now hosted on docker (specifically kubernetes)
> > > >
> > > > It's worked pretty well. I'd suggest if you're curious to speak to my
> > > > devops focussed colleague Chris Bradford that has a great deal of
> > > > experience here. I haven't encountered any issues that would lead me
> to
> > > > describe it as "not ready for production"
> > > >
> > > > Doug
> > > >
> > > >
> > > > On Wednesday, September 23, 2015, Upayavira <u...@odoko.co.uk> wrote:
> > > >
> > > >>
> > > >>
> > > >> On Wed, Sep 23, 2015, at 02:00 PM, aurelien.mazo...@francelabs.com
> > > >> wrote:
> > > >> > Hi Solr community,
> > > >> >
> > > >> > I can find many blog posts on how to deploy Solr with docker but I
> > am
> > > >> > wondering if Solr/Docker is really ready for production.
> > > >> > Has anybody ever ran Solr in production with Docker?
> > > >>
> > > >> Hi Aurelien,
> > > >>
> > > >> I'm wondering if there's anything specific that is needed to run
> Solr
> > > >> inside Docker? Is there something you have in mind?
> > > >>
> > > >> Upayavira
> > > >>
> > > >
> > > >
> > > > --
> > > > *Doug Turnbull **| *Search Relevance Consultant | OpenSource
> > Connections
> > > > <http://opensourceconnections.com>, LLC | 240.476.9983
> > > > Author: Relevant Search <http://manning.com/turnbull>
> > > > This e-mail and all contents, including attachments, is considered to
> > be
> > > > Company Confidential unless explicitly stated otherwise, regardless
> > > > of whether attachments are marked as such.
> > > >
> > > >
> > >
> >
> >
> >
> > --
> > Vincenzo D'Amore
> > email: v.dam...@gmail.com
> > skype: free.dev
> > mobile: +39 349 8513251
> >
>

Re: Taking Solr to production with docker

[Joe Lawson]

Hi Epo,

We aren't using Zookeeper or the SolrCloud stuff on docker yet but it looks
like Vincenzo was using three ZK containers, each with a different port.

Sincerely,

Joe Lawson

On Wed, Sep 23, 2015 at 1:28 PM, Epo Jemba <taha...@gmail.com> wrote:

> Hi Doug,
>
> thank you for your git repo. I am planning a kubernetes + solr integration
> as well,
> can you tell us how do you organize your pods and services (or else)
> regarding zookeeper
> management. How do you organize your pods/services/etc along with solr
> instances, ZK nodes etc ..
>
> Thanks in advance
>
> Epo J.
>
> 2015-09-23 18:15 GMT+02:00 Christopher Bradford <
> cbradf...@opensourceconnections.com>:
>
> > Hi Doug,
> >
> > The Dockerfiles we use have been pushed up to a GitHub repo
> > https://github.com/o19s/solr-docker. I'm happy to answer any questions
> > about them.
> >
> > ~Chris
> >
> > On Wed, Sep 23, 2015 at 8:47 AM Doug Turnbull <
> > dturnb...@opensourceconnections.com> wrote:
> >
> > > Our test Solr and Elasticsearch instances for Quepid(http://quepid.com
> )
> > are
> > > now hosted on docker (specifically kubernetes)
> > >
> > > It's worked pretty well. I'd suggest if you're curious to speak to my
> > > devops focussed colleague Chris Bradford that has a great deal of
> > > experience here. I haven't encountered any issues that would lead me to
> > > describe it as "not ready for production"
> > >
> > > Doug
> > >
> > >
> > > On Wednesday, September 23, 2015, Upayavira <u...@odoko.co.uk> wrote:
> > >
> > >>
> > >>
> > >> On Wed, Sep 23, 2015, at 02:00 PM, aurelien.mazo...@francelabs.com
> > >> wrote:
> > >> > Hi Solr community,
> > >> >
> > >> > I can find many blog posts on how to deploy Solr with docker but I
> am
> > >> > wondering if Solr/Docker is really ready for production.
> > >> > Has anybody ever ran Solr in production with Docker?
> > >>
> > >> Hi Aurelien,
> > >>
> > >> I'm wondering if there's anything specific that is needed to run Solr
> > >> inside Docker? Is there something you have in mind?
> > >>
> > >> Upayavira
> > >>
> > >
> > >
> > > --
> > > *Doug Turnbull **| *Search Relevance Consultant | OpenSource
> Connections
> > > <http://opensourceconnections.com>, LLC | 240.476.9983
> > > Author: Relevant Search <http://manning.com/turnbull>
> > > This e-mail and all contents, including attachments, is considered to
> be
> > > Company Confidential unless explicitly stated otherwise, regardless
> > > of whether attachments are marked as such.
> > >
> > >
> >
>

Re: Taking Solr to production with docker

[Ugo Matrangolo]

Hi,

just curious: what you get by running Solr into a Docker container ?

Best
Ugo

On Wed, Sep 23, 2015 at 5:39 PM, Vincenzo D'Amore <v.dam...@gmail.com>
wrote:

> Hi Doug,
>
> I have ported solrcloud to docker too, I hope you can found something
> interesting here:
>
> https://github.com/freedev/solrcloud-zookeeper-docker
>
> This project runs an zookeeper ensemble and a sorlcloud cluster within many
> containers.
>
> Now, in my spare time, I'm trying to port this project to kubernetes, I
> would like to split all these containers to many nodes.
>
> Cheers,
> Vincenzo
>
>
> On Wed, Sep 23, 2015 at 6:15 PM, Christopher Bradford <
> cbradf...@opensourceconnections.com> wrote:
>
> > Hi Doug,
> >
> > The Dockerfiles we use have been pushed up to a GitHub repo
> > https://github.com/o19s/solr-docker. I'm happy to answer any questions
> > about them.
> >
> > ~Chris
> >
> > On Wed, Sep 23, 2015 at 8:47 AM Doug Turnbull <
> > dturnb...@opensourceconnections.com> wrote:
> >
> > > Our test Solr and Elasticsearch instances for Quepid(http://quepid.com
> )
> > are
> > > now hosted on docker (specifically kubernetes)
> > >
> > > It's worked pretty well. I'd suggest if you're curious to speak to my
> > > devops focussed colleague Chris Bradford that has a great deal of
> > > experience here. I haven't encountered any issues that would lead me to
> > > describe it as "not ready for production"
> > >
> > > Doug
> > >
> > >
> > > On Wednesday, September 23, 2015, Upayavira <u...@odoko.co.uk> wrote:
> > >
> > >>
> > >>
> > >> On Wed, Sep 23, 2015, at 02:00 PM, aurelien.mazo...@francelabs.com
> > >> wrote:
> > >> > Hi Solr community,
> > >> >
> > >> > I can find many blog posts on how to deploy Solr with docker but I
> am
> > >> > wondering if Solr/Docker is really ready for production.
> > >> > Has anybody ever ran Solr in production with Docker?
> > >>
> > >> Hi Aurelien,
> > >>
> > >> I'm wondering if there's anything specific that is needed to run Solr
> > >> inside Docker? Is there something you have in mind?
> > >>
> > >> Upayavira
> > >>
> > >
> > >
> > > --
> > > *Doug Turnbull **| *Search Relevance Consultant | OpenSource
> Connections
> > > <http://opensourceconnections.com>, LLC | 240.476.9983
> > > Author: Relevant Search <http://manning.com/turnbull>
> > > This e-mail and all contents, including attachments, is considered to
> be
> > > Company Confidential unless explicitly stated otherwise, regardless
> > > of whether attachments are marked as such.
> > >
> > >
> >
>
>
>
> --
> Vincenzo D'Amore
> email: v.dam...@gmail.com
> skype: free.dev
> mobile: +39 349 8513251
>

Re: Taking Solr to production with docker

[Joe Lawson]

we get to run commands like, docker run solr and have solr working!

containers make new application deployments a breeze.

On Wed, Sep 23, 2015 at 4:35 PM, Ugo Matrangolo <ugo.matrang...@gmail.com>
wrote:

> Hi,
>
> just curious: what you get by running Solr into a Docker container ?
>
> Best
> Ugo
>
> On Wed, Sep 23, 2015 at 5:39 PM, Vincenzo D'Amore <v.dam...@gmail.com>
> wrote:
>
> > Hi Doug,
> >
> > I have ported solrcloud to docker too, I hope you can found something
> > interesting here:
> >
> > https://github.com/freedev/solrcloud-zookeeper-docker
> >
> > This project runs an zookeeper ensemble and a sorlcloud cluster within
> many
> > containers.
> >
> > Now, in my spare time, I'm trying to port this project to kubernetes, I
> > would like to split all these containers to many nodes.
> >
> > Cheers,
> > Vincenzo
> >
> >
> > On Wed, Sep 23, 2015 at 6:15 PM, Christopher Bradford <
> > cbradf...@opensourceconnections.com> wrote:
> >
> > > Hi Doug,
> > >
> > > The Dockerfiles we use have been pushed up to a GitHub repo
> > > https://github.com/o19s/solr-docker. I'm happy to answer any questions
> > > about them.
> > >
> > > ~Chris
> > >
> > > On Wed, Sep 23, 2015 at 8:47 AM Doug Turnbull <
> > > dturnb...@opensourceconnections.com> wrote:
> > >
> > > > Our test Solr and Elasticsearch instances for Quepid(
> http://quepid.com
> > )
> > > are
> > > > now hosted on docker (specifically kubernetes)
> > > >
> > > > It's worked pretty well. I'd suggest if you're curious to speak to my
> > > > devops focussed colleague Chris Bradford that has a great deal of
> > > > experience here. I haven't encountered any issues that would lead me
> to
> > > > describe it as "not ready for production"
> > > >
> > > > Doug
> > > >
> > > >
> > > > On Wednesday, September 23, 2015, Upayavira <u...@odoko.co.uk> wrote:
> > > >
> > > >>
> > > >>
> > > >> On Wed, Sep 23, 2015, at 02:00 PM, aurelien.mazo...@francelabs.com
> > > >> wrote:
> > > >> > Hi Solr community,
> > > >> >
> > > >> > I can find many blog posts on how to deploy Solr with docker but I
> > am
> > > >> > wondering if Solr/Docker is really ready for production.
> > > >> > Has anybody ever ran Solr in production with Docker?
> > > >>
> > > >> Hi Aurelien,
> > > >>
> > > >> I'm wondering if there's anything specific that is needed to run
> Solr
> > > >> inside Docker? Is there something you have in mind?
> > > >>
> > > >> Upayavira
> > > >>
> > > >
> > > >
> > > > --
> > > > *Doug Turnbull **| *Search Relevance Consultant | OpenSource
> > Connections
> > > > <http://opensourceconnections.com>, LLC | 240.476.9983
> > > > Author: Relevant Search <http://manning.com/turnbull>
> > > > This e-mail and all contents, including attachments, is considered to
> > be
> > > > Company Confidential unless explicitly stated otherwise, regardless
> > > > of whether attachments are marked as such.
> > > >
> > > >
> > >
> >
> >
> >
> > --
> > Vincenzo D'Amore
> > email: v.dam...@gmail.com
> > skype: free.dev
> > mobile: +39 349 8513251
> >
>

Re: SOLR in Production

[rulinma]

AA machine is ok. Maybe SolrCloud is also a good choice for this.



--
View this message in context: 
http://lucene.472066.n3.nabble.com/SOLR-in-Production-tp4143496p4146972.html
Sent from the Solr - User mailing list archive at Nabble.com.

Tomcat or Jetty to use with solr in production ?

[gurunath]

Hi,

Confused with lot of reviews on Jetty and tomcat along with solr 4.7 ?, Is
there any better option for production. want to know the complexity's with
tomcat and jetty in future, as i want to cluster with huge data on solr.

Thanks



--
View this message in context: 
http://lucene.472066.n3.nabble.com/Tomcat-or-Jetty-to-use-with-solr-in-production-tp4144712.html
Sent from the Solr - User mailing list archive at Nabble.com.

Re: Tomcat or Jetty to use with solr in production ?

[Ahmet Arslan]

Hi,

solr test cases use embedded jetty therefore jetty is the recommended one.

Ahmet



On Monday, June 30, 2014 12:08 PM, gurunath gurunath@ge.com wrote:
Hi,

Confused with lot of reviews on Jetty and tomcat along with solr 4.7 ?, Is
there any better option for production. want to know the complexity's with
tomcat and jetty in future, as i want to cluster with huge data on solr.

Thanks



--
View this message in context: 
http://lucene.472066.n3.nabble.com/Tomcat-or-Jetty-to-use-with-solr-in-production-tp4144712.html
Sent from the Solr - User mailing list archive at Nabble.com.

Re: Tomcat or Jetty to use with solr in production ?

[Otis Gospodnetic]

Hi Gurunath,

In 90% of our engagements with various Solr customers we see Jetty, which
we also recommend and use ourselves for Solr + our own services and
products.

Otis
--
Performance Monitoring * Log Analytics * Search Analytics
Solr  Elasticsearch Support * http://sematext.com/



On Mon, Jun 30, 2014 at 5:07 AM, gurunath gurunath@ge.com wrote:

 Hi,

 Confused with lot of reviews on Jetty and tomcat along with solr 4.7 ?, Is
 there any better option for production. want to know the complexity's with
 tomcat and jetty in future, as i want to cluster with huge data on solr.

 Thanks



 --
 View this message in context:
 http://lucene.472066.n3.nabble.com/Tomcat-or-Jetty-to-use-with-solr-in-production-tp4144712.html
 Sent from the Solr - User mailing list archive at Nabble.com.

Re: Tomcat or Jetty to use with solr in production ?

[Erick Erickson]

The only thing I would add is that if you _already_
are a tomcat shop and have considerable
expertise running Tomcat, it might just be easier
to stick with what you know.

But if you have a choice, Jetty is where I'd go.

Best,
Erick

On Mon, Jun 30, 2014 at 4:06 AM, Otis Gospodnetic
otis.gospodne...@gmail.com wrote:
 Hi Gurunath,

 In 90% of our engagements with various Solr customers we see Jetty, which
 we also recommend and use ourselves for Solr + our own services and
 products.

 Otis
 --
 Performance Monitoring * Log Analytics * Search Analytics
 Solr  Elasticsearch Support * http://sematext.com/



 On Mon, Jun 30, 2014 at 5:07 AM, gurunath gurunath@ge.com wrote:

 Hi,

 Confused with lot of reviews on Jetty and tomcat along with solr 4.7 ?, Is
 there any better option for production. want to know the complexity's with
 tomcat and jetty in future, as i want to cluster with huge data on solr.

 Thanks



 --
 View this message in context:
 http://lucene.472066.n3.nabble.com/Tomcat-or-Jetty-to-use-with-solr-in-production-tp4144712.html
 Sent from the Solr - User mailing list archive at Nabble.com.

Re: Tomcat or Jetty to use with solr in production ?

[Steve McKay]

Seconding this. Solr works fine on Jetty. Solr also works fine on Tomcat. The 
Solr community largely uses Jetty, so most of the resources on the Web are for 
running Solr on Jetty, but if you have a reason to use Tomcat and know what 
you're doing then Tomcat is a fine choice.

On Jun 30, 2014, at 11:58 AM, Erick Erickson erickerick...@gmail.com wrote:

 The only thing I would add is that if you _already_
 are a tomcat shop and have considerable
 expertise running Tomcat, it might just be easier
 to stick with what you know.
 
 But if you have a choice, Jetty is where I'd go.
 
 Best,
 Erick
 
 On Mon, Jun 30, 2014 at 4:06 AM, Otis Gospodnetic
 otis.gospodne...@gmail.com wrote:
 Hi Gurunath,
 
 In 90% of our engagements with various Solr customers we see Jetty, which
 we also recommend and use ourselves for Solr + our own services and
 products.
 
 Otis
 --
 Performance Monitoring * Log Analytics * Search Analytics
 Solr  Elasticsearch Support * http://sematext.com/
 
 
 
 On Mon, Jun 30, 2014 at 5:07 AM, gurunath gurunath@ge.com wrote:
 
 Hi,
 
 Confused with lot of reviews on Jetty and tomcat along with solr 4.7 ?, Is
 there any better option for production. want to know the complexity's with
 tomcat and jetty in future, as i want to cluster with huge data on solr.
 
 Thanks
 
 
 
 --
 View this message in context:
 http://lucene.472066.n3.nabble.com/Tomcat-or-Jetty-to-use-with-solr-in-production-tp4144712.html
 Sent from the Solr - User mailing list archive at Nabble.com.
 

SOLR in Production

[EXTERNAL Taminidi Ravi (ETI, Automotive-Service-Solutions)]

Hi, We are planning to move solr for Production Environment. I like to get some 
real time experience or checklist to take care.

We have 1 instance of Solr with 2 Cores. What should be taken care in case of 
the solr instance is down?

What I have to do , if I have 2 instances, the first one is down and I like to 
use the 2 instance without any change in user experience?

Some reference related to this are really appreciable.

Thanks

Ravi

Re: SOLR in Production

[Shalin Shekhar Mangar]

You need to decide between SolrCloud and non-solrcloud mode. A SolrCloud
cluster will need external ZooKeeper instances and will provide failover,
replication, sharding and load balancing between replicas automatically.
But if your needs are small then you can go with a non-solrcloud cluster as
you currently have. Typically people setup a master-slave architecture
where writes are sent to the master only and query requests are load
balanced between both master and slaves. The downside to this approach is
that if you lose the master then writes will fail until you manually bring
the master back.


On Mon, Jun 23, 2014 at 11:51 PM, EXTERNAL Taminidi Ravi (ETI,
Automotive-Service-Solutions) external.ravi.tamin...@us.bosch.com wrote:


 Hi, We are planning to move solr for Production Environment. I like to get
 some real time experience or checklist to take care.

 We have 1 instance of Solr with 2 Cores. What should be taken care in case
 of the solr instance is down?

 What I have to do , if I have 2 instances, the first one is down and I
 like to use the 2 instance without any change in user experience?

 Some reference related to this are really appreciable.

 Thanks

 Ravi




-- 
Regards,
Shalin Shekhar Mangar.

Setting up solr on production server

[Jay Potharaju]

Hi,
I 'm looking for some tips or guidelines to installing solr on the
production server. I am currently using jetty in my dev environment.
Is it recommended to use tomcat on the production server?  Are there are
major advantages of using one over another.

Thanks
J

RE: Setting up solr on production server

[Suresh Soundararajan]

You can go ahead with Tomcat by deploying the solr war in it. It is highly 
scalable.

Thanks,
SureshKumar.S


From: Jay Potharaju jspothar...@gmail.com
Sent: Friday, February 21, 2014 11:10 AM
To: solr-user@lucene.apache.org
Subject: Setting up solr on production server

Hi,
I 'm looking for some tips or guidelines to installing solr on the
production server. I am currently using jetty in my dev environment.
Is it recommended to use tomcat on the production server?  Are there are
major advantages of using one over another.

Thanks
J
[Aspire Systems]

This e-mail message and any attachments are for the sole use of the intended 
recipient(s) and may contain proprietary, confidential, trade secret or 
privileged information. Any unauthorized review, use, disclosure or 
distribution is prohibited and may be a violation of law. If you are not the 
intended recipient, please contact the sender by reply e-mail and destroy all 
copies of the original message.

Re: Setting up solr on production server

[Shawn Heisey]

On 2/20/2014 10:40 PM, Jay Potharaju wrote:
 I 'm looking for some tips or guidelines to installing solr on the
 production server. I am currently using jetty in my dev environment.
 Is it recommended to use tomcat on the production server?  Are there are
 major advantages of using one over another.

The recommendation is to use the jetty (version 8) that comes with Solr.
 It has had a number of unnecessary components removed, and its config
has had a few things tweaked, but otherwise it is unchanged from what
you get if you download the same version from www.eclipse.org.

Jetty is not a toy servlet container.  It is a battle-tested
enterprise-ready system.  It is also the only servlet container that
gets officially tested with Solr.  I have been using Solr under jetty
for nearly four years.

If you don't want to mess with creating your own startup scripts, you
could use a packaged jetty made for (or provided by) your operating
system, but the configuration will probably need tweaking.  At the very
least you may need to increase maxThreads.

There's only one good reason I can think of to use something like
Tomcat.  That is when you already know another servlet container
*really* well, and know how to tune it for varying application requirements.

Thanks,
Shawn

Solr in production env.

[Simon Willnauer]

Hello,

I almost convinced my boss to use Solr in production for a new project
and hopefully for lots of following projects but I'm a bit confused
that there is no release available for download. Is Solr still in a
beta state, are there solr servers in production. Is it recommendable
to use it in production? I would be glad about some experience and
recommendations about this topic.


best regards Simon

Re: Solr in production env.

[Eivind Hasle Amundsen]

I know about a number of production installations.
I even know of a company which mere existence is based partly on Solr. :)

There is also a public list of production installations available on the 
homepage and/or Wiki.


Eivind