Please use the form below to provide your feedback. Because your feedback is valuable to us, the information you submit in this form is recorded in our issue tracking system (JIRA), which is publicly available. You can track the status of your feedback using the ticket number displayed in the dialog once you submit the form.

A newer version of this documentation is available.

View Latest

Install Couchbase Server on SUSE Linux Enterprise Server

      +
      Couchbase Server can be installed on SUSE Linux Enterprise Server for production and development use-cases.

      Use the instructions on this page to install Couchbase Server on SUSE Linux Enterprise using Couchbase-provided RPM packages. The instructions support both Enterprise and Community editions.

      If you’re upgrading an existing installation of Couchbase Server, refer to Upgrading Couchbase Server.

      Before You Install

      Couchbase Server works out-of-the-box with most OS configurations. However, the procedures on this page assume the following:

      • Your system meets the minimum requirements and that your operating system version is supported.

      • You’re working from a clean system and that you’ve uninstalled any previous versions of Couchbase Server.

        If you’re upgrading an existing installation of Couchbase Server, refer to Upgrading Couchbase Server.

      • Your system supports the requisite number of threads to run Couchbase Server. You can check (and optionally change) the default thread limit using the following steps:

        1. Check the default thread limit by running the following command from the shell:

          sudo systemctl show --property DefaultTasksMax

        2. If the value returned is less than 65535, then edit the file: etc/systemd/system.conf and set DefaultTasksMax to 65535.

          The system.conf file may have read-only permissions set; if this is the case, then use the chmod command to set the user permissions to writeable.

        3. From the command shell, execute the following command to load the new setting:

          sudo systemctl daemon-reload

      For production deployments, make sure to follow the deployment guidelines so that your systems and environment are properly sized and configured before installation.

      Basic Installation

      You must be logged in as root (superuser) or use sudo to run the installation commands.

      Install Using RPM Package

      Install Couchbase Server on SUSE Linux Enterprise using a full RPM package provided by Couchbase.

      1. Download the appropriate package from the Couchbase downloads page.

      2. Install Couchbase Server.

        sudo rpm -i package-name.rpm

        Once installation is complete, Couchbase Server will start automatically (and will continue to start automatically at run levels 2, 3, 4, and 5, and explicitly shut down at run levels 0, 1, and 6). You can use the systemctl command (service on older operating systems) to start and stop the Couchbase Server service, as well as check the current status. Refer to Couchbase Server Startup and Shutdown for more information.

      3. Open a web browser and access the Couchbase Web Console to verify that the installation was successful and the node is available.

      Installing as Non-Root

      Non-root installation is performed identically for all supported Linux distributions, including SUSE Linux Enterprise Server. For instructions, see Non-Root Install and Upgrade.

      Next Steps

      Following installation and start-up of Couchbase Server, a node must be initialized and provisioned.

      • If it is the first node in a deployment, initialization and provisioning happens all at once when you create a cluster of one.

        Refer to Create a Cluster

      • If you already have an existing cluster, the node is initialized and provisioned when you add it to the cluster.

        Refer to Add a Node and Rebalance

      • Optionally, initialization can be performed explicitly and independently of provisioning, as a prior process, in order to establish certain configurations, such as custom disk-paths.

        Refer to Initialize a Node