search

microsoft / Purview-ADB-Lineage-Solution-Accelerator

A connector to ingest Azure Databricks lineage into Microsoft Purview
MIT License
90 stars 55 forks source link

Crash with exit code: 143 #209

Open jtran2023 opened 1 year ago

jtran2023 commented 1 year ago

Hi, Hope you could help.

Current setup: image

error from log4j and complete log4j attached:

6803957155303634069_7909027679503007739_job-980829582242690-run-5532233-action-1639381203807456 23/06/28 07:53:52 INFO DriverCorral$: Cleaning the wrapper ReplId-5e6c8-2fbdc-d9b49-5 (currently in status Idle(ReplId-5e6c8-2fbdc-d9b49-5)) 23/06/28 07:53:52 INFO DriverCorral$: sending shutdown signal for REPL ReplId-5e6c8-2fbdc-d9b49-5 23/06/28 07:53:52 INFO PythonDriverLocalBase$RedirectThread: Python RedirectThread exit 23/06/28 07:53:52 INFO PythonDriverLocalBase$RedirectThread: Python RedirectThread exit 23/06/28 07:53:52 INFO ReplCrashUtils$: python shell exit code: 143 23/06/28 07:53:52 INFO DriverCorral$: sending the interrupt signal for REPL ReplId-5e6c8-2fbdc-d9b49-5 23/06/28 07:53:52 INFO DriverCorral$: waiting for localThread to stop for REPL ReplId-5e6c8-2fbdc-d9b49-5 23/06/28 07:53:52 INFO DriverCorral$: ReplId-5e6c8-2fbdc-d9b49-5 successfully discarded 23/06/28 07:53:52 INFO DriverCorral$: Cleaning the wrapper ReplId-54980-b86c0-994c6-a (currently in status Idle(ReplId-54980-b86c0-994c6-a)) 23/06/28 07:53:52 INFO DriverCorral$: sending shutdown signal for REPL ReplId-54980-b86c0-994c6-a 23/06/28 07:53:52 INFO DriverCorral$: sending the interrupt signal for REPL ReplId-54980-b86c0-994c6-a 23/06/28 07:53:52 INFO DriverCorral$: waiting for localThread to stop for REPL ReplId-54980-b86c0-994c6-a 23/06/28 07:53:52 INFO DriverCorral$: ReplId-54980-b86c0-994c6-a successfully discarded 23/06/28 07:54:03 ERROR CommandLineHelper$: Command [REDACTED] failed with exit code 1 out: err: 23/06/28 07:54:54 INFO DataSourceFactory$: DataSource Jdbc URL: jdbc:mariadb://consolidated-australiaeast-prod-metastore-addl-1.mysql.database.azure.com:3306/organization8119356306712193 useSSL=true&sslMode=VERIFY_CA&disableSslHostnameVerification=true&trustServerCertificate=false&serverSslCert=/databricks/common/mysql-ssl-ca-cert.crt 23/06/28 07:54:54 INFO HikariDataSource: metastore-monitor - Starting... 23/06/28 07:54:54 INFO HikariDataSource: metastore-monitor - Start completed. 23/06/28 07:54:55 INFO HikariDataSource: metastore-monitor - Shutdown initiated... 23/06/28 07:54:55 INFO HikariDataSource: metastore-monitor - Shutdown completed. 23/06/28 07:54:55 INFO MetastoreMonitor: Metastore healthcheck successful (connection duration = 490 milliseconds) 23/06/28 07:55:03 INFO HiveMetaStore: 3: get_database: default log4j-active.txt ?

wjohnson commented 12 months ago

Hi, @jtran2023 I apologize for the delay in responding. Thank you for using the accelerator!

Based on the log4j logs I noticed two things:

  1. The cluster appears to be working and successfully able to run jobs. Are you experiencing any actual error in the user experience or jobs? That error seems to be transient and your job is still running.
  2. You are using a later version of OpenLineage. Please install OpenLineage 0.18.0
jtran2023 commented 12 months ago

OFFICIAL

Hi Will,

Thank you for your response. The job ingested successful without any issues. I am have used both OpenLineage 0.28.0 and latest OpenLineage 0.29.2 and have the same error.

I'll download OpenLineage 0.18.0 and give it another try.

Regards, Justin

OFFICIAL

From: Will Johnson @.> Sent: Friday, 14 July 2023 12:00 AM To: microsoft/Purview-ADB-Lineage-Solution-Accelerator @.> Cc: Justin Tran @.>; Mention @.> Subject: [External]Re: [microsoft/Purview-ADB-Lineage-Solution-Accelerator] Crash with exit code: 143 (Issue #209)

CAUTION: This email originated from outside of TAFE NSW. Do not click links or open attachments unless you recognise the sender and know the content is safe.

Hi, @jtran2023https://github.com/jtran2023 I apologize for the delay in responding. Thank you for using the accelerator!

Based on the log4j logs I noticed two things:

  1. The cluster appears to be working and successfully able to run jobs. Are you experiencing any actual error in the user experience or jobs? That error seems to be transient and your job is still running.
  2. You are using a later version of OpenLineage. Please install OpenLineage 0.18.0

- Reply to this email directly, view it on GitHubhttps://github.com/microsoft/Purview-ADB-Lineage-Solution-Accelerator/issues/209#issuecomment-1634299550, or unsubscribehttps://github.com/notifications/unsubscribe-auth/BA5PBN6DQXLYJV35B5H2UALXP75OBANCNFSM6AAAAAAZX3PVF4. You are receiving this because you were mentioned.Message ID: @.**@.>>

The contents of this email and its attachments are confidential and intended solely for the use of the individual or entity to whom they are addressed.

jtran2023 commented 12 months ago

Hi Will, I've tried with 0.18.0... error persist.

Thanking you. Justin

patilni8 commented 10 months ago

Hi Will , wijohns@microsoft.com

Greetings! Justin tried the way you suggested but the error still persist. Highly appreciate if you can look into and support us.

Thanks in advance. With Kind Regards, Nilesh

wjohnson commented 6 months ago

@jtran2023 and @patilni8 is this issue still persisting? When you switched back to 0.18 did you start receiving assets in Purview?

The error code 143 appears to be unrelated to OpenLineage. With OL 0.23, it uses a ConsoleTransport so you wouldn't see any events being pushed to Purview. Moving down to 0.18 should get events out.