1. Installation#

1.1. System Requirements#

QuasarDB runs on several architectures, and requirements differ depending on which architecture you’re targeting.

As a general note, it is strongly advised to have a homogenous hardware configuration within a cluster.

1.1.1. x64 build#

Our main build is optimized for modern CPUs.

  • An Intel Haswell or better microarchitecture (AMD Bulldozer or better)

  • End-to-end ECC memory highly recommended (motherboard, CPU and memory)

  • At least 512 MB of RAM

  • At least 1 GiB of disk

1.1.2. Core2 build#

Our Core2 build is optimized for older CPUs, at a slight cost of performance, you will need it for architectures older than Haswell.

  • An Intel Core or better microarchitecture

  • End-to-end ECC memory highly recommended (motherboard, CPU and memory)

  • At least 512 MB of RAM

  • At least 1 GiB of disk

1.1.3. ARM64 build#

Note

Our ARM builds may need special tuning to give you the best experience. Please contact your Solution Architect for configuration recommendations.

  • ARM64 architecture

  • At least 512 MB of RAM

  • At least 1 GiB of disk

1.2. Installation#

The installation instruction may differ, depending on the operating system you are installing on.

Available images

QuasarDB hosts various Docker images on the official docker hub:

Image

Description

Tags

Core2

bureau14/qdb

QuasarDB daemon

  1. latest

  2. stable

  3. beta

  4. 3.13.7

  5. 3.13

  6. 3.14.0

  7. 3.14

  1. latest-core2

  2. stable-core2

  3. beta-core2

  4. 3.13.7-core2

  5. 3.13-core2

  6. 3.14.0-core2

  7. 3.14-core2

bureau14/qdbsh

QuasarDB shell

  1. latest

  2. stable

  3. beta

  4. 3.13.7

  5. 3.13

  6. 3.14.0

  7. 3.14

  1. latest-core2

  2. stable-core2

  3. beta-core2

  4. 3.13.7-core2

  5. 3.13-core2

  6. 3.14.0-core2

  7. 3.14-core2

bureau14/qdb-replicate

QuasarDB replication tool

  1. latest

  2. stable

  3. beta

  4. 3.13.7

  5. 3.13

  6. 3.14.0

  7. 3.14

  1. latest-core2

  2. stable-core2

  3. beta-core2

  4. 3.13.7-core2

  5. 3.13-core2

  6. 3.14.0-core2

  7. 3.14-core2

bureau14/qdb-dashboard

QuasarDB dashboard

  1. latest

  2. stable

  3. beta

  4. 3.13.7

  5. 3.13

  6. 3.14.0

  7. 3.14

N/A

bureau14/qdb-kinesis-connector

QuasarDB dashboard

  1. latest

  2. stable

  3. beta

  4. 3.13.7

  5. 3.13

  6. 3.14.0

  7. 3.14

N/A

Available tags

All images follow the following tag format:

Tag

Description

QuasarDB version

latest

Latest officially supported image

3.13.7

beta

Latest beta version

3.13.7

stable

Latest stable version

3.14.0

3.14

Latest version in the 3.14 branch.

3.14.0

3.13

Latest version in the 3.13 branch.

3.13.7

*-core2

Core2 variant of a build. Use this version if you’re getting CPU instruction errors on the main branch.

E.g. 3.13.7-core2, 3.14.0-core2, etc.

For each of these images, these are the currently supported tags and features:

Example usage

You can use these images to launch a QuasarDB daemon as follows:

$ docker run -d  --name qdb-server bureau14/qdb
$ docker run -d -p 40000:40000 --link qdb-server:qdb-server -e QDB_URI=qdb://qdb-server:2836 bureau14/qdb-dashboard

You can now navigate with your browser to http://localhost:40000/#anonymous to open the dashboard.

You can also connect with the QuasarDB shell as follows:

$ docker run -ti --link qdb-server:qdb-server bureau14/qdbsh --cluster qdb://qdb-server:2836
quasardb shell version 3.4.3 build 3a2c17b 2019-10-15 07:56:15 +0000
Copyright (c) 2009-2019 quasardb. All rights reserved.

Need some help? Check out our documentation here:  https://doc.quasardb.net

qdbsh >

Environment variables

The QuasarDB docker containers provide several environment variables you can use to configure the most common settings. For more information, see the docker configuration manual.

1.3. Next steps#

If everything went successfully, you now have a ready-to-use QuasarDB installation. You can continue reading with the following chapters, depending on what you’re trying to achieve:

  • If you’re a developer or data scientist looking to write code that interacts with QuasarDB, please continue with our API tutorial.

  • If you’re a systems administrator looking to configure and tune QuasarDB, please continue with our configuration manual.

  • If you’re a systems administrator looking for more information around common operational tasks, please continue with our maintenance manual.