we've still got some trouble here.  This line will cause a new connection to hbase to be created right then and there.  Since we've only just detected the trouble, we're not allowing for the wait of the backing off retry, we're effectively retry immediately. If this new connection fails, it's going to raise exceptions that we're not prepared to deal with.

A better solution would be for the force_reconnect to close the current connection (eating/bug logging any exceptions that happen) then set the `self.conn` to None.  In the `__call__`, test to see if the connection in None, if so make the new connection.  if not None, just yield the current connection.

That'll delay the creation of a new connection to after the retry time and make sure that the creation of connections is within a context that is prepared to handle connection errors.