Maintenance Notification:
On Friday May 3rd 2019 at 2pm CET we will conduct some maintenance. The following Service will not be available for about 1 hour:

Page tree


-

Table of Contents


Exasol versions in the Google Cloud Platform Marketplace

Two different Exasol offerings are available via the Google Cloud Platform Marketplace.

Pay-As-You-Go (PAYG)


  • Simply pay for what you use
  • Charged on an hourly basis
  • Billed through the Marketplace
  • This offering includes enterprise support with 24/7 incident management



Bring-Your-Own-License (BYOL)

  • Select this option if you already have a valid Exasol license for the selected configuration or if you plan to purchase a license.
  • The license file is required to operate this product


Advantages

    • License is portable across platforms
    • Perpetual or subscription licensing
    • Raw data based licensing

For more information please contact the Exasol sales team (Contact Form)


(info)  We recommend reading the getting started guides before launching a database system.


Getting started

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.

Exasol Cloud Deployment Wizard

The easiest way to configure and deploy an Exasol cluster or single node system is using our Cloud Deployment Wizard for public clouds. This tool will guide you through the sizing, configuration and deployment process. Internally it uses and parameterizes our standard Deployment Manager templates (see below). After having configured your cluster you can either download the preconfigured templates or directly open them in the Google Cloud Shell to proceed with the deployment process.

If you proceed with the Google Cloud Shell option you will be forwarded to the Cloud Shell and prompted for remaining parameters that need to be specified (gcp project, passwords etc). You have to confirm the configuration before the deployment process is being started.


Google Cloud Marketplace Solutions

However, you can also easily launch Exasol through the GCP Marketplace solutions (PAYG and BYOL)

Using these solutions you can easily deploy a cluster database or a single node database. The network infrastructure is created completely from scratch in this case.

If you want to deploy a cluster into an existing network infrastructure then we recommend using the Deployment Wizard .

Cluster deployment

By default the checkbox for Cluster deployment is selected.

A cluster always consists of a management node and at least one more data/compute nodes.

In addition you can add standby nodes to guarantee high availability (see more in section Enhanced Failover Capabilities).

Single Node Deployment

If you would like to deploy a single node sytem please select the checkbox for "Single node deployment" in the configuration form and uncheck "Cluster deployment" in the deployment form.

Some details on sizing

 Click here for more information on sizing

(More details on sizing can be found in the documentation portal: https://docs.exasol.com/administration/on-premise/sizing.htm )

A good rule of thumb is that the RAM size of the selected instance should correspond to approximately 10% - 15 % of your raw data.

As a rule of thumb the disk space for a single node should correspond to approximately 0.7x of the amount of raw data that should be managed by the node (equivalent to 7 times the amount of main memory of the node) .
As a cluster always redundantly stores the data for high availability reasons, cluster nodes need more disk space compared to single node systems. As a rule of thumb the disk storage for a cluster node should correspond to 12x of amount of main memory of that node (equivalently: 1,2x of the amount of raw data that should be managed by the node).

In our example: 500GB * 0.7 = 350GB. The attached storage should be therefore not smaller than 350 GB.



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.

gcloud deployment-manager deployments create [DEPLOYMENT_NAME] --config parameter-file


Overview of configuration parameters:

In the next section is a description of all parameters you might encounter in your parameter-file

(depending on a cluster or single node database or if you want to deploy your resources into an existing network or not, you will encounter a different subset of parameters in your template file)
 See full parameter list
ParameterUsage description
publicIPIf set to true, public IP addresses are assignet to all instances 
dbNodeCountNumber of cluster nodes
standbyNodeIf the replication factor is > 1, then a concurrent standby node can take over the work from a failed node
dbSystemNameName of the generated database
exasolPasswordPassword for the exasol operations admin user (EXAoperation 'admin' user)
dbPasswordPassword for the exasol database admin user (Exasol 'sys' user)
licenseIn case of a byol image an already aquired license can be pasted here as string
firewallRuleRestrict access to specific ip addresses (0.0.0.0/0 results in access from everywhere)
networkNameTarget network
subnetworkNameTarget subnetwork
networkCidrCIDR Block of the target network
subnetworkCidrCIDR Block of target subnetwork
firstNodeIPCounting upwards for the IPs of the data nodes (FirstDataNodeIP > LicenceServerIP)
zoneTarget zone where instances and persistent disks are deployed into
timezone

Required timezone for the DB (default Europe/Berlin)

image

VM Image from the Google Marketplace Solution

machineTypeManagementNodee.g. n1-standard-2
machineTypeDatabaseNodee.g. n1-standard-4
dnsServere.g. 169.254.169.254 (Google Cloud internal DNS Server)
ntpServere.g ntp.ubuntu.com
blockDeviceVolumeSizeGBDevices size for data volume
blockDeviceCountNumber 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:

Please note

  • 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*


Cluster Administration

NEW

Our new Web-based Cloud-Management UI is available now.

If you would like to perform one of the following tasks please refer to the Cloud-plugin documentation  SOL-649 - Getting issue details... STATUS  

    • Scale-Out (Add nodes): Add one or more nodes to the database cluster and database
    • Scale-Up/Down (Change instance type): Change the instance type/model of all data nodes in order to increase or decrease the overall processing power
    • Increasing disk storage capacity: Increase the overall storage capacity by enlarging the data volumes of all database nodes.

You might have to update the plugin first. For instructions on how to update or install the plugin please refer to  SOL-640 - Getting issue details... STATUS

(info) The AMI R6.1.2 in the Google Cloud Marketplace already contains the latest Cloud Pugin version.

Enhanced Failover Capabilities

Before Exasol 6.1 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)

For Details please refer to EXASOL-2423 - Getting issue details... STATUS


Database System Documentation and Further Reading

Loading Data

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

Backup/Restore

SOL-354 - Getting issue details... STATUS  describes how to perform backup and restore operations using S3 ( Additional information on enhanced S3 support can be found in  EXASOL-1752 - Getting issue details... STATUS  and  EXASOL-1958 - Getting issue details... STATUS )

More Information 

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

Storage Configuration

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.

For data backup & restore ( SOL-354 - Getting issue details... STATUS as well as data import & export ( EXASOL-1774 - Getting issue details... STATUS ) Exasol supports cost-efficient S3 storage.