Description
Currently, when one faces a SocketTimeoutExceptions (or any exception rather, in a DN log, for a client <-> DN interaction), we fail to print the DFSClient ID. This makes it untraceable (like is it a speculative MR caused timeout, or a RS crash, etc.).