Don't close namenode connection on RPC failure about hdfs HOT 3 CLOSED

It seems like it would be necessary to distinguish between errors that are fatal and errors that are not. Perhaps I can figure out what the java client does.

from hdfs.

@colinmarc, I'm addressing this currently by checking if the returned error for NamenodeConnection.readResponse is EOF in NamenodeConnection.Execute. If it is an EOF, then it falls into the same retry logic as a standby exception. It seems like getting an EOF at this location is constrained to the case of:

1. You successfully connected to a namenode at some point
2. The connection to that namenode has since been severed

What do you think about making this specific inference?

from hdfs.

It's no longer the case that the whole connection is closed - I'm not sure when that was fixed - so I'm going to close this.

from hdfs.