Comment 8 for bug 1599779

Well, confirmed but since the environment wouldn't bootstrap and I killed the bootstrap process so I could look at the logs, I now have a machine I can't kill. Yay.

My guess is that something like log forwarding opens state to log something, logs it, closes the connection (though it could be anything that is performing lots of state open/close calls). The fact that Mongo is sitting there being hammered points at something causing write amplification. Fun.