Shouldn't node down! do a pool shutdown?

[niedfelj]

We are having some weird connection/threading/pool issues when our app first starts up (Moped 2.0.2, Rails 4.1.8, Puma 2.10.2), where Moped can't seem to initially figure out a primary (we are on Heroku cedar-14 stack and Mongolab mongodb 2.6.5). And the errors persist on seemingly one thread until restarted. It seems like Moped is leaving some bad connections around, and in digging through the node.rb code, it looks like down! just tries to checkout a new connection and disconnect it instead of shutting down the whole pool? Shouldn't down! call the ConnectionPool shutdown with a block to shutdown all connections?