fig (aka:[phil]) @bad-example.com · May 11 disappointingly, i can't pin this down to anything on the host. it had some further 14m45s-periodic throttles later yesterday. eventually the connection would get killed somewhere upstream and jetstream would restart. nothing on the host itself indicates a source of throttling though!
1 likes 1 replies
?
Replies
it's very weird because about 6 commits/sec were still arriving during the "dead" periods, which stopped jetstream's liveliness monitor from triggering a restart (note the log scale in that last chart). it *seems* like it was somehow coming from upstream or a middlebox. i'll keep an eye out for it.