CurvineCurvine

Standalone Mode

This chapter describes how to bring up a local Curvine cluster from build/dist and what the bundled helper scripts actually do.

Start the Local Cluster

Build or unpack the distribution first, then run from build/dist:

cd build/dist
./bin/restart-all.sh

restart-all.sh performs these actions:

  1. Unmount /curvine-fuse with lazy umount if it is still mounted.
  2. Kill any previous Curvine processes.
  3. Start curvine-master.
  4. Start curvine-worker.
  5. Start curvine-transfer when [transfer].enabled = true.
  6. Start curvine-fuse.

It does not start a separate webui process. Web pages are served on the service web ports using the bundled webui/ assets.

If you compiled Curvine inside a Docker container, run it in the same environment unless you are sure the host runtime dependencies match the build environment.

Logs and PID Files

Service lifecycle management goes through bin/launch-process.sh.

  • Logs are written to logs/master.out, logs/worker.out, and logs/fuse.out
  • PID files are written at the Curvine home directory root as master.pid, worker.pid, and fuse.pid

Verify Status

Check the cluster summary:

./bin/cv report

Check that FUSE is mounted:

mount | grep curvine-fuse
ls -la /curvine-fuse

Web Endpoints

  • Master web endpoint: http://<host>:9001
  • Worker web endpoint: http://<host>:9002
  • FUSE web endpoint: http://<host>:9003

If you run inside Docker, use --network host or map at least 8995, 8996, 8997, 9001, 9002, and 9003.

Alternative Helper Script

The distribution also includes bin/local-cluster.sh, which manages the server-side processes and starts Transfer when enabled, but does not mount FUSE:

./bin/local-cluster.sh start
./bin/local-cluster.sh status
./bin/local-cluster.sh stop

Use restart-all.sh when you want FUSE mounted as part of the local setup. Use local-cluster.sh when you only need the server-side processes.

On this page

Start the Local ClusterLogs and PID FilesVerify StatusWeb EndpointsAlternative Helper Script