-
Notifications
You must be signed in to change notification settings - Fork 92
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
Suspend bench #446
Suspend bench #446
Conversation
related to: #377
it is look like that shard-manager had issues to connect to redis
after max wait time for service startup was changed from 30s to 90s it is working
|
@@ -118,10 +118,10 @@ async fn wait_for_startup_grpc(host: &str, grpc_port: u16, name: &str) { | |||
if success { | |||
break; | |||
} else { | |||
if start.elapsed().as_secs() > 30 { | |||
if start.elapsed().as_secs() > 90 { |
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.
fix for minikube issues (#377)
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 what was the "issue"?
panic!("Failed to verify that {name} is running"); | ||
} | ||
tokio::time::sleep(Duration::from_secs(1)).await; | ||
tokio::time::sleep(Duration::from_secs(2)).await; |
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.
Hmm.
fixes: #384
result
result