[jira] [Commented] (HADOOP-9944) RpcRequestHeaderProto defines callId as uint32 while ipc.Client.CONNECTION_CONTEXT_CALL_ID is signed (-3)

2014-04-26 Thread Charlene Sun (JIRA)
[ https://issues.apache.org/jira/browse/HADOOP-9944?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13981984#comment-13981984 ] Charlene Sun commented on HADOOP-9944: -- Hey Guys, I discovered the callid for a

[jira] [Commented] (HADOOP-9944) RpcRequestHeaderProto defines callId as uint32 while ipc.Client.CONNECTION_CONTEXT_CALL_ID is signed (-3)

2013-10-31 Thread Benoit Sigoure (JIRA)
[ https://issues.apache.org/jira/browse/HADOOP-9944?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13810371#comment-13810371 ] Benoit Sigoure commented on HADOOP-9944: !http://i.imgur.com/2ClmQri.gif! Where

[jira] [Commented] (HADOOP-9944) RpcRequestHeaderProto defines callId as uint32 while ipc.Client.CONNECTION_CONTEXT_CALL_ID is signed (-3)

2013-09-27 Thread Todd Lipcon (JIRA)
[ https://issues.apache.org/jira/browse/HADOOP-9944?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13780431#comment-13780431 ] Todd Lipcon commented on HADOOP-9944: - This patch made 2.1.1 wire-incompatible with

[jira] [Commented] (HADOOP-9944) RpcRequestHeaderProto defines callId as uint32 while ipc.Client.CONNECTION_CONTEXT_CALL_ID is signed (-3)

2013-09-17 Thread Hudson (JIRA)
[ https://issues.apache.org/jira/browse/HADOOP-9944?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13769422#comment-13769422 ] Hudson commented on HADOOP-9944: SUCCESS: Integrated in Hadoop-Yarn-trunk #335 (See

[jira] [Commented] (HADOOP-9944) RpcRequestHeaderProto defines callId as uint32 while ipc.Client.CONNECTION_CONTEXT_CALL_ID is signed (-3)

2013-09-17 Thread Hudson (JIRA)
[ https://issues.apache.org/jira/browse/HADOOP-9944?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13769442#comment-13769442 ] Hudson commented on HADOOP-9944: FAILURE: Integrated in Hadoop-Hdfs-trunk #1525 (See

[jira] [Commented] (HADOOP-9944) RpcRequestHeaderProto defines callId as uint32 while ipc.Client.CONNECTION_CONTEXT_CALL_ID is signed (-3)

2013-09-17 Thread Hudson (JIRA)
[ https://issues.apache.org/jira/browse/HADOOP-9944?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13769507#comment-13769507 ] Hudson commented on HADOOP-9944: FAILURE: Integrated in Hadoop-Mapreduce-trunk #1551 (See

[jira] [Commented] (HADOOP-9944) RpcRequestHeaderProto defines callId as uint32 while ipc.Client.CONNECTION_CONTEXT_CALL_ID is signed (-3)

2013-09-16 Thread Hadoop QA (JIRA)
[ https://issues.apache.org/jira/browse/HADOOP-9944?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13768394#comment-13768394 ] Hadoop QA commented on HADOOP-9944: --- {color:red}-1 overall{color}. Here are the

[jira] [Commented] (HADOOP-9944) RpcRequestHeaderProto defines callId as uint32 while ipc.Client.CONNECTION_CONTEXT_CALL_ID is signed (-3)

2013-09-16 Thread Binglin Chang (JIRA)
[ https://issues.apache.org/jira/browse/HADOOP-9944?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13768475#comment-13768475 ] Binglin Chang commented on HADOOP-9944: --- Hi Arun, Currently change uint32 to int32

[jira] [Commented] (HADOOP-9944) RpcRequestHeaderProto defines callId as uint32 while ipc.Client.CONNECTION_CONTEXT_CALL_ID is signed (-3)

2013-09-16 Thread Hadoop QA (JIRA)
[ https://issues.apache.org/jira/browse/HADOOP-9944?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13768470#comment-13768470 ] Hadoop QA commented on HADOOP-9944: --- {color:red}-1 overall{color}. Here are the

[jira] [Commented] (HADOOP-9944) RpcRequestHeaderProto defines callId as uint32 while ipc.Client.CONNECTION_CONTEXT_CALL_ID is signed (-3)

2013-09-16 Thread Suresh Srinivas (JIRA)
[ https://issues.apache.org/jira/browse/HADOOP-9944?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13768466#comment-13768466 ] Suresh Srinivas commented on HADOOP-9944: - +1 for the new patch.

[jira] [Commented] (HADOOP-9944) RpcRequestHeaderProto defines callId as uint32 while ipc.Client.CONNECTION_CONTEXT_CALL_ID is signed (-3)

2013-09-16 Thread Suresh Srinivas (JIRA)
[ https://issues.apache.org/jira/browse/HADOOP-9944?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13768434#comment-13768434 ] Suresh Srinivas commented on HADOOP-9944: - +1 for the change.

[jira] [Commented] (HADOOP-9944) RpcRequestHeaderProto defines callId as uint32 while ipc.Client.CONNECTION_CONTEXT_CALL_ID is signed (-3)

2013-09-16 Thread Junping Du (JIRA)
[ https://issues.apache.org/jira/browse/HADOOP-9944?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13769060#comment-13769060 ] Junping Du commented on HADOOP-9944: bq. If we do permit breaking compatibility,

[jira] [Commented] (HADOOP-9944) RpcRequestHeaderProto defines callId as uint32 while ipc.Client.CONNECTION_CONTEXT_CALL_ID is signed (-3)

2013-09-16 Thread Junping Du (JIRA)
[ https://issues.apache.org/jira/browse/HADOOP-9944?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13769081#comment-13769081 ] Junping Du commented on HADOOP-9944: Forget my above comments, +1 on change from

[jira] [Commented] (HADOOP-9944) RpcRequestHeaderProto defines callId as uint32 while ipc.Client.CONNECTION_CONTEXT_CALL_ID is signed (-3)

2013-09-16 Thread Hadoop QA (JIRA)
[ https://issues.apache.org/jira/browse/HADOOP-9944?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13769111#comment-13769111 ] Hadoop QA commented on HADOOP-9944: --- {color:red}-1 overall{color}. Here are the

[jira] [Commented] (HADOOP-9944) RpcRequestHeaderProto defines callId as uint32 while ipc.Client.CONNECTION_CONTEXT_CALL_ID is signed (-3)

2013-09-16 Thread Hudson (JIRA)
[ https://issues.apache.org/jira/browse/HADOOP-9944?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13769206#comment-13769206 ] Hudson commented on HADOOP-9944: SUCCESS: Integrated in Hadoop-trunk-Commit #4428 (See

[jira] [Commented] (HADOOP-9944) RpcRequestHeaderProto defines callId as uint32 while ipc.Client.CONNECTION_CONTEXT_CALL_ID is signed (-3)

2013-09-10 Thread Binglin Chang (JIRA)
[ https://issues.apache.org/jira/browse/HADOOP-9944?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13763135#comment-13763135 ] Binglin Chang commented on HADOOP-9944: --- Hi Daryn, it is probably late to change

[jira] [Commented] (HADOOP-9944) RpcRequestHeaderProto defines callId as uint32 while ipc.Client.CONNECTION_CONTEXT_CALL_ID is signed (-3)

2013-09-10 Thread Arun C Murthy (JIRA)
[ https://issues.apache.org/jira/browse/HADOOP-9944?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13763132#comment-13763132 ] Arun C Murthy commented on HADOOP-9944: --- Yes, I think we should change it to int32

[jira] [Commented] (HADOOP-9944) RpcRequestHeaderProto defines callId as uint32 while ipc.Client.CONNECTION_CONTEXT_CALL_ID is signed (-3)

2013-09-09 Thread Daryn Sharp (JIRA)
[ https://issues.apache.org/jira/browse/HADOOP-9944?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13762118#comment-13762118 ] Daryn Sharp commented on HADOOP-9944: - There are multiple negative callIds to signal

[jira] [Commented] (HADOOP-9944) RpcRequestHeaderProto defines callId as uint32 while ipc.Client.CONNECTION_CONTEXT_CALL_ID is signed (-3)

2013-09-09 Thread Suresh Srinivas (JIRA)
[ https://issues.apache.org/jira/browse/HADOOP-9944?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13762633#comment-13762633 ] Suresh Srinivas commented on HADOOP-9944: - Making it sint32 makes sense. But this