Re: Using Solr For a Real Search Engine
Hi Otis; You are right. start.jar starts up an Jetty and there is a war file under example directory and deploys start.jar to itself, is that true? 2013/4/25 Otis Gospodnetic otis.gospodne...@gmail.com Suggestion : Don't call this embedded Jetty to avoid confusion with the actual embedded jetty. Otis Solr ElasticSearch Support http://sematext.com/ On Apr 23, 2013 4:56 PM, Furkan KAMACI furkankam...@gmail.com wrote: Thanks for the answers. I will go with embedded Jetty for my SolrCloud. If I face with something important I would want to share my experiences with you. 2013/4/23 Shawn Heisey s...@elyograg.org On 4/23/2013 2:25 PM, Furkan KAMACI wrote: Is there any documentation that explains using Jetty as embedded or not? I use Solr deployed at Tomcat but after you message I will consider about Jetty. If we think about other issues i.e. when I want to update my Solr jars/wars etc.(this is just an foo example) does any pros and cons Tomcat or Jetty has? The Jetty in the example is only 'embedded' in the sense that you don't have to install it separately. It is not special -- the Jetty components are not changed at all, a subset of them is just included in the Solr download with a tuned configuration file. If you go to www.eclipse.org/jetty and download the latest stable-8 version, you'll see some familiar things - start.jar, an etc directory, a lib directory, and a contexts directory. They have more in them than the example does -- extra functionality Solr doesn't need. If you want to start the downloaded version, you can use 'java -jar start.jar' just like you do with Solr. Thanks, Shawn
Re: Using Solr For a Real Search Engine
Hi, No, start.jar is not deployed. That *is* Jetty. This is what the real Embedded Jetty is about: http://wiki.eclipse.org/Jetty/Tutorial/Embedding_Jetty What we have here is Solr is just an *included* Jetty, so it's easier to get started. That's all. :) Otis -- Solr ElasticSearch Support http://sematext.com/ On Thu, Apr 25, 2013 at 3:30 AM, Furkan KAMACI furkankam...@gmail.com wrote: Hi Otis; You are right. start.jar starts up an Jetty and there is a war file under example directory and deploys start.jar to itself, is that true? 2013/4/25 Otis Gospodnetic otis.gospodne...@gmail.com Suggestion : Don't call this embedded Jetty to avoid confusion with the actual embedded jetty. Otis Solr ElasticSearch Support http://sematext.com/ On Apr 23, 2013 4:56 PM, Furkan KAMACI furkankam...@gmail.com wrote: Thanks for the answers. I will go with embedded Jetty for my SolrCloud. If I face with something important I would want to share my experiences with you. 2013/4/23 Shawn Heisey s...@elyograg.org On 4/23/2013 2:25 PM, Furkan KAMACI wrote: Is there any documentation that explains using Jetty as embedded or not? I use Solr deployed at Tomcat but after you message I will consider about Jetty. If we think about other issues i.e. when I want to update my Solr jars/wars etc.(this is just an foo example) does any pros and cons Tomcat or Jetty has? The Jetty in the example is only 'embedded' in the sense that you don't have to install it separately. It is not special -- the Jetty components are not changed at all, a subset of them is just included in the Solr download with a tuned configuration file. If you go to www.eclipse.org/jetty and download the latest stable-8 version, you'll see some familiar things - start.jar, an etc directory, a lib directory, and a contexts directory. They have more in them than the example does -- extra functionality Solr doesn't need. If you want to start the downloaded version, you can use 'java -jar start.jar' just like you do with Solr. Thanks, Shawn
Re: Using Solr For a Real Search Engine
Thanks, Otis I got it. 2013/4/25 Otis Gospodnetic otis.gospodne...@gmail.com Hi, No, start.jar is not deployed. That *is* Jetty. This is what the real Embedded Jetty is about: http://wiki.eclipse.org/Jetty/Tutorial/Embedding_Jetty What we have here is Solr is just an *included* Jetty, so it's easier to get started. That's all. :) Otis -- Solr ElasticSearch Support http://sematext.com/ On Thu, Apr 25, 2013 at 3:30 AM, Furkan KAMACI furkankam...@gmail.com wrote: Hi Otis; You are right. start.jar starts up an Jetty and there is a war file under example directory and deploys start.jar to itself, is that true? 2013/4/25 Otis Gospodnetic otis.gospodne...@gmail.com Suggestion : Don't call this embedded Jetty to avoid confusion with the actual embedded jetty. Otis Solr ElasticSearch Support http://sematext.com/ On Apr 23, 2013 4:56 PM, Furkan KAMACI furkankam...@gmail.com wrote: Thanks for the answers. I will go with embedded Jetty for my SolrCloud. If I face with something important I would want to share my experiences with you. 2013/4/23 Shawn Heisey s...@elyograg.org On 4/23/2013 2:25 PM, Furkan KAMACI wrote: Is there any documentation that explains using Jetty as embedded or not? I use Solr deployed at Tomcat but after you message I will consider about Jetty. If we think about other issues i.e. when I want to update my Solr jars/wars etc.(this is just an foo example) does any pros and cons Tomcat or Jetty has? The Jetty in the example is only 'embedded' in the sense that you don't have to install it separately. It is not special -- the Jetty components are not changed at all, a subset of them is just included in the Solr download with a tuned configuration file. If you go to www.eclipse.org/jetty and download the latest stable-8 version, you'll see some familiar things - start.jar, an etc directory, a lib directory, and a contexts directory. They have more in them than the example does -- extra functionality Solr doesn't need. If you want to start the downloaded version, you can use 'java -jar start.jar' just like you do with Solr. Thanks, Shawn
Re: Using Solr For a Real Search Engine
Suggestion : Don't call this embedded Jetty to avoid confusion with the actual embedded jetty. Otis Solr ElasticSearch Support http://sematext.com/ On Apr 23, 2013 4:56 PM, Furkan KAMACI furkankam...@gmail.com wrote: Thanks for the answers. I will go with embedded Jetty for my SolrCloud. If I face with something important I would want to share my experiences with you. 2013/4/23 Shawn Heisey s...@elyograg.org On 4/23/2013 2:25 PM, Furkan KAMACI wrote: Is there any documentation that explains using Jetty as embedded or not? I use Solr deployed at Tomcat but after you message I will consider about Jetty. If we think about other issues i.e. when I want to update my Solr jars/wars etc.(this is just an foo example) does any pros and cons Tomcat or Jetty has? The Jetty in the example is only 'embedded' in the sense that you don't have to install it separately. It is not special -- the Jetty components are not changed at all, a subset of them is just included in the Solr download with a tuned configuration file. If you go to www.eclipse.org/jetty and download the latest stable-8 version, you'll see some familiar things - start.jar, an etc directory, a lib directory, and a contexts directory. They have more in them than the example does -- extra functionality Solr doesn't need. If you want to start the downloaded version, you can use 'java -jar start.jar' just like you do with Solr. Thanks, Shawn
Re: Using Solr For a Real Search Engine
At first I will work on 100 Solr nodes and I want to use Tomcat as container and deploy Solr as a war. I just wonder what folks are using for large systems and what kind of problems or benefits they have with their choices. 2013/3/26 Otis Gospodnetic otis.gospodne...@gmail.com Hi, This question is too open-ended for anyone to give you a good answer. Maybe you want to ask more specific questions? As for embedding vs. war, start with a simpler war and think about the alternatives if that doesn't work for you. Otis -- Solr ElasticSearch Support http://sematext.com/ On Fri, Mar 22, 2013 at 8:07 AM, Furkan KAMACI furkankam...@gmail.com wrote: If I want to use Solr in a web search engine what kind of strategies should I follow about how to run Solr. I mean I can run it via embedded jetty or use war and deploy to a container? You should consider that I will have heavy work load on my Solr.
Re: Using Solr For a Real Search Engine
Tomcat should work just fine in most cases. The downside to Tomcat is that all of the devs generally run Jetty since it's the default. Also, all of our units tests run against Jetty - in fact, a specific version of Jetty. Usually, Solr will run fine in other webapps. Many, many users run Solr in other webapps. All of our tests run against a specific version of Jetty though. In some (generally rare) cases, that means something might work with Jetty and not another container until/unless the issue is reported by a user and fixed. - Mark On Apr 23, 2013, at 3:25 PM, Furkan KAMACI furkankam...@gmail.com wrote: At first I will work on 100 Solr nodes and I want to use Tomcat as container and deploy Solr as a war. I just wonder what folks are using for large systems and what kind of problems or benefits they have with their choices. 2013/3/26 Otis Gospodnetic otis.gospodne...@gmail.com Hi, This question is too open-ended for anyone to give you a good answer. Maybe you want to ask more specific questions? As for embedding vs. war, start with a simpler war and think about the alternatives if that doesn't work for you. Otis -- Solr ElasticSearch Support http://sematext.com/ On Fri, Mar 22, 2013 at 8:07 AM, Furkan KAMACI furkankam...@gmail.com wrote: If I want to use Solr in a web search engine what kind of strategies should I follow about how to run Solr. I mean I can run it via embedded jetty or use war and deploy to a container? You should consider that I will have heavy work load on my Solr.
Re: Using Solr For a Real Search Engine
Thanks for the answer. If I find something that explains using embedded Jetty or Jetty, or Tomcat it would be nice. 2013/4/23 Mark Miller markrmil...@gmail.com Tomcat should work just fine in most cases. The downside to Tomcat is that all of the devs generally run Jetty since it's the default. Also, all of our units tests run against Jetty - in fact, a specific version of Jetty. Usually, Solr will run fine in other webapps. Many, many users run Solr in other webapps. All of our tests run against a specific version of Jetty though. In some (generally rare) cases, that means something might work with Jetty and not another container until/unless the issue is reported by a user and fixed. - Mark On Apr 23, 2013, at 3:25 PM, Furkan KAMACI furkankam...@gmail.com wrote: At first I will work on 100 Solr nodes and I want to use Tomcat as container and deploy Solr as a war. I just wonder what folks are using for large systems and what kind of problems or benefits they have with their choices. 2013/3/26 Otis Gospodnetic otis.gospodne...@gmail.com Hi, This question is too open-ended for anyone to give you a good answer. Maybe you want to ask more specific questions? As for embedding vs. war, start with a simpler war and think about the alternatives if that doesn't work for you. Otis -- Solr ElasticSearch Support http://sematext.com/ On Fri, Mar 22, 2013 at 8:07 AM, Furkan KAMACI furkankam...@gmail.com wrote: If I want to use Solr in a web search engine what kind of strategies should I follow about how to run Solr. I mean I can run it via embedded jetty or use war and deploy to a container? You should consider that I will have heavy work load on my Solr.
Re: Using Solr For a Real Search Engine
My 2 cents on this is if you have a choice, just stick with Jetty. This article has some pretty convincing information: http://www.openlogic.com/wazi/bid/257366/Power-Java-based-web-apps-with-Jetty-application-server The folks over at OpenLogic definitely know their stuff when it comes to supporting open source Java app servers. I was impressed by the fact that Google migrated from Tomcat to Jetty for AppEngine, which is pretty compelling evidence that Jetty works well in a very large cluster. Lastly, the bulk of the processing in Solr happens in Solr/Lucene code and Jetty (or whatever engine you choose) is a very small part of any request. On Tue, Apr 23, 2013 at 1:52 PM, Furkan KAMACI furkankam...@gmail.com wrote: Thanks for the answer. If I find something that explains using embedded Jetty or Jetty, or Tomcat it would be nice. 2013/4/23 Mark Miller markrmil...@gmail.com Tomcat should work just fine in most cases. The downside to Tomcat is that all of the devs generally run Jetty since it's the default. Also, all of our units tests run against Jetty - in fact, a specific version of Jetty. Usually, Solr will run fine in other webapps. Many, many users run Solr in other webapps. All of our tests run against a specific version of Jetty though. In some (generally rare) cases, that means something might work with Jetty and not another container until/unless the issue is reported by a user and fixed. - Mark On Apr 23, 2013, at 3:25 PM, Furkan KAMACI furkankam...@gmail.com wrote: At first I will work on 100 Solr nodes and I want to use Tomcat as container and deploy Solr as a war. I just wonder what folks are using for large systems and what kind of problems or benefits they have with their choices. 2013/3/26 Otis Gospodnetic otis.gospodne...@gmail.com Hi, This question is too open-ended for anyone to give you a good answer. Maybe you want to ask more specific questions? As for embedding vs. war, start with a simpler war and think about the alternatives if that doesn't work for you. Otis -- Solr ElasticSearch Support http://sematext.com/ On Fri, Mar 22, 2013 at 8:07 AM, Furkan KAMACI furkankam...@gmail.com wrote: If I want to use Solr in a web search engine what kind of strategies should I follow about how to run Solr. I mean I can run it via embedded jetty or use war and deploy to a container? You should consider that I will have heavy work load on my Solr.
Re: Using Solr For a Real Search Engine
Is there any documentation that explains using Jetty as embedded or not? I use Solr deployed at Tomcat but after you message I will consider about Jetty. If we think about other issues i.e. when I want to update my Solr jars/wars etc.(this is just an foo example) does any pros and cons Tomcat or Jetty has? 2013/4/23 Timothy Potter thelabd...@gmail.com My 2 cents on this is if you have a choice, just stick with Jetty. This article has some pretty convincing information: http://www.openlogic.com/wazi/bid/257366/Power-Java-based-web-apps-with-Jetty-application-server The folks over at OpenLogic definitely know their stuff when it comes to supporting open source Java app servers. I was impressed by the fact that Google migrated from Tomcat to Jetty for AppEngine, which is pretty compelling evidence that Jetty works well in a very large cluster. Lastly, the bulk of the processing in Solr happens in Solr/Lucene code and Jetty (or whatever engine you choose) is a very small part of any request. On Tue, Apr 23, 2013 at 1:52 PM, Furkan KAMACI furkankam...@gmail.com wrote: Thanks for the answer. If I find something that explains using embedded Jetty or Jetty, or Tomcat it would be nice. 2013/4/23 Mark Miller markrmil...@gmail.com Tomcat should work just fine in most cases. The downside to Tomcat is that all of the devs generally run Jetty since it's the default. Also, all of our units tests run against Jetty - in fact, a specific version of Jetty. Usually, Solr will run fine in other webapps. Many, many users run Solr in other webapps. All of our tests run against a specific version of Jetty though. In some (generally rare) cases, that means something might work with Jetty and not another container until/unless the issue is reported by a user and fixed. - Mark On Apr 23, 2013, at 3:25 PM, Furkan KAMACI furkankam...@gmail.com wrote: At first I will work on 100 Solr nodes and I want to use Tomcat as container and deploy Solr as a war. I just wonder what folks are using for large systems and what kind of problems or benefits they have with their choices. 2013/3/26 Otis Gospodnetic otis.gospodne...@gmail.com Hi, This question is too open-ended for anyone to give you a good answer. Maybe you want to ask more specific questions? As for embedding vs. war, start with a simpler war and think about the alternatives if that doesn't work for you. Otis -- Solr ElasticSearch Support http://sematext.com/ On Fri, Mar 22, 2013 at 8:07 AM, Furkan KAMACI furkankam...@gmail.com wrote: If I want to use Solr in a web search engine what kind of strategies should I follow about how to run Solr. I mean I can run it via embedded jetty or use war and deploy to a container? You should consider that I will have heavy work load on my Solr.
Re: Using Solr For a Real Search Engine
On 4/23/2013 1:52 PM, Furkan KAMACI wrote: Thanks for the answer. If I find something that explains using embedded Jetty or Jetty, or Tomcat it would be nice. 2013/4/23 Mark Miller markrmil...@gmail.com Tomcat should work just fine in most cases. The downside to Tomcat is that all of the devs generally run Jetty since it's the default. Also, all of our units tests run against Jetty - in fact, a specific version of Jetty. Usually, Solr will run fine in other webapps. Many, many users run Solr in other webapps. All of our tests run against a specific version of Jetty though. In some (generally rare) cases, that means something might work with Jetty and not another container until/unless the issue is reported by a user and fixed. Mark outlines a really good reason to use Jetty - it's extremely well tested. New tests are being added all the time, and most of those will start Jetty to run. If you don't already have a good reason to use a container other than the Jetty included in Solr, then go and copy the example setup and modify it until it does what you need. The one thing that's really missing is an init script to manage Solr startup and shutdown. I plan to do something about that, but I've got a lot of cleanup to do on it. I've only come across one truly compelling reason to use something else: If your system admins are already familiar with Tomcat, Glassfish, or something else, then you probably want to stick with that. For instance, you may have automation in place for deploying and managing farms of Tomcat servers. Switching would likely be too painful. There could be features useful for Solr in other containers that I don't know about. If there are, and someone has a good reason for needing those features, let us know about them. Update the wiki. Jetty is a low-overhead servlet container without a lot of fancy features. The Jetty instance that is included in the Solr example is a bare-bones setup. It does not include all of the jars or config found in a full Jetty download, because those features are not needed for Solr. Thanks, Shawn
Re: Using Solr For a Real Search Engine
According to answers here for a huge crawling system and high response time searching SolrCloud system I will try Jetty. If anyone has a good reason they can explain it here, you are right. By the way, Shawn when I read you answer I understand that I should choose embedded Jetty, is that right? 2013/4/23 Shawn Heisey s...@elyograg.org On 4/23/2013 1:52 PM, Furkan KAMACI wrote: Thanks for the answer. If I find something that explains using embedded Jetty or Jetty, or Tomcat it would be nice. 2013/4/23 Mark Miller markrmil...@gmail.com Tomcat should work just fine in most cases. The downside to Tomcat is that all of the devs generally run Jetty since it's the default. Also, all of our units tests run against Jetty - in fact, a specific version of Jetty. Usually, Solr will run fine in other webapps. Many, many users run Solr in other webapps. All of our tests run against a specific version of Jetty though. In some (generally rare) cases, that means something might work with Jetty and not another container until/unless the issue is reported by a user and fixed. Mark outlines a really good reason to use Jetty - it's extremely well tested. New tests are being added all the time, and most of those will start Jetty to run. If you don't already have a good reason to use a container other than the Jetty included in Solr, then go and copy the example setup and modify it until it does what you need. The one thing that's really missing is an init script to manage Solr startup and shutdown. I plan to do something about that, but I've got a lot of cleanup to do on it. I've only come across one truly compelling reason to use something else: If your system admins are already familiar with Tomcat, Glassfish, or something else, then you probably want to stick with that. For instance, you may have automation in place for deploying and managing farms of Tomcat servers. Switching would likely be too painful. There could be features useful for Solr in other containers that I don't know about. If there are, and someone has a good reason for needing those features, let us know about them. Update the wiki. Jetty is a low-overhead servlet container without a lot of fancy features. The Jetty instance that is included in the Solr example is a bare-bones setup. It does not include all of the jars or config found in a full Jetty download, because those features are not needed for Solr. Thanks, Shawn
Re: Using Solr For a Real Search Engine
On 4/23/2013 2:25 PM, Furkan KAMACI wrote: Is there any documentation that explains using Jetty as embedded or not? I use Solr deployed at Tomcat but after you message I will consider about Jetty. If we think about other issues i.e. when I want to update my Solr jars/wars etc.(this is just an foo example) does any pros and cons Tomcat or Jetty has? The Jetty in the example is only 'embedded' in the sense that you don't have to install it separately. It is not special -- the Jetty components are not changed at all, a subset of them is just included in the Solr download with a tuned configuration file. If you go to www.eclipse.org/jetty and download the latest stable-8 version, you'll see some familiar things - start.jar, an etc directory, a lib directory, and a contexts directory. They have more in them than the example does -- extra functionality Solr doesn't need. If you want to start the downloaded version, you can use 'java -jar start.jar' just like you do with Solr. Thanks, Shawn
Re: Using Solr For a Real Search Engine
Thanks for the answers. I will go with embedded Jetty for my SolrCloud. If I face with something important I would want to share my experiences with you. 2013/4/23 Shawn Heisey s...@elyograg.org On 4/23/2013 2:25 PM, Furkan KAMACI wrote: Is there any documentation that explains using Jetty as embedded or not? I use Solr deployed at Tomcat but after you message I will consider about Jetty. If we think about other issues i.e. when I want to update my Solr jars/wars etc.(this is just an foo example) does any pros and cons Tomcat or Jetty has? The Jetty in the example is only 'embedded' in the sense that you don't have to install it separately. It is not special -- the Jetty components are not changed at all, a subset of them is just included in the Solr download with a tuned configuration file. If you go to www.eclipse.org/jetty and download the latest stable-8 version, you'll see some familiar things - start.jar, an etc directory, a lib directory, and a contexts directory. They have more in them than the example does -- extra functionality Solr doesn't need. If you want to start the downloaded version, you can use 'java -jar start.jar' just like you do with Solr. Thanks, Shawn
Re: Using Solr For a Real Search Engine
Hi, This question is too open-ended for anyone to give you a good answer. Maybe you want to ask more specific questions? As for embedding vs. war, start with a simpler war and think about the alternatives if that doesn't work for you. Otis -- Solr ElasticSearch Support http://sematext.com/ On Fri, Mar 22, 2013 at 8:07 AM, Furkan KAMACI furkankam...@gmail.comwrote: If I want to use Solr in a web search engine what kind of strategies should I follow about how to run Solr. I mean I can run it via embedded jetty or use war and deploy to a container? You should consider that I will have heavy work load on my Solr.
Using Solr For a Real Search Engine
If I want to use Solr in a web search engine what kind of strategies should I follow about how to run Solr. I mean I can run it via embedded jetty or use war and deploy to a container? You should consider that I will have heavy work load on my Solr.
