You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@avro.apache.org by "Jeff Hammerbacher (JIRA)" <ji...@apache.org> on 2010/05/22 03:48:16 UTC
[jira] Created: (AVRO-548) Investigate why Python client feels need
to send message twice to Java server once protocol has been cached
Investigate why Python client feels need to send message twice to Java server once protocol has been cached
-----------------------------------------------------------------------------------------------------------
Key: AVRO-548
URL: https://issues.apache.org/jira/browse/AVRO-548
Project: Avro
Issue Type: Bug
Components: java, python
Reporter: Jeff Hammerbacher
Assignee: Jeff Hammerbacher
In building the Avro server and client for HBase (see http://github.com/hammer/hbase-trunk-with-avro), I've come across a bug where my first RPC from client to server behaves nicely, but the second message sent will create two RPCs between the client and server. Not sure if the client or server is at fault, but this JIRA will document my investigations.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (AVRO-548) Python client should handle CLIENT
handshake match status correctly
Posted by "Jeff Hammerbacher (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AVRO-548?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jeff Hammerbacher updated AVRO-548:
-----------------------------------
Summary: Python client should handle CLIENT handshake match status correctly (was: Investigate why Python client feels need to send message twice to Java server once protocol has been cached)
Description:
In building the Avro server and client for HBase (see http://github.com/hammer/hbase-trunk-with-avro), I've come across a bug where my first RPC from client to server behaves nicely, but the second message sent will create two RPCs between the client and server. Not sure if the client or server is at fault, but this JIRA will document my investigations.
Further investigations have shown that the issue was incorrect handling of the CLIENT match in the handshake. We were telling the requestor that no response was present; in fact, a response is present, and should be processed as a result of the request.
was:In building the Avro server and client for HBase (see http://github.com/hammer/hbase-trunk-with-avro), I've come across a bug where my first RPC from client to server behaves nicely, but the second message sent will create two RPCs between the client and server. Not sure if the client or server is at fault, but this JIRA will document my investigations.
> Python client should handle CLIENT handshake match status correctly
> -------------------------------------------------------------------
>
> Key: AVRO-548
> URL: https://issues.apache.org/jira/browse/AVRO-548
> Project: Avro
> Issue Type: Bug
> Components: java, python
> Reporter: Jeff Hammerbacher
> Assignee: Jeff Hammerbacher
>
> In building the Avro server and client for HBase (see http://github.com/hammer/hbase-trunk-with-avro), I've come across a bug where my first RPC from client to server behaves nicely, but the second message sent will create two RPCs between the client and server. Not sure if the client or server is at fault, but this JIRA will document my investigations.
> Further investigations have shown that the issue was incorrect handling of the CLIENT match in the handshake. We were telling the requestor that no response was present; in fact, a response is present, and should be processed as a result of the request.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (AVRO-548) Python client should handle CLIENT
handshake match status correctly
Posted by "Doug Cutting (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AVRO-548?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12870747#action_12870747 ]
Doug Cutting commented on AVRO-548:
-----------------------------------
Jeff, is it possible to add a test that would have detected the problem?
> Python client should handle CLIENT handshake match status correctly
> -------------------------------------------------------------------
>
> Key: AVRO-548
> URL: https://issues.apache.org/jira/browse/AVRO-548
> Project: Avro
> Issue Type: Bug
> Components: java, python
> Reporter: Jeff Hammerbacher
> Assignee: Jeff Hammerbacher
> Attachments: AVRO-548.patch
>
>
> In building the Avro server and client for HBase (see http://github.com/hammer/hbase-trunk-with-avro), I've come across a bug where my first RPC from client to server behaves nicely, but the second message sent will create two RPCs between the client and server. Not sure if the client or server is at fault, but this JIRA will document my investigations.
> Further investigations have shown that the issue was incorrect handling of the CLIENT match in the handshake. We were telling the requestor that no response was present; in fact, a response is present, and should be processed as a result of the request.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (AVRO-548) Investigate why Python client feels
need to send message twice to Java server once protocol has been cached
Posted by "Jeff Hammerbacher (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AVRO-548?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12870267#action_12870267 ]
Jeff Hammerbacher commented on AVRO-548:
----------------------------------------
Poking around at http://github.com/hammer/avro-548/ to diagnose this one.
> Investigate why Python client feels need to send message twice to Java server once protocol has been cached
> -----------------------------------------------------------------------------------------------------------
>
> Key: AVRO-548
> URL: https://issues.apache.org/jira/browse/AVRO-548
> Project: Avro
> Issue Type: Bug
> Components: java, python
> Reporter: Jeff Hammerbacher
> Assignee: Jeff Hammerbacher
>
> In building the Avro server and client for HBase (see http://github.com/hammer/hbase-trunk-with-avro), I've come across a bug where my first RPC from client to server behaves nicely, but the second message sent will create two RPCs between the client and server. Not sure if the client or server is at fault, but this JIRA will document my investigations.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (AVRO-548) Python client should handle CLIENT
handshake match status correctly
Posted by "Jeff Hammerbacher (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AVRO-548?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12870827#action_12870827 ]
Jeff Hammerbacher commented on AVRO-548:
----------------------------------------
Doug: see AVRO-333. If I get time I'll try to get this into 1.3.3, otherwise it will have to wait until 1.4.0. I'm traveling right now and don't have tons of time to page in the testing infrastructure for RPCs and write a new test, but I want to make sure clients don't have this bug ASAP.
> Python client should handle CLIENT handshake match status correctly
> -------------------------------------------------------------------
>
> Key: AVRO-548
> URL: https://issues.apache.org/jira/browse/AVRO-548
> Project: Avro
> Issue Type: Bug
> Components: java, python
> Reporter: Jeff Hammerbacher
> Assignee: Jeff Hammerbacher
> Attachments: AVRO-548.patch
>
>
> In building the Avro server and client for HBase (see http://github.com/hammer/hbase-trunk-with-avro), I've come across a bug where my first RPC from client to server behaves nicely, but the second message sent will create two RPCs between the client and server. Not sure if the client or server is at fault, but this JIRA will document my investigations.
> Further investigations have shown that the issue was incorrect handling of the CLIENT match in the handshake. We were telling the requestor that no response was present; in fact, a response is present, and should be processed as a result of the request.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (AVRO-548) Python client should handle CLIENT
handshake match status correctly
Posted by "Jeff Hammerbacher (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AVRO-548?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jeff Hammerbacher updated AVRO-548:
-----------------------------------
Fix Version/s: 1.3.3
Merged into branch-1.3 with revision 950155.
> Python client should handle CLIENT handshake match status correctly
> -------------------------------------------------------------------
>
> Key: AVRO-548
> URL: https://issues.apache.org/jira/browse/AVRO-548
> Project: Avro
> Issue Type: Bug
> Components: java, python
> Reporter: Jeff Hammerbacher
> Assignee: Jeff Hammerbacher
> Fix For: 1.3.3
>
> Attachments: AVRO-548.patch
>
>
> In building the Avro server and client for HBase (see http://github.com/hammer/hbase-trunk-with-avro), I've come across a bug where my first RPC from client to server behaves nicely, but the second message sent will create two RPCs between the client and server. Not sure if the client or server is at fault, but this JIRA will document my investigations.
> Further investigations have shown that the issue was incorrect handling of the CLIENT match in the handshake. We were telling the requestor that no response was present; in fact, a response is present, and should be processed as a result of the request.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Resolved: (AVRO-548) Python client should handle CLIENT
handshake match status correctly
Posted by "Jeff Hammerbacher (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AVRO-548?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jeff Hammerbacher resolved AVRO-548.
------------------------------------
Resolution: Fixed
Committed revision 947586.
> Python client should handle CLIENT handshake match status correctly
> -------------------------------------------------------------------
>
> Key: AVRO-548
> URL: https://issues.apache.org/jira/browse/AVRO-548
> Project: Avro
> Issue Type: Bug
> Components: java, python
> Reporter: Jeff Hammerbacher
> Assignee: Jeff Hammerbacher
> Attachments: AVRO-548.patch
>
>
> In building the Avro server and client for HBase (see http://github.com/hammer/hbase-trunk-with-avro), I've come across a bug where my first RPC from client to server behaves nicely, but the second message sent will create two RPCs between the client and server. Not sure if the client or server is at fault, but this JIRA will document my investigations.
> Further investigations have shown that the issue was incorrect handling of the CLIENT match in the handshake. We were telling the requestor that no response was present; in fact, a response is present, and should be processed as a result of the request.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (AVRO-548) Python client should handle CLIENT
handshake match status correctly
Posted by "Jeff Hammerbacher (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AVRO-548?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jeff Hammerbacher updated AVRO-548:
-----------------------------------
Component/s: (was: java)
> Python client should handle CLIENT handshake match status correctly
> -------------------------------------------------------------------
>
> Key: AVRO-548
> URL: https://issues.apache.org/jira/browse/AVRO-548
> Project: Avro
> Issue Type: Bug
> Components: python
> Reporter: Jeff Hammerbacher
> Assignee: Jeff Hammerbacher
> Fix For: 1.3.3
>
> Attachments: AVRO-548.patch
>
>
> In building the Avro server and client for HBase (see http://github.com/hammer/hbase-trunk-with-avro), I've come across a bug where my first RPC from client to server behaves nicely, but the second message sent will create two RPCs between the client and server. Not sure if the client or server is at fault, but this JIRA will document my investigations.
> Further investigations have shown that the issue was incorrect handling of the CLIENT match in the handshake. We were telling the requestor that no response was present; in fact, a response is present, and should be processed as a result of the request.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (AVRO-548) Python client should handle CLIENT
handshake match status correctly
Posted by "Jeff Hammerbacher (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AVRO-548?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jeff Hammerbacher updated AVRO-548:
-----------------------------------
Attachment: AVRO-548.patch
> Python client should handle CLIENT handshake match status correctly
> -------------------------------------------------------------------
>
> Key: AVRO-548
> URL: https://issues.apache.org/jira/browse/AVRO-548
> Project: Avro
> Issue Type: Bug
> Components: java, python
> Reporter: Jeff Hammerbacher
> Assignee: Jeff Hammerbacher
> Attachments: AVRO-548.patch
>
>
> In building the Avro server and client for HBase (see http://github.com/hammer/hbase-trunk-with-avro), I've come across a bug where my first RPC from client to server behaves nicely, but the second message sent will create two RPCs between the client and server. Not sure if the client or server is at fault, but this JIRA will document my investigations.
> Further investigations have shown that the issue was incorrect handling of the CLIENT match in the handshake. We were telling the requestor that no response was present; in fact, a response is present, and should be processed as a result of the request.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.