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.

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

Slow down execution of data suite #422

Open
jeanetteclark opened this issue Apr 25, 2024 · 2 comments
Open

Slow down execution of data suite #422

jeanetteclark opened this issue Apr 25, 2024 · 2 comments

Comments

@jeanetteclark
Copy link
Collaborator

The data suite shouldn't run unless the metadata document and resource map have finished indexing. I'm not positive, but I'm seeing some random "identifier not found on the node" errors with the data quality suite, and I think it is because the package has not finished indexing.

Need to find a mechanism to not run the suite until that indexing has finished

@mbjones
Copy link
Member

mbjones commented May 3, 2024

This sounds smart if we are accessing things via the API. If we move to accessing content from the filesystem, I presume this wait is not necessary and we can go ahead with the metadig data runs before indexing completes?

@jeanetteclark
Copy link
Collaborator Author

yes for sure not needed when we switch to filesystem access. For now I have a bit of a hack in the first check that runs in the suite that seems to be working ok, and is easily removed when we switch data access mechanisms

    data_pids <- NULL
    attempt <- 1
    while(is.null(data_pids) && attempt <=10) {
      attempt <- attempt + 1
      try(data_pids <- get_data_pids(sys@identifier, sys@authoritativeMemberNode))
      Sys.sleep(5)
    }

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants