Hi, I'm Bolo!
What would you like to know?
ASK BOLO
Please to access Bolo.

Table of Contents

Search

  1. Advanced clusters
  2. Setting up AWS
  3. Setting up Google Cloud
  4. Setting up Microsoft Azure
  5. Setting up a self-service cluster
  6. Setting up a local cluster
  7. Advanced configurations
  8. Troubleshooting
  9. Appendix A: Command reference

Advanced Clusters

Advanced Clusters

Learn about resource access

Learn about resource access

To process data, the Secure Agent and the self-service cluster access the resources that are part of a job, including resources on the cloud platform, source and target data, and staging and log locations.
The agent and the cluster access resources to perform the following tasks:
  • Design a mapping.
  • Connect to a self-service cluster.
  • Run a job, including a data preview job.
  • Poll logs.
Designing a mapping
When you design a mapping, the Secure Agent accesses sources and targets so that you can read and write data.
For example, when you add a Source transformation to a mapping, the Secure Agent accesses the source to display the fields that you can use in the rest of the mapping. The Secure Agent also accesses the source when you preview data.
To access a source or target, the Secure Agent uses the connection properties. For example, the Secure Agent might use the user name and password that you provide in the connection properties to access a database.
Connecting to a self-service cluster
To connect to a self-service cluster, the Secure Agent stores cluster information in the staging location.
Running a job
To run an
advanced job
, the Secure Agent and worker nodes access sources and targets, the staging location, and the log location.
The following image shows how resources are accessed when a job runs on a self-service cluster:
The Secure Agent stores job dependencies in the staging location and submits the job to the cluster. Then, the cluster nodes get the job dependencies, stage data in the staging location, and store logs in the log location. At the end of the job, the Secure Agent uploads the agent log to the log location.
The following steps describe the process that the Secure Agent and cluster nodes use to run the job:
  1. You run a job.
  2. The Secure Agent stores cluster information in the staging location using the permission from the Secure Agent role.
  3. The Secure Agent accesses the cluster using the kubeconfig file and submits a job to the self-service cluster.
  4. The worker nodes use the access information to the staging and log storage accounts to get job dependencies from the staging location, to stage data in the staging location, and to store logs in the log location.
  5. The Secure Agent uses the Secure Agent role to upload the agent job log to the log location.
Polling logs
When you use Monitor, the Secure Agent accesses the log location to poll logs.
To poll logs from the log location, the Secure Agent uses the role that is assigned to the Secure Agent machine.

0 COMMENTS

We’d like to hear from you!