-
Notifications
You must be signed in to change notification settings - Fork 43
deploy 5 CockroachDB nodes from RSS #3450
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
Changes from all commits
5a7ecec
9c7bbf7
a3012b2
2c30183
ee88853
409c949
a3e0562
5e5177a
4d87e71
64c0c4f
8651d75
1976753
d820a55
c24c2e8
752f01e
d98a2a5
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -127,7 +127,7 @@ pub async fn nexus_addr() -> Result<IpAddr> { | |
&resolver, | ||
&dns_name, | ||
Duration::from_secs(1), | ||
Duration::from_secs(300), | ||
Duration::from_secs(600), | ||
) | ||
.await | ||
} | ||
|
@@ -240,7 +240,7 @@ pub async fn build_client() -> Result<oxide_client::Client> { | |
}) | ||
}, | ||
&Duration::from_secs(1), | ||
&Duration::from_secs(300), | ||
&Duration::from_secs(600), | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. We're deploying two extra CockroachDB nodes and it can take a little longer for the system to set up now. There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. I can look into parallelizing service bringup on the sled-agent side, if that would help mitigate? There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. I expect it would. No pressure on my part in terms of urgency. There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Sounds good, lets not block this PR, but I can do this as a follow-up. |
||
) | ||
.await | ||
.context("logging in")?; | ||
|
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.
For local testing CRDB -- e.g. with the omicron-dev tool -- what does this do?
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.
Good question. I expect it will have no practical impact. The default replication factor is 3, which is already more nodes than we ever have today. The impact is that CockroachDB considers all of its data under-replicated. It reports it as such (e.g., here) and if new nodes show up, it will try to replicate data until nothing is under-replicated.
One could imagine that this would instead disallow you from writing any data to the cluster when it can't satisfy this constraint. That doesn't seem to be how it works. If it did, the tests wouldn't run at all, I think.