You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@hbase.apache.org by "stack (JIRA)" <ji...@apache.org> on 2008/12/09 21:59:44 UTC

[jira] Created: (HBASE-1053) bring recent rpc changes down from hadoop

bring recent rpc changes down from hadoop
-----------------------------------------

                 Key: HBASE-1053
                 URL: https://issues.apache.org/jira/browse/HBASE-1053
             Project: Hadoop HBase
          Issue Type: Improvement
            Reporter: stack
             Fix For: 0.19.0
         Attachments: rpc.patch

Add HADOOP-4797 "RPC Server can leave a lot of direct buffers" and HADOOP-4802 "RPC Server send buffer retains size of largest response ever sent" to our rpc.  These are 0.20.0 improvements.  Bring them down so for first we have benefit of the improvement and the second, so we can undo our bringing RPC Server local when we move to 0.20.0 (having the two RPCServers look the same will make it easier undoing it).

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


[jira] Updated: (HBASE-1053) bring recent rpc changes down from hadoop

Posted by "stack (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/HBASE-1053?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

stack updated HBASE-1053:
-------------------------

    Attachment: rpc.patch

> bring recent rpc changes down from hadoop
> -----------------------------------------
>
>                 Key: HBASE-1053
>                 URL: https://issues.apache.org/jira/browse/HBASE-1053
>             Project: Hadoop HBase
>          Issue Type: Improvement
>            Reporter: stack
>             Fix For: 0.19.0
>
>         Attachments: rpc.patch
>
>
> Add HADOOP-4797 "RPC Server can leave a lot of direct buffers" and HADOOP-4802 "RPC Server send buffer retains size of largest response ever sent" to our rpc.  These are 0.20.0 improvements.  Bring them down so for first we have benefit of the improvement and the second, so we can undo our bringing RPC Server local when we move to 0.20.0 (having the two RPCServers look the same will make it easier undoing it).

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


[jira] Updated: (HBASE-1053) bring recent rpc changes down from hadoop

Posted by "stack (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/HBASE-1053?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

stack updated HBASE-1053:
-------------------------

    Resolution: Fixed
        Status: Resolved  (was: Patch Available)

Brought down HADOOP-4797.  Its in TRUNK of 0.19 but we wouldn't pick it up because we now have our own version of Hadoop RPC.

> bring recent rpc changes down from hadoop
> -----------------------------------------
>
>                 Key: HBASE-1053
>                 URL: https://issues.apache.org/jira/browse/HBASE-1053
>             Project: Hadoop HBase
>          Issue Type: Improvement
>            Reporter: stack
>             Fix For: 0.19.0
>
>         Attachments: rpc.patch
>
>
> Add HADOOP-4797 "RPC Server can leave a lot of direct buffers" and HADOOP-4802 "RPC Server send buffer retains size of largest response ever sent" to our rpc.  These are 0.20.0 improvements.  Bring them down so for first we have benefit of the improvement and the second, so we can undo our bringing RPC Server local when we move to 0.20.0 (having the two RPCServers look the same will make it easier undoing it).

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


[jira] Assigned: (HBASE-1053) bring recent rpc changes down from hadoop

Posted by "stack (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/HBASE-1053?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

stack reassigned HBASE-1053:
----------------------------

    Assignee: stack

> bring recent rpc changes down from hadoop
> -----------------------------------------
>
>                 Key: HBASE-1053
>                 URL: https://issues.apache.org/jira/browse/HBASE-1053
>             Project: Hadoop HBase
>          Issue Type: Improvement
>            Reporter: stack
>            Assignee: stack
>             Fix For: 0.19.0
>
>         Attachments: rpc.patch
>
>
> Add HADOOP-4797 "RPC Server can leave a lot of direct buffers" and HADOOP-4802 "RPC Server send buffer retains size of largest response ever sent" to our rpc.  These are 0.20.0 improvements.  Bring them down so for first we have benefit of the improvement and the second, so we can undo our bringing RPC Server local when we move to 0.20.0 (having the two RPCServers look the same will make it easier undoing it).

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


[jira] Updated: (HBASE-1053) bring recent rpc changes down from hadoop

Posted by "stack (JIRA)" <ji...@apache.org>.
     [ https://issues.apache.org/jira/browse/HBASE-1053?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

stack updated HBASE-1053:
-------------------------

    Status: Patch Available  (was: Open)

> bring recent rpc changes down from hadoop
> -----------------------------------------
>
>                 Key: HBASE-1053
>                 URL: https://issues.apache.org/jira/browse/HBASE-1053
>             Project: Hadoop HBase
>          Issue Type: Improvement
>            Reporter: stack
>             Fix For: 0.19.0
>
>         Attachments: rpc.patch
>
>
> Add HADOOP-4797 "RPC Server can leave a lot of direct buffers" and HADOOP-4802 "RPC Server send buffer retains size of largest response ever sent" to our rpc.  These are 0.20.0 improvements.  Bring them down so for first we have benefit of the improvement and the second, so we can undo our bringing RPC Server local when we move to 0.20.0 (having the two RPCServers look the same will make it easier undoing it).

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.