Timeouts are not configurable for RPC

[peay]

The timeouts for RPC do not seem to be configurable. From rpc.go:

var (
	connectTimeout  = 1 * time.Second
	namenodeTimeout = 3 * time.Second
	datanodeTimeout = 3 * time.Second
)

These values are rather low (especially the connection timeout), and I have been experiencing quite a lot of timeouts.

Being able to configure these would be very helpful. This does not have to be per client -- a global setting would be fine too.

[colinmarc]

Hi @peay,

Good point - this should definitely be configurable. This dovetails well with the need for a configurable dialer in #70.

[colinmarc]

With #77, there now exists a ClientOptions struct, so this should now be implementable.

[Itfly]

@colinmarc Any update for this issue, i also got error: dial tcp: i/o timeout. After modifying the value to 3, the real error is hostname cannot be resolved. This is beacause the datanodes' hostnames are not being registed into my company's DNS server.

[colinmarc]

I'm working on a rework of timeouts. But it doesn't sound like your issue is timouts, @Itfly; it sounds like your datanode hosts aren't resolvable from the client. If you fix your DNS setup it should work.

[Itfly]

@colinmarc Yes it works after i adding the datanode host to our company's DNSSelfService. However, i suggest to make it configurable about using hostname or ip address (#123)