Red Hat Linux

CrateDB maintains the official RPM repositories for:

Both of these work with RedHat Enterprise Linux, CentOS, and Scientific Linux.

Table of contents

Configure YUM

All CrateDB packages are signed with GPG.

To get started, you must import the CrateDB public key, like so:

sh$ sudo rpm --import

You must then install the CrateDB repository definition.

For Red Hat Enterprise Linux, run:

sh$ sudo rpm -Uvh

For CrateDB versions < 4.2.0, run:

sh$ sudo rpm -Uvh

The above commands will create the /etc/yum.repos.d/crate.repo configuration file.

CrateDB provides a stable and a testing release channel. At this point, you should select which one you wish to use.

By default, YUM (Red Hat’s package manager) will use the stable repository. This is because the testing repository’s configuration marks it as disabled.

If you would like to enable to testing repository, open the crate.repo file and set enabled=1 under the [crate-testing] section.

Install CrateDB

With everything set up, you can install CrateDB, like so:

yum install crate

CrateDB is now installed, but not running.

Running and controlling CrateDB

With Red Hat Enterprise Linux, you can control the crate service like so:

sh$ sudo systemctl COMMAND crate

Here, replace COMMAND with start, stop, restart, status and so on.

After you run the appropriate command with the start argument, the crate service should be up-and-running.

You should be able to access it by visiting:


See also

If you’re new to CrateDB, check out our our first use documentation.


Be sure to read the guide to rolling upgrades and full restart upgrades before attempting to upgrade a running cluster.


Configuration files

The main CrateDB configuration files are located in the /etc/crate directory.


The CrateDB startup script sources environment variables from the /etc/sysconfig/crate file.

You can use this mechanism to configure CrateDB.

Here’s one example:

# Heap Size (defaults to 256m min, 1g max)

# Maximum number of open files, defaults to 65535.

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

# Additional Java OPTS

# Force the JVM to use IPv4 stack

Customized setups

A full list of package files can be obtained with this command:

sh$ rpm -ql crate

If you want to deviate from the way that the crate package integrates with your system, we recommend that you go with a basic tarball installation.


How helpful was this page?