https://community.databricks.com/t5/warehousing-analytics/unable-to-run-2-different-applications-with-the-same-class-name/m-p/20783#M453 <P>I have two jars with the same class name. It works fine on yarn. When trying to run these jars on the Databricks cluster, I run into issues. Why Databricks is having this limitation?</P> Thu, 20 Mar 2025 17:11:12 GMT brickster_2018 2025-03-20T17:11:12Z https://community.databricks.com/t5/warehousing-analytics/unable-to-run-2-different-applications-with-the-same-class-name/m-p/20783#M453 <P>I have two jars with the same class name. It works fine on yarn. When trying to run these jars on the Databricks cluster, I run into issues. Why Databricks is having this limitation?</P> Thu, 20 Mar 2025 17:11:12 GMT https://community.databricks.com/t5/warehousing-analytics/unable-to-run-2-different-applications-with-the-same-class-name/m-p/20783#M453 brickster_2018 2025-03-20T17:11:12Z https://community.databricks.com/t5/warehousing-analytics/unable-to-run-2-different-applications-with-the-same-class-name/m-p/20784#M454 <P>When you run the jobs in Yarn, those are 2 different applications getting submitted on Yarn. Hence each application will have a separate Spark driver JVM's. </P><P>In Databricks, a cluster has one JVM for the Spark driver. When applications with the same name are submitted on the same JVM, it's possible the classes are loaded from the incorrect jars. </P><P></P><P>Mitigations/Solution:</P><UL><LI>Use an on-demand cluster for your jobs. This will ensure one jar uses a dedicated cluster. </LI><LI>Change the class name in one of the classes to avoid conflict. </LI></UL><P></P> Thu, 24 Jun 2021 06:52:56 GMT https://community.databricks.com/t5/warehousing-analytics/unable-to-run-2-different-applications-with-the-same-class-name/m-p/20784#M454 brickster_2018 2021-06-24T06:52:56Z