Hi team! good morning! i did the deploy with kubernetes and everythings its ok, but when im trying to do an ingestion the status is continually running, any ideas? i see this error: raise HTTPError(http_error_msg, response=self) requests.exceptions.HTTPError: 500 Server Error: Server Error for url: http://datahub-datahub-gms:8080/aspects?action=ingestProposal and: datahub.configuration.common.OperationalError: ('Unable to emit metadata to DataHub GMS: com.datahub.util.exception.RetryLimitReached: Failed to add after 3 retries', {'exceptionClass': 'com.linkedin.restli.server.RestLiServiceException', 'message': 'com.datahub.util.exception.RetryLimitReached: Failed to add after 3 retries', 'status': 500}) and: RuntimeError: Something went wrong in the subprocess executor: ('Unable to emit metadata to DataHub GMS: com.datahub.util.exception.RetryLimitReached: Failed to add after 3 retries', {'exceptionClass': 'com.linkedin.restli.server.RestLiServiceException', 'message': 'com.datahub.util.exception.RetryLimitReached: Failed to add after 3 retries', 'status': 500})

you are running the ingestion from local machine or via UI ingestion?

Via ui ingestión

and these are the logs from the actions container?

gms container

okay. Can you please check the logs of the actions container. This is the container used to run the ingestion configured via UI. It downloads the python packages (that why it might stay a bit longer time in running in the first run) and then runs it. Maybe there are some other logs

i have doubts wiht the sink url, this recipe its ok? source: type: oracle config: host_port: '0000000000000' service_name: 00000000000000 username: 0000000000000 password: 0000000000 table_pattern: allow: - '.*FFFFF' include_views: false sink: type: datahub-rest config: server: 'http://datahub-datahub-gms.datahub.svc.cluster.local:8080'

if you configure via UI you do not need to add the sink config, isnt it?

So my recipe its ok if i do the ingestion by cli?

So my recipe its ok if i do the ingestion by cli?

if you have access to that url locally yes but I think this wont work as its the kubedns. you would either need to forward the gms to local machine and use that as sink or have another reachable endpoint. And you need to specify a token for auth.

and if i would like to do the ingstion via UI i only have this in my recipe: source: type: oracle config: host_port: '0000000000000' service_name: 00000000000000 username: 0000000000000 password: 0000000000 table_pattern: allow: - '.*FFFFF' include_views: false so the job never finish

can you please check the logs in the actions container if there are additional info?

[d991cf54-be66-4842-b8ea-e38689ca4a41 logs] Successfully uninstalled pip-23.0.1 [2024-01-08 101554,436] DEBUG {acryl.executor.execution.default_executor:136} - Cleaned up task for d991cf54-be66-4842-b8ea-e38689ca4a41 [2024-01-08 101554,533] ERROR {acryl.executor.dispatcher.default_dispatcher:33} - Failed dispatch for d991cf54-be66-4842-b8ea-e38689ca4a41: Traceback (most recent call last): File "/usr/local/lib/python3.10/site-packages/datahub/emitter/rest_emitter.py", line 266, in _emit_generic response.raise_for_status() File "/usr/local/lib/python3.10/site-packages/requests/models.py", line 1021, in raise_for_status raise HTTPError(http_error_msg, response=self) requests.exceptions.HTTPError: 500 Server Error: Server Error for url: http://datahub-datahub-gms:8080/aspects?action=ingestProposal The above exception was the direct cause of the following exception: Traceback (most recent call last): File "/usr/local/lib/python3.10/site-packages/acryl/executor/dispatcher/default_dispatcher.py", line 30, in dispatch_async res = executor.execute(request) File "/usr/local/lib/python3.10/site-packages/acryl/executor/execution/reporting_executor.py", line 94, in execute self._datahub_graph.emit_mcp(completion_mcp) File "/usr/local/lib/python3.10/site-packages/datahub/emitter/rest_emitter.py", line 245, in emit_mcp self._emit_generic(url, payload) datahub.configuration.common.OperationalError: ('Unable to emit metadata to DataHub GMS: com.datahub.util.exception.RetryLimitReached: Failed to add after 3 retries', {'exceptionClass': 'com.linkedin.restli.server.RestLiServiceException', 'message': 'com.datahub.util.exception.RetryLimitReached: Failed to add after 3 retries', 'status': 500})

okay, so its really an emitting error. You are using the default helm chart? or any modifications? Can you log in to the actions container and try to ping the gms pod?

ok i finally find the solution, the problem was the collation of my bbdd so now from the ui works 😃 thbks for your help