Table of Contents
Exasol versions in the Google Cloud Platform Marketplace
Two different Exasol offerings are available via the Google Cloud Platform Marketplace.
We recommend reading the getting started guides before launching a database system.
We recommend setting up Exasol as cluster. This offers the following advantages:
- Scalability: easily scale out a cluster by adding additional nodes to process more data and to serve more concurrent users
- High availability: When a nodes failes the system automatically tries to repair this node or includes a standby node into the system (if a standby node was configured).
However, for small data sizes or evaluation purposes a single-node system might be be sufficient and appropriate.
Overview Deployment Manager Templates
We offer deployment manager templates for cluster and single node database deployment.
A template always consist of a resource-file and a parameter-file.
The resource-file (in jinja format) must not be changed as all the custom configuration is done in the parameter file. The parameter file itself holds a reference to the resource file.
A deployment is launched with the GCloud CLI where the parameter-file is referenced.
Overview of configuration parameters:
In the next section is a description of all parameters you might encounter in your parameter-file.
|publicIP||If set to true, public IP addresses are assignet to all instances|
|dbNodeCount||Number of cluster nodes|
|standbyNode||If the replication factor is > 1, then a concurrent standby node can take over the work from a failed node|
|dbSystemName||Name of the generated database|
|exasolPassword||Password for the exasol operations admin user (EXAoperation 'admin' user)|
|dbPassword||Password for the exasol database admin user (Exasol 'sys' user)|
|license||In case of a byol image an already aquired license can be pasted here as string|
|firewallRule||Restrict access to specific ip addresses (0.0.0.0/0 results in access from everywhere)|
|networkCidr||CIDR Block of the target network|
|subnetworkCidr||CIDR Block of target subnetwork|
|firstNodeIP||Counting upwards for the IPs of the data nodes (FirstDataNodeIP > LicenceServerIP)|
|zone||Target zone where instances and persistent disks are deployed into|
Required timezone for the DB (default Europe/Berlin)
VM Image from the Google Marketplace Solution
|dnsServer||e.g. 169.254.169.254 (Google Cloud internal DNS Server)|
|blockDeviceVolumeSizeGB||Devices size for data volume|
|blockDeviceCount||Number of storage volumes for each node|
Support, Troubleshooting & Software Updates
Exasol Analytic Database (Single Node and Cluster, Enterprise Support)
The Pay-as-you-go version of Exasol 6.1.2 that can be purchased via the Google Cloud Marketplace includes 24/7 incident management.
After registration the following services are available:
- This support offering is only valid for Exasol instances launched using the Google Cloud Platform Marketplace offering
- In order to be fully eligible for support you have to register (see below). The registration process may take some days.
- SLAs only apply after successfully completing the onboarding process.
- In case you need support before the registration process has been completed you may already use the "send support request" from below.
Register for Exasol PAYG support for Google Cloud Platform*
Enhanced Failover Capabilities
Before a spare node had to be running all the time to provide automatic fail-safety capabilities in case of a node failure.
Starting with 6.1 on Google Cloud Platform failover capabilities are also available if:
- no spare/standby node is configured
- a spare node was configured but suspended (not running)
Database System Documentation and Further Reading
If you just want to quickly find out how to load data from S3 and other sources into Exasol or how to connect Exasol to the most popular BI tools you should take a look the following guide: Getting Started
- SOL-354Getting issue details... STATUS describes how to perform backup and restore operations using S3 ( Additional information on enhanced S3 support can be found in - EXASOL-1752Getting issue details... STATUS and - EXASOL-1958Getting issue details... STATUS )
Recommendations for using Exasol on Google Cloud Platform
Recommended instance families: n1-standard, n1-highcpu, n1-highmem
Recommended storage: SSD persistend disk
Minimum size of main memory: 16 GB
Instance-integrated hard drives (ephemeral storage) are supported for test and evaluation purposes only, as data in the instance store is lost when the instance is stopped.
For production environments we recommend using high-available SSD persistend disk, as these provide maximum reliability and durability.