Hi, I tried to run a mysql ingestion from the cli, while connection to datahub that is deployed on k8s. It got stuck with the following error:

Cli report:
{'cli_version': '0.8.43.6',
 'cli_entry_location': '/Users/liza.raskin/datahub-env/lib/python3.9/site-packages/datahub/__init__.py',
 'py_version': '3.9.7 (default, Sep 16 2021, 08:50:36) \n[Clang 10.0.0 ]',
 'py_exec_path': '/Users/liza.raskin/datahub-env/bin/python3',
 'os_details': 'macOS-10.16-x86_64-i386-64bit'}
Source (mysql) report:
{'events_produced': '1001',
 'events_produced_per_sec': '13',
 'event_ids': ['container-info-trc-urn:li:container:abb952b2a1b5dfedb83e8e726f23be70',
               'container-platforminstance-trc-urn:li:container:abb952b2a1b5dfedb83e8e726f23be70',
               'container-subtypes-trc-urn:li:container:abb952b2a1b5dfedb83e8e726f23be70',
               'container-urn:li:container:abb952b2a1b5dfedb83e8e726f23be70-to-urn:li:dataset:(urn:li:dataPlatform:mysql,trc._account_history_tmp,PROD)',
               'trc._account_history_tmp',
               'trc._account_history_tmp-subtypes',
               '... 990 more elements',
               'container-urn:li:container:abb952b2a1b5dfedb83e8e726f23be70-to-urn:li:dataset:(urn:li:dataPlatform:mysql,trc.fpp_client_placement_identifier_config,PROD)',
               'trc.fpp_client_placement_identifier_config',
               'trc.fpp_client_placement_identifier_config-subtypes',
               'container-urn:li:container:abb952b2a1b5dfedb83e8e726f23be70-to-urn:li:dataset:(urn:li:dataPlatform:mysql,trc.fpp_experiment_variant_rules,PROD)',
               'trc.fpp_experiment_variant_rules'],
 'warnings': {'trc.cra_predictions_task': ['unable to map type BIT(length=1) to metadata schema'],
              'trc.dco_advertisers': ['unable to map type BIT(length=1) to metadata schema',
                                      'unable to map type BIT(length=1) to metadata schema',
                                      'unable to map type BIT(length=1) to metadata schema']},
 'failures': {},
 'tables_scanned': '333',
 'views_scanned': '0',
 'entities_profiled': '0',
 'filtered': [],
 'soft_deleted_stale_entities': [],
 'start_time': '2022-08-31 15:19:18.625657',
 'running_time_in_seconds': '72'}
Sink (datahub-rest) report:
{'total_records_written': '0',
 'records_written_per_second': '0',
 'warnings': [],
 'failures': [],
 'start_time': '2022-08-31 15:17:38.528119',
 'current_time': '2022-08-31 15:20:30.860222',
 'total_duration_in_seconds': '172.33',
 'gms_version': 'v0.8.43',
 'pending_requests': '1000'}

:hourglass_flowing_sand: Pipeline running with 4 warnings so far; produced 1001 events

looking at the datahub logs I see this error:

org.apache.kafka.common.errors.TimeoutException: Topic MetadataChangeLog_Versioned_v1 not present in metadata after 60000 ms.

Kafka pod is up and running Any ideas what can be causing this?

hi, if you are using the helm charts, can you see the kafka-setup-jobs? have they run successfully?