Currently our build automatically creates a debian package and an RPM package, which is available on the download page. The package itself does not have any dependencies, but you have to make sure that you installed a JDK.

Each package features a configuration file, which allows you to set the following parameters


The user to run as, defaults to elasticsearch


The group to run as, defaults to elasticsearch


The heap size to start with


The size of the new generation heap


The maximum size of the direct memory


Maximum number of open files, defaults to 65535


Maximum locked memory size. Set to "unlimited" if you use the bootstrap.mlockall option in elasticsearch.yml. You must also set ES_HEAP_SIZE.


Maximum number of memory map areas a process may have. If you use mmapfs as index store type, make sure this is set to a high value. For more information, check the linux kernel documentation about max_map_count. This is set via sysctl before starting elasticsearch. Defaults to 65535


Log directory, defaults to /var/log/elasticsearch


Data directory, defaults to /var/lib/elasticsearch


Work directory, defaults to /tmp/elasticsearch


Configuration file directory (which needs to include elasticsearch.yml and logging.yml files), defaults to /etc/elasticsearch


Path to configuration file, defaults to /etc/elasticsearch/elasticsearch.yml


Any additional java options you may want to apply. This may be useful, if you need to set the property, but do not want to change the elasticsearch.yml configuration file, because it is distributed via a provisioning system like puppet or chef. Example: ES_JAVA_OPTS=""


Configure restart on package upgrade, defaults to false. This means you will have to restart your elasticsearch instance after installing a package manually. The reason for this is to ensure, that upgrades in a cluster do not result in a continouos shard reallocation resulting in high network traffic and reducing the response times of your cluster.


The debian package ships with everything you need as it uses standard debian tools like update update-rc.d to define the runlevels it runs on. The init script is placed at /etc/init.d/elasticsearch is you would expect it. The configuration file is placed at /etc/default/elasticsearch.

Installing the oracle JDKedit

The usual recommendation is to run the Oracle JDK with elasticsearch. However Ubuntu and Debian only ship the OpenJDK due to license issues. You can easily install the oracle installer package though. In case you are missing the add-apt-repository command under Debian GNU/Linux, make sure have at least Debian Wheezy and the package python-software-properties installed

sudo add-apt-repository ppa:webupd8team/java
sudo apt-get update
sudo apt-get install oracle-java7-installer
java -version

The last command should verify a successful installation of the Oracle JDK.


RedHat based distributions are using chkconfig to enable and disable services. The init script is at /etc/init.d/elasticsearch, where as the configuration file is placed at /etc/sysconfig/elasticsearch.


SuSe does not use the chkconfig tool to register services, but rather systemd and its command /bin/systemctl to start and stop services. The configuration file is also placed at /etc/sysconfig/elasticsearch.

Also note that changing the MAX_MAP_COUNT setting in /etc/sysconfig/elasticsearch does not have any effect, you will have to change it in /usr/lib/sysctl.d/elasticsearch.conf in order to have it applied at startup.