"Yup. Solr 5 is not a WAR. It's a search server application."
or it is still what is was before, just the fact that it is servlet based is hidden now, and without the obvious option of alternative deployments.
Regardless, I'll update solr-undertow (which already makes it a search server application by using the WAR outside of an application server) to work with a distribution archive instead of the packaged WAR. The WAR had less files than a full distribution which also includes examples so this makes Solr bigger.
Would be nice if you do this that you make a clean distribution as well without any samples and just minimal placeholder files.
Also with this change are the parameters for things like jetty.port, solr.home, solr.data going to be cleaned up and use something like a configuration file? or made more uniform and obvious in some way?
This was something else I cleaned up in https://github.com/bremeld/solr-undertow using typesafe config. Maybe merge some of those ideas in and I can drop the separate project. But then again rate limiters to protect the server and other features might be missing...
Also, we should review the thread and other settings that were previously recommended by Jetty if it is continued to be used, because they were excessive (10,000 will exceed most file limits set per user on boxes by default, and is unnecessarily high). Settings like this create a chance for the server to fail under high load rather than just slow down, it is more likely to crash.
Also, multiple ports. One for internal communication, another for external, maybe another for updates different from queries, for admin. Helps to make sure that under load (eating the thread pool) a server still responds for other needs.
If you take on responsibility to provide Solr as a server, it needs to start adding features around these other issues. Otherwise people will be configuring something in front of Solr to proxy and protect it, and then you might as well have stayed in a WAR so they could do it within the same process.