lucene-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Apache Wiki <wikidi...@apache.org>
Subject [Solr Wiki] Update of "WhyNoWar" by ShawnHeisey
Date Mon, 24 Apr 2017 13:31:45 GMT
Dear Wiki user,

You have subscribed to a wiki page or wiki category on "Solr Wiki" for change notification.

The "WhyNoWar" page has been changed by ShawnHeisey:
https://wiki.apache.org/solr/WhyNoWar?action=diff&rev1=21&rev2=22

Comment:
Fix typo.  Clarify that an unsupported container will *probably* work, but we can't be sure.

  
  == Can I still deploy Solr 5.x or 6.x in another container? ==
  
- For the moment, yes.  You won't find documentation on how to do this here or in the reference
guide.  You'll need to consult the documentation for the container you plan to use.
+ For the moment, probably, but we cannot be sure everything will work like it does in Jetty.
 You won't find documentation on how to do this here or in the reference guide.  You'll need
to consult the documentation for the container you plan to use.
  
  === Solr 5.0 through 5.2.1 ===
  
@@ -56, +56 @@

  
  Note that if you choose to do this kind of deployment, you are on your own.  The project
cannot support every container out there.  Solr already has problems deploying in some containers,
even with older releases that DID have the .war file in the dist directory.  If bugs are filed
on these problems, they will be closed without action.
  
- ASt some point in the future, date unknown, Solr will become a completely standalone application.
 When that happens, there will be no guarantee that users can still compile Solr in a way
that can be deployed in a third-party container.  This remains an option at the moment, but
that option is expected to disappear in a later release.
+ At some point in the future, date unknown, Solr will become a completely standalone application.
 When that happens, there will be no guarantee that users can still compile Solr in a way
that can be deployed in a third-party container.  This remains an option at the moment, but
that option is expected to disappear in a later release.
  
  One of the ideas that has been considered is to make Solr into ''two'' applications -- the
first would be a controller application with minimal memory requirements.  That application
would be responsible for running and monitoring a second JVM running the main application.
 With proper communication between those two apps, we would have the ability to place more
things under the control of the admin UI -- things like security settings, listening port,
memory allocations, GC tuning, Solr restarts, etc.
  

Mime
View raw message