Trivial Description
MonitorLoggingIT contains to fail for me on different platforms. It ends up waiting for the log message to show up until the test eventually times out.
The code waits for the Monitor to be up, that it placed its location in ZooKeeper. However, for log-forwarding to be active, any tserver running also has to get the watcher update for the log4j-forwarding node that the monitor updates.
My hunch is that we did the scan, caused the error, and then log4j forwarding was enabled. Should be able to stabilize by waiting before we scan. To definitively know, we'd have to add something to the RPC for tservers to query what their current log-forwarding "state" is (which probably isn't worth the hassle).
