What I am faced with is this. I have to create my own crawler, similar to DIH. I have to deploy this on the same server as Solr (this is given, I cannot change it). I have to manage this crawler just like I have to manage my Solr deployment using Solr API through HTTP request. I figured if I deploy my application under Jetty, with Solr, then problem is solved.
The other option I looked at is writing my own handler for my crawler and plugging it into Solr's solrconfig.xml. If I do this, then my crawler will run in the same JVM space as Solr, this is something I want to avoid. Yet another option is for me deploy a second instance of Jetty on the Solr server just for my crawler. This is over kill in my opinion. What do folks think about this and what's the best way to approach this issue? Deploy my crawler on a separate server is not an option and for my use case Solr will be used in a lightweight so there is plenty of CPU / RAM on this one server to host Solr and my crawler. Steve On Tue, Jul 7, 2015 at 12:31 PM, Upayavira <u...@odoko.co.uk> wrote: > > > On Tue, Jul 7, 2015, at 05:03 PM, Steven White wrote: > > Hi Everyone, > > > > This may be a question to be posted on Jetty mailing list, but I figured > > I > > should start here first. > > > > Using Solr 5.2.0, when I start Solr, http://localhost:8983/solr/ is the > > entry point. My question is: > > > > 1) Where is "solr" on the file system? > > 2) How can I add http://localhost:8983/MyHandler/ to Jetty? > > > > For #2, I'm exploring the possibility of using the existing Web Server to > > see if I can have an additional application running on the same host as > > Solr. > > Why do you want to do this? It is not recommended as you are not > supposed to think of Solr as a servlet container. > > If you *must*, then you can place a war file in the webapps directory > next to solr.war and it will expand and be available when you start > Jetty. > > You cannot be sure that this behaviour will work long term. > > Upayavira >
