On 2/19/2016 8:47 PM, Brian Wright wrote: > Here's the fundamental issue when talking about use of software like > Solr in a corporate environment. As a systems engineer at Marketo, my > best practices recommendations and justifications are based on the > documentation provided by the project owners. If the project's docs > state that something is feasible without any warnings, not only will > the software engineer latch onto that documentation and want to use it > in that way, my hands will be tied as a systems engineer when I'm > expected to roll that architecture to production, as I have nothing to > argue against that use case.
I've updated the "Taking Solr to Production" reference guide page with what I feel is an appropriate caution against running multiple instances in a typical installation. I'd actually like to use stronger language, but I worry that doing so will also discourage those who have a viable use case. This change to the reference guide is live on the Confluence wiki, but it will most likely not appear in a released version of the guide until the 6.0 version. The 5.5 version of the guide has already been built and is in the final approval phase now. Thanks, Shawn
