You are viewing a plain text version of this content. The canonical link for it is here.
Posted to mapreduce-issues@hadoop.apache.org by "Gilad Wolff (JIRA)" <ji...@apache.org> on 2014/01/04 02:54:50 UTC
[jira] [Created] (MAPREDUCE-5707) JobClient does not allow to set
rpcTimeout
Gilad Wolff created MAPREDUCE-5707:
--------------------------------------
Summary: JobClient does not allow to set rpcTimeout
Key: MAPREDUCE-5707
URL: https://issues.apache.org/jira/browse/MAPREDUCE-5707
Project: Hadoop Map/Reduce
Issue Type: Bug
Components: client
Affects Versions: 2.2.0, 0.20.2
Reporter: Gilad Wolff
The ApplicationClientProtocolPBClientImpl c'tor (and the JobClient 0.20.2 c'tor as well) creates an rpc proxy that eventually uses '0' as the rpcTimeout:
{code}
public ApplicationClientProtocolPBClientImpl(long clientVersion,
InetSocketAddress addr, Configuration conf) throws IOException {
RPC.setProtocolEngine(conf, ApplicationClientProtocolPB.class,
ProtobufRpcEngine.class);
proxy = RPC.getProxy(ApplicationClientProtocolPB.class, clientVersion, addr, conf);
}
{code}
which leads to this call in RPC:
{code}
public static <T> ProtocolProxy<T> getProtocolProxy(Class<T> protocol,
long clientVersion,
InetSocketAddress addr,
UserGroupInformation ticket,
Configuration conf,
SocketFactory factory) throws IOException {
return getProtocolProxy(
protocol, clientVersion, addr, ticket, conf, factory, 0, null);
{code}
(the '0' above is the rpc timeout).
Clients should be able to specify the rpc timeout.
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)