Deploy for Development
You can deploy Redpanda using well-known configuration properties optimized for a development or test environment. This configuration uses less system resources and simplifies setup, but it’s not suitable for a production deployment. For example, in development mode, the default group_topic_partitions
is 3, and the default storage_min_free_bytes
is 1 GiB. In production mode, the default group_topic_partitions
is 16, and the default storage_min_free_bytes
is 5 GiB.
Development mode bypasses See Deploy for Production to deploy for a production environment. See Redpanda Quickstart to try out Redpanda in Docker. |
Prerequisites
Make sure you meet the hardware and software requirements.
Install Redpanda
Install Redpanda on each system you want to be part of your cluster. There are binaries available for Fedora/RedHat or Debian systems.
You can also install Redpanda using an Ansible playbook.
-
Fedora/RedHat
-
Debian/Ubuntu
curl -1sLf 'https://dl.redpanda.com/nzc4ZYQK3WRGd9sy/redpanda/cfg/setup/bash.rpm.sh' | \
sudo -E bash && sudo yum install redpanda -y
curl -1sLf 'https://dl.redpanda.com/nzc4ZYQK3WRGd9sy/redpanda/cfg/setup/bash.deb.sh' | \
sudo -E bash && sudo apt install redpanda -y
Install Redpanda Console
Redpanda Console is a developer-friendly web UI for managing and debugging your Redpanda cluster and your applications. Install Redpanda Console alongside a Redpanda cluster.
For each new release, Redpanda compiles the Redpanda Console to a single binary for Linux, macOS, and Windows. You can find the binaries in the attachments of each release on GitHub.
-
Fedora/RedHat
-
Debian/Ubuntu
curl -1sLf 'https://dl.redpanda.com/nzc4ZYQK3WRGd9sy/redpanda/cfg/setup/bash.rpm.sh' | \
sudo -E bash && sudo yum install redpanda-console -y
curl -1sLf 'https://dl.redpanda.com/nzc4ZYQK3WRGd9sy/redpanda/cfg/setup/bash.deb.sh' | \
sudo -E bash && sudo apt-get install redpanda-console -y
Start Redpanda
Configure Redpanda using the rpk redpanda config bootstrap
command, then start Redpanda:
sudo rpk redpanda config bootstrap --self <private-ip> --ips <seed-server-ips> && \
sudo rpk redpanda config set redpanda.empty_seed_starts_cluster false && \
sudo systemctl start redpanda
-
The
--self
flag tells Redpanda the interface address to bind to. Usually this is its private IP. -
The
--ips
flag lists all the seed servers in the cluster, including the one being started. Seed servers correspond to theseed_servers
property inredpanda.yaml
.-
The
--ips
flag must be set identically (with nodes listed in identical order) on each node. -
Do not run
sudo rpk redpanda tune all
on development deployments.
-
When a Redpanda cluster starts, it instantiates a controller Raft group with all the seed servers that are specified in the --ips
flag. After all seed servers complete their startup procedure and become accessible, the cluster is then available. After that, non-seed servers start up and are added to the cluster.
|
Start Redpanda Console
-
Start Redpanda Console:
sudo systemctl start redpanda-console
-
Make sure that Redpanda Console is active and running:
sudo systemctl status redpanda-console
Verify the installation
To verify that the Redpanda cluster is up and running, use rpk
to get information about the cluster:
rpk cluster info
To create a topic:
rpk topic create panda
Next steps
-
If clients connect from a different subnet, see Configure Listeners.
-
Observability is essential. See Monitor Redpanda.