Search K
Appearance
Palomar: GeoDB
The GeoDB contains the metadata used by Palomar to route users and groups, maintain the platform health and performance, and allow autodiscovery and bootstrapping of nodes in the platform.
Proxies, Backends, and Controllers access GeoDB to perform these actions.
GeoDB requires a server that supports CQL version 4 or higher. GeoDB otherwise shares the same Cassandra requirements as Dictmap.
Key Features of GeoDB
GeoDB organizes cluster state data into several object types:
Site
A site contains multiple Backends.
Backend
A Dovecot Backends entity with status, statistics and load factor.
Family Features
A set of Cluster Controllers features that can be enabled, disabled, or DryRun (enabled for logging purposes only).
Dependency on Cassandra
GeoDB depends on Cassandra as its primary data store. However, ScyllaDB has also been tested and confirmed to be compatible with GeoDB, offering users an alternative.
Deployment Solutions for Cassandra
Manual
It is recommended to install your own Cassandra cluster with your specific business requirements and use it for both Dovecot fs-dictmap and Cluster Controller.
These settings should be set:
Kubernetes
Cluster Controller's Kubernetes deployment offers a minimal deployment of either Cassandra or ScyllaDB databases.
WARNING
It is not recommended to use this for production use, as it is a single node installation without replication or high availability considerations.
To disable this managed database deployment set database.enabled = false in the helm variables.
Docker Compose
The Docker-compose deployment method does not support Cassandra and it is expected that a running Cassandra is available.
Cassandra Keyspace for GeoDB
The keyspace used by Controller is set in CASSANDRA_KEYSPACE.
You normally don't need to create the keyspace beforehand because deployment automation should take care of that.
If you've opted out of automatic database initialization, then you'll need to create the keyspace and all the tables needed for Controller to work.