Re: solr 5 leaving tomcat, will I be the only one fearing about this?

> For cleaner version control on my system, I create $SOLR_HOME/lib as a > symlink to another directory that I create myself -- > $INSTALL_DIR/solrlib ... that way, all binary stuff like jars is in the > *program* version control location, not the *data* location. That’s right. It is possible to

Re: solr 5 leaving tomcat, will I be the only one fearing about this?

Thanks John... yes that was the first idea came to our mind, but it will require doubling our servers (in replica data centers as well etc), definitely we can't afford the cost. We have thought of first establishing a small pool of 'hot' servers and use them to take incoming new index data using

Re: solr 5 leaving tomcat, will I be the only one fearing about this?

Renee - you have probably already thought of this, but just in case it helps... (It helped me a lot several years ago and I hadn't thought of it at the time...) If you end up needing to do a big re-index, Production doesn't have to be affected (assuming you have the hardware/cloud resources).

Re: solr 5 leaving tomcat, will I be the only one fearing about this?

Shawn and Ari, the 3rd party jars are exactly just one of the concerns I have. We had more than just a multi-lingual integration, we have to integrate with many other 3rd party tools. We basically deploy all those jars into an 'external' lib extension path in production, then for each 3rd party

Re: solr 5 leaving tomcat, will I be the only one fearing about this?

For what it's worth / in case it's helpful... I haven't dealt with JDBC in this context so I can't offer anything useful there... You can reference the data in Zookeeper when creating a new collection - so you don't need to put the configs anywhere on the Solr boxes themselves. It's not

Re: solr 5 leaving tomcat, will I be the only one fearing about this?

On 10/10/2016 6:59 AM, Aristedes Maniatis wrote: > We also use com.vividsolutions.jts.geom so we need to add this jar > somewhere. The only places that seem to work are inside the Jetty > installation because that's where the classloader will find it. > ${solr.installation.dir}/server/lib or into

Re: solr 5 leaving tomcat, will I be the only one fearing about this?

Hi Shalin Thanks for your reply. On 10/10/16 3:28pm, Shalin Shekhar Mangar wrote: > As far as configuration is concerned -- everything Solr specific goes to > zookeeper. The solr.xml can also be put into zookeeper. JNDI is not > supported -- can you explain why you need it? Where do I put the

Re: solr 5 leaving tomcat, will I be the only one fearing about this?

As far as configuration is concerned -- everything Solr specific goes to zookeeper. The solr.xml can also be put into zookeeper. JNDI is not supported -- can you explain why you need it? Can cluster properties solve the problem? or replica properties? Both of those can go into zookeeper.

Re: solr 5 leaving tomcat, will I be the only one fearing about this?

Although I don't like docker, I do make heavy use of saltstack with jails plus ZFS snapshots to shipping virtual machines around. Docker is mostly just a reinvention of BSD/Solaris jails/zones. You might prefer docker's own custom dockerfile language and I prefer python with salt. But

Re: solr 5 leaving tomcat, will I be the only one fearing about this?

If you can, switch to Docker (https://hub.docker.com/_/solr/). It's a pain to get everything going the right way, but once it's running you get a lot of stuff for free: * Deployment, scaling etc. is all taken care of by the Docker ecosystem * Testing is a breeze. Need a clean Solr instance to run

Re: solr 5 leaving tomcat, will I be the only one fearing about this?

On 9/10/16 11:11am, Aristedes Maniatis wrote: > * deployment is also scattered: > - Solr platform specific package manager (pkg in FreeBSD in my case, which > I've had to write myself since it didn't exist) > - updating config files above > - writing custom scripts to push Zookeeper

Re: solr 5 leaving tomcat, will I be the only one fearing about this?

On 9/10/16 2:09am, Shawn Heisey wrote: > One of the historical challenges on this mailing list is that we were > rarely aware of what steps the user had taken to install or start Solr, > and we had to support pretty much any scenario. Since 5.0, the number > of supported ways to deploy and start

Re: solr 5 leaving tomcat, will I be the only one fearing about this?

On 10/7/2016 5:13 PM, Renee Sun wrote: > I just read through the following link Shawn shared in his reply: > https://wiki.apache.org/solr/WhyNoWar > > While the following statement is true: > > "Supporting a single set of binary bits is FAR easier than worrying > about what kind of customized

Re: solr 5 leaving tomcat, will I be the only one fearing about this?

Chegg uses a servlet filter to collect metrics on each request and forward them to Graphite and New Relic. We can configure that because we have hooks into the webapp config. This works with 4.10.4. We haven’t tried it with a later version, but it could be a blocker for upgrading. Our SLA

Re: solr 5 leaving tomcat, will I be the only one fearing about this?

I think it just means they won't officially support deploying war to tomcat or other container. make sense to me if I was in charge of solr, I would just support jetty, predictable with a single configuration. I wouldn't want to spent countless hrs supporting various configurations. Instead use

Re: solr 5 leaving tomcat, will I be the only one fearing about this?

I just read through the following link Shawn shared in his reply: https://wiki.apache.org/solr/WhyNoWar While the following statement is true: "Supporting a single set of binary bits is FAR easier than worrying about what kind of customized environment the user has chosen for their

Re: solr 5 leaving tomcat, will I be the only one fearing about this?

Rajesh was right on Renee -- the only big concern might be if that other code is tightly-coupled to Tomcat or to other things which *must* have Tomcat. But it sounds to me as if your multi-lingual processors - if they just work with Solr/Tomcat - out to "just work" with Solr/Jetty - or work with

Re: solr 5 leaving tomcat, will I be the only one fearing about this?

Thanks everyone, I think this is very helpful... I will post more specific questions once we start to get more familiar with solr 6. -- View this message in context: http://lucene.472066.n3.nabble.com/solr-5-leaving-tomcat-will-I-be-the-only-one-fearing-about-this-tp4300065p4300253.html Sent

Re: solr 5 leaving tomcat, will I be the only one fearing about this?

On 10/7/2016 10:33 AM, Renee Sun wrote: > In our production, we have cloud based big data indexing using Solr for many > years. We have developed lots business related logic/component deployed as > webapps working seamlessly with solr. > > I will give you a simple example, we purchased

Re: solr 5 leaving tomcat, will I be the only one fearing about this?

Renee, I dont understand what would be the difficulties of putting your 3rd party distributions in some contrib folders and import them in your solr configs and your processors should get loaded using solr class loader. we have used our custom based synonym processor putting the jar in contrib

Re: solr 5 leaving tomcat, will I be the only one fearing about this?

I won't speak for the committers, but I'm guessing you won't find a lot of support for the idea of continuing to provide a WAR file with the standard SOLR releases... I feel for you and your situation however - I've had to wrestle with a number of situations where a somewhat monolithic

Re: solr 5 leaving tomcat, will I be the only one fearing about this?

Thanks ... but that is an extremely simplified situation. We are not just looking for Solr as a new tool to start using it. In our production, we have cloud based big data indexing using Solr for many years. We have developed lots business related logic/component deployed as webapps working

Re: solr 5 leaving tomcat, will I be the only one fearing about this?

To give an exanmple: While you earlier would do some thing like Download and install Tomcat (or some other servlet container) Setup Tomcat as a service Download and unpack Solr Create a SOLR_HOME folder with correct content copy solr.war into tomcat/webapps set

Re: solr 5 leaving tomcat, will I be the only one fearing about this?

Treat Solr as a blackbox standalone database. Your MySQL is running standalone, right? And try to go to Solr 6, if you can. 5 is not latest anymore and there had been lots of scaling improvements in 6. Regards, Alex On 7 Oct 2016 5:02 AM, "Renee Sun" wrote: > need