As suggested by thumper, this appears to be caused by a goroutine leak:
$ for i in 1 2 3 ; do juju_goroutines | head -n 1; sleep 60; done Querying @jujud-machine-0 introspection socket: /debug/pprof/goroutine?debug=1 goroutine profile: total 34295 Querying @jujud-machine-0 introspection socket: /debug/pprof/goroutine?debug=1 goroutine profile: total 34499 Querying @jujud-machine-0 introspection socket: /debug/pprof/goroutine?debug=1 goroutine profile: total 34725
As suggested by thumper, this appears to be caused by a goroutine leak:
$ for i in 1 2 3 ; do juju_goroutines | head -n 1; sleep 60; done pprof/goroutine ?debug= 1 pprof/goroutine ?debug= 1 pprof/goroutine ?debug= 1
Querying @jujud-machine-0 introspection socket: /debug/
goroutine profile: total 34295
Querying @jujud-machine-0 introspection socket: /debug/
goroutine profile: total 34499
Querying @jujud-machine-0 introspection socket: /debug/
goroutine profile: total 34725