connectors

No menu items for this category
Home/Connectors/Database/Impala/Troubleshooting

Troubleshooting

Workflow Deployment Error

If there were any errors during the workflow deployment process, the Ingestion Pipeline Entity will still be created, but no workflow will be present in the Ingestion container.

  • You can then Edit the Ingestion Pipeline and Deploy it again.
  • From the Connection tab, you can also Edit the Service if needed.

Connector Debug Troubleshooting

This section provides instructions to help resolve common issues encountered during connector setup and metadata ingestion in OpenMetadata. Below are some of the most frequently observed troubleshooting scenarios.

How to Enable Debug Logging for Any Ingestion

To enable debug logging for any ingestion workflow in OpenMetadata:

  1. Navigate to Services Go to Settings > Services > Service Type (e.g., Database) in the OpenMetadata UI.

  2. Select a Service Choose the specific service for which you want to enable debug logging.

Select a Service

Select a Service

  1. Access Ingestion Tab Go to the Ingestion tab and click the three-dot menu on the right-hand side of the ingestion type, and select Edit.
Access Agents Tab

Access Agents Tab

  1. Enable Debug Logging In the configuration dialog, enable the Debug Log option and click Next.
Enable Debug Logging

Enable Debug Logging

  1. Schedule and Submit Configure the schedule if needed and click Submit to apply the changes.
Schedule and Submit

Schedule and Submit

Permission Issues

If you encounter permission-related errors during connector setup or metadata ingestion, ensure that all the prerequisites and access configurations specified for each connector are properly implemented. Refer to the connector-specific documentation to verify the required permissions.

Learn how to resolve the most common problems people encounter in the Impala connector.

Connection Timeout

You might be getting thrift.transport.TTransport.TTransportException: TSocket read 0 bytes.

Make sure that if there is a Load Balancer in between OpenMetadata and Impala, the LB timeout is not impacting the ingestion. For example, when extracting data with a lot of partitions the DESCRIBE command might take more than 60 seconds, so a Load Balancer with Idle Timeout at 60 seconds would kill the connection.