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

Nucleus lambda function pds-nucleus-datasync-completion sometimes fails to write copied data file names to Nucleus database #83

Closed
ramesh-maddegoda opened this issue Feb 5, 2024 · 3 comments
Assignees
Labels
bug Something isn't working s.high High severity

Comments

@ramesh-maddegoda
Copy link
Contributor

ramesh-maddegoda commented Feb 5, 2024

Checked for duplicates

Yes - I've already checked

🐛 Describe the bug

When I copied a large amount data with AWS DataSync, the Nucleus lambda function pds-nucleus-datasync-completion got triggered as expected. Also, Nucleus was able to process a many products. However, I noticed that there are few products remain in the Nucleus database as "INCOMPLETE". When I checked the database and files, I had the following observations.

  1. The AWS DataSyn has copied all the data files and products labels of these "INCOMPLETE" products to the EFS volume.
  2. The Nucleus lambda function pds-nucleus-datasync-completion has successfully updated the Nucleus database tables: product and product_data_file_mapping
  3. The Nucleus lambda function pds-nucleus-datasync-completion has failed to update the Nucleus database table: data_file
  4. The failed data files that were not written to the database are large IMG files

🕵️ Expected behavior

I expected the Nucleus lambda function pds-nucleus-datasync-completion to update the Nucleus table: data_file, after copying the data file to EFS, regardless of the size or type of the data file.

📜 To Reproduce

Copy a large amount data with AWS DataSync and let the the Nucleus lambda function pds-nucleus-datasync-completion to get triggered.

Check if it has relevant records for all the files copied.

@tloubrieu-jpl
Copy link
Member

Hi @ramesh-maddegoda ,

Do you foresee a PR associated with this ticket ? I am wondering what the review process will be here.

Thanks

@ramesh-maddegoda
Copy link
Contributor Author

Hi @ramesh-maddegoda ,

Do you foresee a PR associated with this ticket ? I am wondering what the review process will be here.

Thanks

@tloubrieu-jpl , I changed the status to Review/QA, because I was doing QA on it with large data sets. Now QA is completed.

I also have a pull request now: #85

@ramesh-maddegoda
Copy link
Contributor Author

The pull request: #85 approved and also tested successfully.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working s.high High severity
Projects
Status: 🏁 Done
Development

No branches or pull requests

3 participants