Package Details: solr 8.1.1-1

Git Clone URL: (read-only)
Package Base: solr
Description: Popular, blazing fast open source enterprise search platform from the Apache Lucene project
Upstream URL:
Licenses: Apache
Submitter: mtorromeo
Maintainer: sanduhrs
Last Packager: sanduhrs
Votes: 43
Popularity: 0.016397
First Submitted: 2011-05-23 09:43
Last Updated: 2019-07-18 11:42

Latest Comments

1 2 3 4 5 6 Next › Last »

gdkags commented on 2019-02-15 11:18

request to add /opt/solr/bin/ to the backup files. AFAIK this is were the heap sizes and zookeeper information are normally configured.

edit: to circumvent losing the setting, you can as well use an override for the EnvironmentFile in /etc/systemd/system/solr.service.d/override.conf:


Contents of the /etc/conf.d/solr.env could be:


mellow_yellow commented on 2018-11-06 11:27

Just to add details to the previous comments, you can adjust service and memory settings like this:

1) Override this package's solr.service by creating your own, as root, based on the original packaging: Example: sudo vi /etc/systemd/system/solr.service

Description=Solr full text search engine

ExecStart=/opt/solr/bin/solr start -f


2) Reload units:

sudo systemctl daemon-reload
sudo systemctl restart solr.service

3) Check if it worked. Example: sudo journalctl -b -u solr.service

4) Optionally, give solr more memory. Example: sudo vi /opt/solr/bin/ Set appropriate values, like SOLR_HEAP="6144m" Check if it worked: http://localhost:8983/solr/#/ -- see JVM-Memory

crt commented on 2018-06-29 21:51

Note that if Solr reports warnings when starting the Solr systemd service file similar to

*** [WARN] *** Your open file limit is currently 1024. *** [WARN] ***  Your Max Processes Limit is currently 1932. It should be set to 65000 to avoid operational disruption.

You need to include some ulimit values in /etc/systemd/systemd/solr.service file so the warnings go away.


The other different ulimit directives can be found in the systemd.exec man page if needed.

graphicmist commented on 2017-01-29 14:23

6.4.0 is out

trichards commented on 2016-09-09 17:06

@webdawg: There's no particular reason for the `java-environment-common` dependency, other than the initial packager having made it that way. You're right, though -- the package should depend on an actual Java runtime and not just the common files. Along with the 6.2.0 version upgrade, I've changed the package to depend on `java-runtime-headless>=8` which should allow you to pick from a wide range of JREs/JDKs.

webdawg commented on 2016-09-04 20:13

So solr looks like it requires java, and it pulls in java-environment-common, but when I install it it does not install java, what is the deal? Why does not java-environment-common pull in java or ask you which you want to install?

Is their any reason you did not pull in a specific java, is it just for flexibility?

webdawg commented on 2016-09-04 19:07

6.2.0 is out

jamesan commented on 2015-07-11 15:38

I've created a solr5 package that installs Solr 5.2.1. I've tried to break up the package according to the FHS with symlinks from the package's webapp directory to the various

It runs out of the box with either the systemd service unit or a /usr/bin/solr script that specifies the correct FHS paths for the various components.

grimsock commented on 2015-05-27 10:09

For now updated to 4.10.4.

nineinchnick commented on 2015-03-18 08:52

Maybe this package should be copied as solr4 (and updated to 4.10.4) and solr should be at version 5.0?