System Requirements

To deploy NuoDB in a production environment, you must deploy on one of the following supported Linux platforms. To develop or test/evaluate NuoDB, you can use any of the following platforms:

Platform Requirements Support Level

Linux (x64)

Red Hat Enterprise Linux (RHEL) / CentOS 7.7 and later

Red Hat Enterprise Linux (RHEL) 8.x

Production

Windows (x64)

Windows 10

Development / Test

Java Requirements

The NuoDB server and the NuoDB JDBC client software requires the Java Runtime Environment (JRE) installed on the system. The following Java versions are supported:

  • Java 8

  • Java 11

  • Java 17

On Linux, install either the JDK or the JRE.

On 64-bit Windows, the 64-bit JRE must be installed. See Installing NuoDB on Windows for details about a required Windows update, which you might or might not already have.

Red Hat Enterprise Linux (RHEL) Prerequisites

The ncurses-compat-libs library is required to install NuoDB. ncurses is used by nuosql to implement command line editing capabilities. Please check for its existence prior to your NuoDB install. If it is not installed, please follow your OS installation instructions to install this library. For example, if using the yum package installer, run:

sudo yum install ncurses-compat-libs

TLS requirements

Domain and database management in NuoDB deployments is handled by NuoDB Admin (nuoadmin). NuoDB Admin supports TLS encryption for all processes in the domain.

To use NuoDB Admin with TLS encryption, TLS must be enabled. For more information, see Enabling TLS Encryption.

To use NuoDB Admin without TLS encryption, see Managing TLS Security.

LDAP Requirements

LDAP requirements on Linux platforms are as follows:

  • On Ubuntu:

    $ sudo apt-get update
    $ sudo apt-get install ldap-utils
  • On Red Hat / CentOS Linux:

    sudo yum install openldap-clients

On Windows, there are no additional requirements.

Networking

NuoDB supports TCP over either IPv4 or IPv6.

  • x86_64 dual core CPU, 1.6GHz

  • 4GB memory

For Linux, it is highly recommended that your file system support fallocate(). The fallocate() system call is supported by the following:

  • XFS (since Linux kernel 2.6.38)

  • ext4 (since Linux kernel 3.0)

  • ZFS ((since ZFS on Linux kernel 0.6.4)

  • Btrfs (since Linux kernel 3.7)

  • tmpfs (since Linux kernel 3.5)

Network File System (NFS) storage is not supported for archive and journal locations.
The ext2 and ext3 file systems are not supported.

Starting in NuoDB Release 3.0, NuoDB on Linux supports Nehalem or later processors only. This change was implemented to take advantage of compilation performance optimizations available in Nehalem and later processor models.

In order to determine if the machine processor on Linux is Nehalem or later run the following command:

grep sse4_2 /proc/cpuinfo | sort -u

If the command returns text output then the processor type is supported.

VMware VMOTION Considerations

If you are using VMotion to migrate NuoDB virtual machines between servers, NuoDB strongly recommends that you stop any running NuoDB process(es) within the virtual machine prior to migration, and restart the NuoDB process(es) after the migration. This is because VMotion can cause running NuoDB process(es) to stop unexpectedly. If VMotion is used while NuoDB processes are still running, you must check the status of the NuoDB processes after migration then manually restart any stopped processes when migration is complete.