Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Getting 'Atum already initialized' error when trying to run Std+Conf multiple times #2213

Open
yruslan opened this issue Mar 19, 2024 · 1 comment
Open

Getting 'Atum already initialized' error when trying to run Std+Conf multiple times #2213

yruslan opened this issue Mar 19, 2024 · 1 comment
Labels
bug Something isn't working priority: undecided Undecided priority to be assigned after discussion

Comments

@yruslan
Copy link
Contributor

yruslan commented Mar 19, 2024

Describe the bug

The error occurs when Standardization+Conformance jobs from a single Spark session. This happenned when running from Pramen since Pramen runs multiple Standardization+Conformance jobs in a single Spark Session.

To Reproduce

Steps to reproduce the behavior OR commands run:

  1. Configure Pramen to run EnceladusSink for multiple tables in a pipeline.
  2. Run the pipeline.
  3. The error will occur saying "Control Measurements Tracking already initialized"

Expected behavior

Allow running multiple Standardization+Conformance jobs multiple times from teh same Spask session.

Screenshots

N/A

Desktop (please complete the following information):

This was happening both in UAT and in PROD.

Additional context

There is already logic in Enceladus that explicitly disables control metrics when conformance jobs runs after standardization. So single Standardization, Conformance, and Standardization+Conformance jobs run fine. The issue happens only if both Standardization and Conformance run multiple times.
@yruslan yruslan added bug Something isn't working priority: undecided Undecided priority to be assigned after discussion labels Mar 19, 2024
yruslan added a commit that referenced this issue Mar 21, 2024
@yruslan @benedeki
#2213 Explicitly disable control metrics at the end of the job. (#2212)
db76241 
* Explicitly disable control metrics at the end of the job.

This is needed when the main method can be invoked more than once externally.

* Update spark-jobs/src/main/scala/za/co/absa/enceladus/standardization_conformance/StandardizationAndConformanceJob.scala

Co-authored-by: David Benedeki <14905969+benedeki@users.noreply.github.com>

---------

Co-authored-by: David Benedeki <14905969+benedeki@users.noreply.github.com>
@yruslan
Copy link
Contributor Author

yruslan commented Mar 21, 2024

Fixed in 2.27. Fix for 3.0 is pending.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bug Something isn't working priority: undecided Undecided priority to be assigned after discussion
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@yruslan