Re: Solr 4 (CloudSolrServer and LBHttpSolrServer question)
CloudSolrServer can be used for indexing and is smart about indexing since it knows the current cluster state. For 4.0 I'd use one per collection because there is a bug around this fixed in the upcoming 4.1 (using one for more than one collection). In fact, if you are moving to 4, it's a good idea to get your feet wet with 4.0, but I'd hold off for 4.1 for production if you can. Huge number of bug fixes and improvements. - Mark On Jan 4, 2013, at 10:06 AM, Jay Parashar jparas...@itscape.com wrote: Hi, I am trying to migrate to Solr 4 (from 3.6) for a multithreaded/multicollection environment using the Solrj java client. I need some clarification of when to use the Cloud Solr Server vs LBHttpSolrServer. Any help is appreciated. Which one do I use? The CloudSolrServer uses the LB server internally so should this be the one for both searching and indexing? The documentation says the LB server must not be used for indexing. As the CloudSolrServer uses the LB server internally, so I guess we should not use it for indexing. Is this correct? So if the ConcurrentUpdateSolrServer is used for indexing, how do I load balance that? Reusing: Should I create multiple Cloud Solr Servers, one for each collection? Simply put, what is the best practice for reusing a server in a multithreaded/multicollection scenario and what server do I use for indexing and querying? The CloudSolrServer instantiates a new LB server per request. Isn't that expensive? On Solr 3.6, I used the ConcurrentUpdateSolrServer for indexing and the HttpSolrServer for searching. In each case, I had a new server per core and reused (I used a MAP with the corename as key and the server as the value). So for 5 cores, I had 5 servers identified by the core and re-used. I did this as I understood instantiating a new server for every request was expensive Thanks Jay
Re: Solr 4 (CloudSolrServer and LBHttpSolrServer question)
Any release stimation date, Mark? I heard something about January. I was considering using 4.0 for production but if 4.1 release is incomming I could wait a little more. 2013/1/4 Mark Miller markrmil...@gmail.com CloudSolrServer can be used for indexing and is smart about indexing since it knows the current cluster state. For 4.0 I'd use one per collection because there is a bug around this fixed in the upcoming 4.1 (using one for more than one collection). In fact, if you are moving to 4, it's a good idea to get your feet wet with 4.0, but I'd hold off for 4.1 for production if you can. Huge number of bug fixes and improvements. - Mark On Jan 4, 2013, at 10:06 AM, Jay Parashar jparas...@itscape.com wrote: Hi, I am trying to migrate to Solr 4 (from 3.6) for a multithreaded/multicollection environment using the Solrj java client. I need some clarification of when to use the Cloud Solr Server vs LBHttpSolrServer. Any help is appreciated. Which one do I use? The CloudSolrServer uses the LB server internally so should this be the one for both searching and indexing? The documentation says the LB server must not be used for indexing. As the CloudSolrServer uses the LB server internally, so I guess we should not use it for indexing. Is this correct? So if the ConcurrentUpdateSolrServer is used for indexing, how do I load balance that? Reusing: Should I create multiple Cloud Solr Servers, one for each collection? Simply put, what is the best practice for reusing a server in a multithreaded/multicollection scenario and what server do I use for indexing and querying? The CloudSolrServer instantiates a new LB server per request. Isn't that expensive? On Solr 3.6, I used the ConcurrentUpdateSolrServer for indexing and the HttpSolrServer for searching. In each case, I had a new server per core and reused (I used a MAP with the corename as key and the server as the value). So for 5 cores, I had 5 servers identified by the core and re-used. I did this as I understood instantiating a new server for every request was expensive Thanks Jay
Re: Solr 4 (CloudSolrServer and LBHttpSolrServer question)
On 1/4/2013 8:54 AM, Luis Cappa Banda wrote: Any release stimation date, Mark? I heard something about January. I was considering using 4.0 for production but if 4.1 release is incomming I could wait a little more. I'm not a committer, but I contribute the occasional patch and keep an eye on things so I know where things are with the issues that I file. Right after Christmas, the number of open Lucene and Solr issues for 4.1 was well over 400. Just before the new year, the triage for a 4.1 release began. Most of those issues got moved to 4.2, and now that we're into the new year, I see tons of work being done to close the issues that remain in 4.1. Right now there are 57 open SOLR issues and 47 open LUCENE issues. It's likely that some of those will be bumped to 4.2 or closed without action, but that's pretty much the working list. Total speculation: A release before the end of January is *possible*, if no major hurdles are encountered. Realistically, I don't know if it's going to happen, but I remain hopeful. Solr 4.1 open issues: http://goo.gl/60oyB Lucene 4.1 open issues: http://goo.gl/ckyxX http://www.merriam-webster.com/dictionary/triage Thanks, Shawn
RE: Solr 4 (CloudSolrServer and LBHttpSolrServer question)
Thanks Mark. -Original Message- From: Mark Miller [mailto:markrmil...@gmail.com] Sent: Friday, January 04, 2013 9:51 AM To: solr-user@lucene.apache.org Subject: Re: Solr 4 (CloudSolrServer and LBHttpSolrServer question) CloudSolrServer can be used for indexing and is smart about indexing since it knows the current cluster state. For 4.0 I'd use one per collection because there is a bug around this fixed in the upcoming 4.1 (using one for more than one collection). In fact, if you are moving to 4, it's a good idea to get your feet wet with 4.0, but I'd hold off for 4.1 for production if you can. Huge number of bug fixes and improvements. - Mark On Jan 4, 2013, at 10:06 AM, Jay Parashar jparas...@itscape.com wrote: Hi, I am trying to migrate to Solr 4 (from 3.6) for a multithreaded/multicollection environment using the Solrj java client. I need some clarification of when to use the Cloud Solr Server vs LBHttpSolrServer. Any help is appreciated. Which one do I use? The CloudSolrServer uses the LB server internally so should this be the one for both searching and indexing? The documentation says the LB server must not be used for indexing. As the CloudSolrServer uses the LB server internally, so I guess we should not use it for indexing. Is this correct? So if the ConcurrentUpdateSolrServer is used for indexing, how do I load balance that? Reusing: Should I create multiple Cloud Solr Servers, one for each collection? Simply put, what is the best practice for reusing a server in a multithreaded/multicollection scenario and what server do I use for indexing and querying? The CloudSolrServer instantiates a new LB server per request. Isn't that expensive? On Solr 3.6, I used the ConcurrentUpdateSolrServer for indexing and the HttpSolrServer for searching. In each case, I had a new server per core and reused (I used a MAP with the corename as key and the server as the value). So for 5 cores, I had 5 servers identified by the core and re-used. I did this as I understood instantiating a new server for every request was expensive Thanks Jay
Re: Solr 4 (CloudSolrServer and LBHttpSolrServer question)
I'm going to push *hard* for a Jan release. Woe to those that get in my way :) - Mark On Jan 4, 2013, at 11:37 AM, Shawn Heisey s...@elyograg.org wrote: On 1/4/2013 8:54 AM, Luis Cappa Banda wrote: Any release stimation date, Mark? I heard something about January. I was considering using 4.0 for production but if 4.1 release is incomming I could wait a little more. I'm not a committer, but I contribute the occasional patch and keep an eye on things so I know where things are with the issues that I file. Right after Christmas, the number of open Lucene and Solr issues for 4.1 was well over 400. Just before the new year, the triage for a 4.1 release began. Most of those issues got moved to 4.2, and now that we're into the new year, I see tons of work being done to close the issues that remain in 4.1. Right now there are 57 open SOLR issues and 47 open LUCENE issues. It's likely that some of those will be bumped to 4.2 or closed without action, but that's pretty much the working list. Total speculation: A release before the end of January is *possible*, if no major hurdles are encountered. Realistically, I don't know if it's going to happen, but I remain hopeful. Solr 4.1 open issues: http://goo.gl/60oyB Lucene 4.1 open issues: http://goo.gl/ckyxX http://www.merriam-webster.com/dictionary/triage Thanks, Shawn
RE: Solr 4 (CloudSolrServer and LBHttpSolrServer question)
Well, i hope this won't spoil everything then: https://issues.apache.org/jira/browse/SOLR-4260 I'll continue tests monday -Original message- From:Mark Miller markrmil...@gmail.com Sent: Fri 04-Jan-2013 17:54 To: solr-user@lucene.apache.org Subject: Re: Solr 4 (CloudSolrServer and LBHttpSolrServer question) I'm going to push *hard* for a Jan release. Woe to those that get in my way :) - Mark On Jan 4, 2013, at 11:37 AM, Shawn Heisey s...@elyograg.org wrote: On 1/4/2013 8:54 AM, Luis Cappa Banda wrote: Any release stimation date, Mark? I heard something about January. I was considering using 4.0 for production but if 4.1 release is incomming I could wait a little more. I'm not a committer, but I contribute the occasional patch and keep an eye on things so I know where things are with the issues that I file. Right after Christmas, the number of open Lucene and Solr issues for 4.1 was well over 400. Just before the new year, the triage for a 4.1 release began. Most of those issues got moved to 4.2, and now that we're into the new year, I see tons of work being done to close the issues that remain in 4.1. Right now there are 57 open SOLR issues and 47 open LUCENE issues. It's likely that some of those will be bumped to 4.2 or closed without action, but that's pretty much the working list. Total speculation: A release before the end of January is *possible*, if no major hurdles are encountered. Realistically, I don't know if it's going to happen, but I remain hopeful. Solr 4.1 open issues: http://goo.gl/60oyB Lucene 4.1 open issues: http://goo.gl/ckyxX http://www.merriam-webster.com/dictionary/triage Thanks, Shawn
Re: Solr 4 (CloudSolrServer and LBHttpSolrServer question)
That's probably as official as anything ever gets around here. -- Jack Krupansky -Original Message- From: Mark Miller Sent: Friday, January 04, 2013 11:47 AM To: solr-user@lucene.apache.org Subject: Re: Solr 4 (CloudSolrServer and LBHttpSolrServer question) I'm going to push *hard* for a Jan release. Woe to those that get in my way :) - Mark On Jan 4, 2013, at 11:37 AM, Shawn Heisey s...@elyograg.org wrote: On 1/4/2013 8:54 AM, Luis Cappa Banda wrote: Any release stimation date, Mark? I heard something about January. I was considering using 4.0 for production but if 4.1 release is incomming I could wait a little more. I'm not a committer, but I contribute the occasional patch and keep an eye on things so I know where things are with the issues that I file. Right after Christmas, the number of open Lucene and Solr issues for 4.1 was well over 400. Just before the new year, the triage for a 4.1 release began. Most of those issues got moved to 4.2, and now that we're into the new year, I see tons of work being done to close the issues that remain in 4.1. Right now there are 57 open SOLR issues and 47 open LUCENE issues. It's likely that some of those will be bumped to 4.2 or closed without action, but that's pretty much the working list. Total speculation: A release before the end of January is *possible*, if no major hurdles are encountered. Realistically, I don't know if it's going to happen, but I remain hopeful. Solr 4.1 open issues: http://goo.gl/60oyB Lucene 4.1 open issues: http://goo.gl/ckyxX http://www.merriam-webster.com/dictionary/triage Thanks, Shawn
