Skip to content
This repository has been archived by the owner on Sep 30, 2024. It is now read-only.

Commit

Permalink
pkg/conf: clarify what exactly the deadlock detector found when panic…
Browse files Browse the repository at this point in the history
…king
  • Loading branch information
slimsag committed Jun 6, 2019
1 parent eb6b5fb commit 8304609
Showing 1 changed file with 1 addition and 1 deletion.
2 changes: 1 addition & 1 deletion pkg/conf/store.go
Original file line number Diff line number Diff line change
Expand Up @@ -144,7 +144,7 @@ func (s *Store) WaitUntilInitialized() {
// deadlock, so ask Go to dump all goroutine stack traces.
debug.SetTraceback("all")
if IsDev(DeployType()) {
panic("deadlock detected: you have called conf.Get or conf.Watch before the frontend has been initialized (you may need to use a goroutine)")
panic("potential deadlock detected: the frontend's configuration server hasn't started after 30s indicating a deadlock may be happening. A common cause of this is calling conf.Get or conf.Watch before the frontend has started fully (e.g. inside an init function) and if that is the case you may need to invoke those functions in a separate goroutine.")
}
panic(fmt.Sprintf("(bug) frontend configuration server failed to start after %v, this may indicate the DB is inaccessible", deadlockTimeout))
}
Expand Down

0 comments on commit 8304609

Please sign in to comment.