Background With versions prior to 5.0.15 EXASOL cluster deployments only
supported CIDR block 188.8.131.52/16 and subnet 184.108.40.206/16, now it's
possible to use custom CIDR blocks but with some restrictions, because
the CIDR block will automatically be man...
Background This article explains how to activate a new license.
Scenario: License Upgrade with DB RAM expansion Prerequisites: The valid
license file (XML) Short Downtime to stop and start the database
EXAoperation User with privilege Level "Master" ...
Hi @torsten , Since the docker version of Exasol uses different
architecture unfortunately it is not possible to use scripts in
https://github.com/exasol/exaoperation-xmlrpc to manage cluster via
XML-RPC. But of course, you can use the XML-RPC module...
Hi @magarb , Unfortunately, Exasol does not support reducing the size of
the EBS volumes. You can log in via ssh user and change partition size,
but it might cause issues on your system. We will post a new article in
the community to explain how to m...
Hi Mucio, Correct, step 6 may take up to 45 minutes for the EXAoperation
to be online after deployment. You can see the deployment logs in
/var/log/exawolke folder. The management node is accessible via ssh on
port 20 during the deployment process. P...