---
name: "kumostat"
section: "1"
platform: "linux"
package: "kumofs"
version: "0.4.13-6.1"
release: "Debian 8 (Jessie)"
platforms: ["linux"]
url: "https://new.carta.tech/kumostat"
---

# kumostat(1)

get kumofs status

## NAME

kumostat - get kumofs status

## SYNOPSIS

kumostat server-address\[:port=19800\] command

kumostat -m manager-address\[:port=19700\] command

## DESCRIPTION

Get status from Server node.

## COMMANDS

- **pid**

  get pid of server process

- **uptime**

  get uptime

- **time**

  get UNIX time

- **version**

  get version

- **cmd\_get**

  get total number of processed get requests

- **cmd\_set**

  get total number of processed set requests

- **cmd\_delete**

  get total number of processed delete requests

- **items**

  get number of stored items

- **rhs**

  get rhs (routing table for Get)

- **whs**

  get whs (routing table for Set/Delete)

- **hscheck**

  check if rhs == whs

- **set\_delay**

  maximize throughput at the expense of latency

- **unset\_delay**

  maximize throughput at the expense of latency

## DELAY MODE

If the delay mode is enabled, req/sec throughput is maximized at the expense of latency. This mode actually disables TCP\_NODELAY option of all sockets. The practice of this feature is as following:

\- run some scripts that watches load of the kumo-server. (see source code of kumotop)

\- if the load of kumo-server becomes high, enable delay mode by **kumostat set\_delay** command.

\- if the load of kumo-server becomes low, disable delay mode by **kumostat unset\_delay** command.

## EXAMPLE

$ kumostat svr1 items

$ kumotop -m mgr1 hscheck

## SEE ALSO

[kumo-server(1)](/kumo-server/1.md).