OpenTSDB in Docker

This is Mesos ready OpenTSDB TSD server docker image. Tags are corresponding to OpenTSDB releases.

Configuration

Containers from this image are fully configured with environment variables. To convert OpenTSDB configuration property name to env variable name, you should:

Add prefix TSD_CONF_
Replace . with __

You can also make variable name upper case. An example:

tsd.network.async_io becomes TSD_CONF_tsd__network__async_io

To see available configuration properties, take a look at config options.

JVM options

OpenTSDB sets JVMARGS=""-enableassertions -enablesystemassertions". You can change this env variable to tune JVM. It's a good idea to set heap size limit with -Xmx option:

JVMARGS="-Xms2g -Xmx2g -enableassertions -enablesystemassertions"

Cache cleanup

OpenTSDB does not support automatic cache cleanup, but cache directory can become quite big for intense users. To fix this problem, this image removes old cache entries from cache directory. There are two environment variables that control cleanup process:

TSD_CACHE_CLEANUP_INTERVAL interval between cleanups in seconds
TSD_CACHE_MAX_AGE_MINUTES max age of cache files in minutes

TSD telemetry

Setting TSD_TELEMETRY_INTERVAL to some positive value enables feeding TSD metrics back to OpenTSDB. Value for host tag will be taken from MESOS_TASK_ID if possible or from hostname -s output.

Log level

The following log level env variables exist:

TSD_ROOT_LOG_LEVEL to set root log level, defaults to INFO.
TSD_QUERY_LOG_LEVEL to set query log level, defaults to INFO.

Note that default root log level is quite verbose and you'll probably want to change it to WARN for production. Setting query log level to WARN or higher effectively disables query logging.

Running ad-hoc OpenTSDB commands

If you supply any args to the image, they will be passed to tsdb executable. This way you could run fsck:

docker run [...] cloudflare/opentsdb:2.2.0 fsck --full-scan --fix-all --compact

Config is is still picked up from environment in this case.

Security

After initial configuration container drops root privileges and runs with dedicated opentsdb user.

Example marathon configuration

{
  "id": "/opentsdb/tsd",
  "cpus": 1,
  "instances": 1,
  "mem": 3072,
  "ports": [0],
  "container": {
    "type": "DOCKER",
    "docker": {
      "image": "cloudflare/opentsdb:2.2.0",
      "network": "HOST"
    }
  },
  "env": {
    "VMARGS": "-Xms2g -Xmx2g -enableassertions -enablesystemassertions",
    "TSD_CONF_tsd__storage__hbase__zk_quorum": "zk:2181"
  },
  "healthChecks": [
    {
      "protocol": "HTTP",
      "path": "/api/version",
      "gracePeriodSeconds": 15,
      "intervalSeconds": 10,
      "timeoutSeconds": 10,
      "maxConsecutiveFailures": 3
    }
  ]
}

This image is also zoidberg and zoidberg-nginx friendly.

License

MIT

bjozet/docker-opentsdb