After you submit a Staging Push Cassandra dSource, Data Control Tower creates and manages a staging Cassandra cluster on the staging host. You do not manually create a tenant database as part of this workflow.
Your responsibility is to ensure that the required Cassandra backup data is available at the staging mount path specified during dSource creation.
What happens after submission
When you create a Staging Push Cassandra dSource, the Cassandra connector:
- Mounts the configured staging path
- Validates the host, ports, and Cassandra binaries
- Sets up and manages the staging Cassandra cluster
- Uses the staged backup data during linking and snapshot workflows
- Creates and manages the staging Cassandra cluster entirely through the connector workflow
The dSource status reflects whether the staging Cassandra instances are running successfully.
- Do not manually create a “tenant database” at the staging mount path.
- Do not treat the staging mount path as a location to initialize a new Cassandra database.
Steps
- Confirm the staging mount path specified during dSource creation.
- If needed, log in to the staging host to verify the mount path and file access.
- Ensure that the required Cassandra backup data is present at the mounted staging path.
- In Data Control Tower, monitor the dSource job and verify that it reaches a healthy running state.
Verification
Verify the following in Data Control Tower:
- The dSource job completes successfully
- The staging workflow finishes without errors
- The dSource shows a running or active status
If the dSource does not become active
Check for the following issues:
- Missing or incorrectly placed Cassandra backup data
- An invalid or inaccessible staging mount path
- Port conflicts on the staging host
- Host or environment-user configuration problems
- Missing Cassandra binaries or required dependencies
If needed, download the connector logs for troubleshooting.