Skip to content

Commit 7a0844c

Browse files
anholtsylvestre
authored andcommitted
Give the --dist-status user some information about when a retry will happen.
The retry timeout is so long that I sometimes wonder during setup debug if it's even going to retry.
1 parent 96d7400 commit 7a0844c

File tree

1 file changed

+5
-2
lines changed

1 file changed

+5
-2
lines changed

src/server.rs

Lines changed: 5 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -258,10 +258,13 @@ impl DistClientContainer {
258258
"enabled, auth not configured".to_string(),
259259
)
260260
}
261-
DistClientState::RetryCreateAt(cfg, _) => {
261+
DistClientState::RetryCreateAt(cfg, time) => {
262262
return DistInfo::NotConnected(
263263
cfg.scheduler_url.clone(),
264-
"enabled, not connected, will retry".to_string(),
264+
format!(
265+
"enabled, not connected, will retry in {:.1}s",
266+
time.duration_since(Instant::now()).as_secs_f32()
267+
),
265268
)
266269
}
267270
DistClientState::Some(cfg, client) => (Arc::clone(client), cfg.scheduler_url.clone()),

0 commit comments

Comments
 (0)