hbase-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ted Yu (Commented) (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HBASE-3581) hbase rpc should send size of response
Date Tue, 18 Oct 2011 18:39:10 GMT

    [ https://issues.apache.org/jira/browse/HBASE-3581?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13129922#comment-13129922
] 

Ted Yu commented on HBASE-3581:
-------------------------------

TestMultiParallel#testFlushCommitsWithAbort hangs on MacBook.

I see this in output:
{code}
2011-10-18 10:55:39,063 INFO  [Thread-333] client.TestMultiParallel(231): Aborted=10.246.204.195,60919,1318960526880
2011-10-18 10:55:39,081 WARN  [IPC Client (47) connection to /10.246.204.195:60919 from an
unknown user] ipc.HBaseClient$Connection(493): Unexpected exception receiving call responses
java.lang.NullPointerException
        at org.apache.hadoop.hbase.io.HbaseObjectWritable.readObject(HbaseObjectWritable.java:522)
        at org.apache.hadoop.hbase.io.HbaseObjectWritable.readFields(HbaseObjectWritable.java:296)
        at org.apache.hadoop.hbase.ipc.HBaseClient$Connection.receiveResponse(HBaseClient.java:575)
        at org.apache.hadoop.hbase.ipc.HBaseClient$Connection.run(HBaseClient.java:490)
{code}
                
> hbase rpc should send size of response
> --------------------------------------
>
>                 Key: HBASE-3581
>                 URL: https://issues.apache.org/jira/browse/HBASE-3581
>             Project: HBase
>          Issue Type: Improvement
>            Reporter: ryan rawson
>            Assignee: stack
>            Priority: Critical
>             Fix For: 0.92.0
>
>         Attachments: 3581-v2.txt, 3581-v3.txt, 3581-v4.txt, HBASE-rpc-response.txt
>
>
> The RPC reply from Server->Client does not include the size of the payload, it is
framed like so:
> <i32> callId
> <byte> errorFlag
> <byte[]> data
> The data segment would contain enough info about how big the response is so that it could
be decoded by a writable reader.
> This makes it difficult to write buffering clients, who might read the entire 'data'
then pass it to a decoder. While less memory efficient, if you want to easily write block
read clients (eg: nio) it would be necessary to send the size along so that the client could
snarf into a local buf.
> The new proposal is:
> <i32> callId
> <i32> size
> <byte> errorFlag
> <byte[]> data
> the size being sizeof(data) + sizeof(errorFlag).

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message