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 import of Cardano transactions in testing-mainnet #1849

Closed
6 tasks done
jpraynaud opened this issue Jul 22, 2024 · 0 comments · Fixed by #1850
Closed
6 tasks done

Slow import of Cardano transactions in testing-mainnet #1849

jpraynaud opened this issue Jul 22, 2024 · 0 comments · Fixed by #1850
Assignees
Labels
performances 🥇 Performances

Comments

@jpraynaud
Copy link
Member

jpraynaud commented Jul 22, 2024

Why

We have noticed very slow import of the Cardano transactions on the testing-mainnet network (more than 2 weeks for the aggregator database).

Important

After investigation, it appears that the hard disk that is used on the aggregator is not fast enough and should be upgraded.
We have tested faster disk on the VM and this has fixed the problem. We have not seen the problem occurring on the signers side as their database is pruned along the way: this means that only the aggregator needs to be upgraded.

What

Investigate the origin of the problem and implement a fix.

How

  • Investigate the problem
  • Upgrade the data disk of the testing-mainnet VM to pd-balanced
    • check no SSL problem => it will require a regeneration of the SSL certificate
    • check disk backup policy is activated
  • Re-import aggregator Cardano transactions and check that it takes reasonable time
  • Prepare the upgrade of the data disk of the release-mainnet VM to pd-balanced and plan it with a release prior to activation of the certification of Cardano transactions

Later

  • Create a runbook for upgrading the disk instance of a VM
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
performances 🥇 Performances
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant