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

Wait longer for first tip in restore-bench #2681

Merged
merged 1 commit into from
May 31, 2021

Conversation

Anviking
Copy link
Member

@Anviking Anviking commented May 31, 2021

Issue Number

ADP-846

Overview

  • Wait longer for first node tip in restore bench

Comments

Attempt to fix this timeout:

https://buildkite.com/input-output-hk/cardano-wallet-nightly/builds/964#fb8228aa-158e-4517-b5bb-883e2be30b24

[bench-restore:Notice:15] [2021-05-31 01:01:17.09 UTC] [cardano-node.66880] withBackend action done. Terminating child process
restore: UnliftIO.Exception.throwString called with:

Gave up in waitForNodeSync, waiting a tip
Called from:
  throwString (bench/Restore.hs:777:18 in main:Main)

It might just be the node re-validating its entire state, taking a lot
of time. In this case, waiting longer should help.

Update

https://buildkite.com/input-output-hk/cardano-wallet-nightly/builds/966#32b592d5-567d-41b9-91bb-d99d89209506

After a while we start seeing Initial node synchronization: still restoring (97.04%), so it seems to work.

Attempt to fix this timeout:

https://buildkite.com/input-output-hk/cardano-wallet-nightly/builds/964#fb8228aa-158e-4517-b5bb-883e2be30b24

```
[bench-restore:Notice:15] [2021-05-31 01:01:17.09 UTC] [cardano-node.66880] withBackend action done. Terminating child process
restore: UnliftIO.Exception.throwString called with:

Gave up in waitForNodeSync, waiting a tip
Called from:
  throwString (bench/Restore.hs:777:18 in main:Main)
```

It might just be the node re-validating its entire state, taking a lot
of time. In this case, waiting longer should help.
@Anviking Anviking requested a review from piotr-iohk May 31, 2021 10:55
@Anviking Anviking self-assigned this May 31, 2021
Copy link
Contributor

@piotr-iohk piotr-iohk left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🤞

@piotr-iohk
Copy link
Contributor

bors r+

@iohk-bors
Copy link
Contributor

iohk-bors bot commented May 31, 2021

Build succeeded:

@iohk-bors iohk-bors bot merged commit 0b8cadb into master May 31, 2021
@iohk-bors iohk-bors bot deleted the anviking/ADP-846/greater-timeout branch May 31, 2021 15:25
@ghost

This comment has been minimized.

@Anviking
Copy link
Member Author

Fixed this error, but the previous heap exhausted error remains.

Copy link
Contributor

@rvl rvl left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks!

Two hours is quite a while. 😬

But usually the chain should be cached on the benchmark machine between runs.

And we don't want to start the benchmark before cardano-node is fully synced, because it will influence the measurements.

@Anviking
Copy link
Member Author

Anviking commented Jun 1, 2021

Two hours is quite a while.

But usually the chain should be cached on the benchmark machine between runs

Yes. We should mostly wait for either the ledger-validation, or full synchronisation, but never both.

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

Successfully merging this pull request may close these issues.

3 participants