-
Notifications
You must be signed in to change notification settings - Fork 4.4k
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
testnet-automation: Don't clobber testnet prefix #12527
testnet-automation: Don't clobber testnet prefix #12527
Conversation
@@ -223,6 +223,9 @@ if [[ -z $NUMBER_OF_VALIDATOR_NODES ]]; then | |||
exit 1 | |||
fi | |||
|
|||
dbName="$TESTNET_TAG" |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
So won't clobber the testnets, but you will have overlapping writes to the same db in this case if two hosts are running parallel networks with the same TESTNET_TAG
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
You'll need to update init-metrics.sh
and the call to it here
solana/system-test/testnet-automation.sh
Line 106 in 13ff6b2
"${REPO_ROOT}"/net/init-metrics.sh -e |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ah... yeah... are we worried about having a mess of DBs?
Would be nice if we could have just the one, then generate a UUID for each test run that's tagged to metrics, but I suspect that's a lot of plumbing elsewhere
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Could set custom retention policies for dynamically-created DBs so they don't stick around for too long. The slackbot already creates a custom URL for each test that's run so it displays the db in question only for the time during which the test was running. If something simple like that works for you, that's fine. The bigger problem will come if/when you are having nodes from unrelated testnets writing to the same db at the same time.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks! I'll look into that this evening and report back
This pull request has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. |
This stale pull request has been automatically closed. Thank you for your contributions. |
This pull request has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. |
This pull request has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. |
This stale pull request has been automatically closed. Thank you for your contributions. |
This pull request has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. |
This stale pull request has been automatically closed. Thank you for your contributions. |
Problem
testnet automation doesn't set any host-specific field in the testnet prefix, leading to agents clobbering each others testnets
Summary of Changes
Append hostname to script/user specified
TESTNET_TAG