After ADB Control upgrade to 4.3.2, the Export job settings (that are defined on the Configuration → Job policy → Metrics offload page) are reset to defaults |
4.3.2 |
4.3.2 |
Fill in and save the required settings. The problem does not affect future upgrades |
Standby activation after switching from master fails on clusters with ADB Control/ADBM installed |
4.3.1 |
4.3.2 |
Use external ADB Control/ADBM |
In ADB Control 4.2.1, you cannot register new external ADB clusters with versions earlier than 6.23.3 |
4.2.1 |
4.2.1 |
Update ADB cluster to 6.23.3 |
Commands appear in the Running status on the Monitoring → Commands → Online page but after 14-16 seconds they freeze in the Unknown status (with no metrics updated). After the command completion, all metrics become available on the Monitoring → Commands → History page, but the Unknown status persists |
4.1.0 |
4.2.0 |
-
Using the psql or other SQL IDE, set the adcc user password via the following command:
ALTER USER adcc WITH ENCRYPTED PASSWORD '<password>';
-
Open the Configuration → Clusters page in the ADCC UI and go to editing the cluster connection.
-
In the Password field, set the <password> value from the step 1. Click Save.
|
There is a potential memory leak with specific queries affected by the gpperfmon engine. If you use queries against huge tables with UDF that generate inner per-tuple queries, you may experience the significant RAM consumption, and even get OOM errors. The example is the information_schema.columns view, which can cause memory leak when being selected against a large system catalog |
4.0.0 |
4.1.0 |
The possible solution is to switch off monitoring metrics (this operation requires cluster restart):
-
Remove gpadcc from shared_preload_libraries, e.g.:
$ gpconfig -c shared_preload_libraries -v ""
-
Switch off the following parameters:
$ gpconfig -c gp_enable_gpperfmon -v off
$ gpconfig -c adcc.explain_log_verbose -v off
$ gpconfig -c adcc.explain_log_analyze -v off
-
Restart your cluster:
$ gpstop -a -M fast
$ gpstart a
Remember that this workaround does not disable the ADCC UI and Arenadata DB Backup Manager
|
Backend ADCC server cannot connect to ADCC UI server. Data update may not always work on the details page |
4.0.0 |
4.1.0 |
-
Connect to the ADCC server via SSH.
-
Go to the /opt/adcc directory.
-
Edit the docker-compose.yaml file. For the adcc_ui_server and adcc_backend_server services, change the value of the ADCC_EUREKA_CLIENT_PREFER_IP_ADDRESS environment variable to true.
-
Run the command and wait until all Docker containers stop:
-
Run the following command:
|
It is impossible to configure the Data cleanup job on the Configuration page. In general, ADCC can work without data cleanup, but you need to monitor the metrics database size |
4.0.0 |
4.1.0 |
-
Connect to the ADCC server via SSH.
-
Go to the /opt/adcc directory.
-
Edit the docker-compose.yaml file. For the adcc_scheduler service, add the following environment variable: ADCC_SCHEDULER_GRPC_PORT: 6572.
-
Run the command and wait until all Docker containers stop:
-
Run the following command:
|
