UltipaDocs
Products
Solutions
Resources
Company
Start Free Trial
UltipaDocs
Start Free Trial
    • Install Ultipa
    • Install Ultipa Manager
  • Deployment with Kubernetes
  • Standalone Mode
  • License
    • Meta Servers
    • Shard Servers
    • HDC Servers
    • Vector Servers
    • Server Statistics
    • Privilege
    • Role (Policy)
    • User
    • Resource Group
  • Configuration
  • Monitoring
  • Security
  • Backup and Restore
  • Auto-Sharding Rebalancing
  • Change Data Capture (CDC)
  1. Docs
  2. /
  3. Operations & Maintenance

Standalone Mode

Overview

Standalone mode is a simplified deployment mode that embeds the Shard Server into the Name Server process. Instead of running three separate processes (Meta Server, Shard Server, and Name Server), standalone mode requires only two processes (Meta Server and Name Server).

This mode is suitable for:

  • Development and testing environments
  • Single-machine deployments
  • Resource-constrained environments
  • Quick prototyping
NOTE

Standalone mode is not recommended for production environments as it lacks shard-level fault isolation and horizontal scaling capabilities.

Comparison with Standard Mode

Feature
Standard ModeStandalone Mode
Processes requiredMeta Server + Shard Server + Name ServerMeta Server + Name Server
Configuration complexityMultiple server configsName Server config only
Resource usageHigher (multiple processes)Lower (merged processes)
Use caseProduction, distributedDevelopment, single-machine

Configuration

Add the [Standalone] section to name-server.config:

Ini
[Standalone]
enabled = true
shard_id = 1
data_path = /data/ultipa/shard
resource_path = /data/ultipa/resource
Parameter
DefaultDescription
enabledfalseEnables or disables standalone mode.
shard_id1Unique identifier for the embedded shard.
data_path(empty)Shard data storage path. Uses Server.data_path if empty.
resource_path(empty)Resource file path (e.g., full-text search dictionaries). Uses data_path if empty.

Full Configuration Example

Ini
[Server]
addr = 0.0.0.0:60061
private_addr = 127.0.0.1:60161
id = 1
meta_server_addrs = 127.0.0.1:50061
data_path = /data/ultipa
worker_num = 10
authorized = true

[Log]
level = 3
stdout = true

[Standalone]
enabled = true
shard_id = 1
data_path = /data/ultipa/shard
resource_path = /data/ultipa/resource

Starting

Using the Startup Script

Bash
cd /opt/ultipa
./start_standalone.sh

The script automatically copies the standalone configuration template, creates necessary data directories, starts Meta Server and Name Server, and checks process status.

Manual Startup

Bash
# Copy standalone config template
cp config/name-server-standalone.config config/name-server.config

# Start Meta Server
./meta-server &
sleep 3

# Start Name Server (with embedded shard)
./name-server &

Limitations

  • Only supports engine_type=default. Other engine types are not compatible with standalone mode.
  • No shard-level fault isolation.
  • No horizontal scaling.
  • Migrating from standalone mode to standard mode requires data export and re-import.