TB117 Engine Sync Import and Algorithm Rekey Operations May Fail Unexpectedly on Engines Registered With DCT
Alert Type
Functionality
Impact
Continuous Compliance Engines that have been registered with Delphix Data Control Tower (DCT) may experience unexpected, intermittent failures performing engine sync import and algorithm rekey operations.
The following actions from the environment UI are affected:
-
Import Settings
-
Import Environment
The following API paths are affected:
-
algorithms/{algorithmName}/randomize-key
-
sync/import
-
sync/import-async
These errors occur because DCT occasionally initiates sync export activity on registered compliance engines to collect configuration state. The resulting failures have no impact on the stability of the Compliance Engine. Failed operations may be safely attempted again at a later time, though they may fail again unless a workaround is applied.
Contributing Factors
The issue only affects Continuous Compliance engines registered with Data Control Tower (DCT) version 13.0 or greater.
This article applies to the following versions of the Delphix engine:
| Date | Release |
|---|---|
| Jan 25, 2024 | 19.0.0.0 |
| Dec 20, 2023 | Jan 10, 2024 | 18.0.0.0 | 18.0.0.1 |
| Nov 21, 2023 | 17.0.0.0 |
| Oct 18, 2023 | 16.0.0.0 |
| Sep 21, 2023 | 15.0.0.0 |
| Aug 24, 2023 | 14.0.0.0 |
| Jul 24, 2023 | 13.0.0.0 |
| Jun 21, 2023 | 12.0.0.0 |
| May 25, 2023 | 11.0.0.0 |
| Apr 13, 2023 | 10.0.0.0 |
| Mar 13, 2023 | Mar 20, 2023 | 9.0.0.0 | 9.0.0.1 |
| Feb 13, 2023 | 8.0.0.0 |
| Jan 12, 2023 | 7.0.0.0 |
| Releases Prior to 2023 | |
| Major Release | All Sub Releases |
| 6.0 | 6.0.13.0, 6.0.13.1, 6.0.14.0, 6.0.15.0, 6.0.16.0, 6.0.17.0, 6.0.17.1, 6.0.17.2 |
Symptoms
API or UI initiated sync import and rekey operations may fail with the error:
Unable to import while another sync operation is going on or job is running.
This issue may be encountered even when no other customer-initiated sync job or sync import is running.
Relief/Workaround
It is recommended that upgrades to DCT version 13.0.0 or later be delayed until registered compliance engines are upgraded to a version that contains the fix for this issue.
DCT administrators may deregister an affected Continuous Compliance Engine using the Compliance tab of the Data Control Tower UI:
-
Select the Compliance tab in the user interface.
-
Select Compliance Engines.
-
Select the affected continuous compliance engine.
-
In the Actions pull down menu, select Deregister.
Alternatively you may use the management/engine endpoint of the DCT API to deregister an engine. See the “Managing Engines” documentation referenced below for an API example.
Resolution
Resolved in DevOps Data Platform 20.0.0.0 and later releases for Continuous Compliance Engines.
Additional Information
N/A