Details

    • Type: Improvement Improvement
    • Status: Resolved
    • Priority: Major Major
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 0.90.0
    • Component/s: None
    • Labels:
      None
    • Hadoop Flags:
      Reviewed
    • Release Note:
      Adds a timeout for client-side RPC. Default to 60 seconds. Change by adding hbase.rpc.timeout to hbase-site.xml and setting timeout in milliseconds.

      Description

      We see a client stuck at an RPC to a zombie RS. HBase RPC should support timeout.

      "IPC Client (47) connection to msgstore179.ash2.facebook.com/10.138.89.182:60020 from an unknown user" daemon prio=10 tid=0x00007f554c5ab800 nid=0x5df3 runnable [0x00000000590d4000]
      java.lang.Thread.State: RUNNABLE
      at sun.nio.ch.EPollArrayWrapper.epollWait(Native Method)
      at sun.nio.ch.EPollArrayWrapper.poll(EPollArrayWrapper.java:215)
      at sun.nio.ch.EPollSelectorImpl.doSelect(EPollSelectorImpl.java:65)
      at sun.nio.ch.SelectorImpl.lockAndDoSelect(SelectorImpl.java:69)

      • locked <0x00007f5aa402a9e8> (a sun.nio.ch.Util$1)
      • locked <0x00007f5aa402aac0> (a java.util.Collections$UnmodifiableSet)
      • locked <0x00007f596a398408> (a sun.nio.ch.EPollSelectorImpl)
        at sun.nio.ch.SelectorImpl.select(SelectorImpl.java:80)
        at org.apache.hadoop.net.SocketIOWithTimeout$SelectorPool.select(SocketIOWithTimeout.java:332)
        at org.apache.hadoop.net.SocketIOWithTimeout.doIO(SocketIOWithTimeout.java:157)
        at org.apache.hadoop.net.SocketInputStream.read(SocketInputStream.java:155)
        at org.apache.hadoop.net.SocketInputStream.read(SocketInputStream.java:128)
        at java.io.FilterInputStream.read(FilterInputStream.java:116)
        at org.apache.hadoop.hbase.ipc.HBaseClient$Connection$PingInputStream.read(HBaseClient.java:279)
        at java.io.BufferedInputStream.fill(BufferedInputStream.java:218)
        at java.io.BufferedInputStream.read(BufferedInputStream.java:237)
      • locked <0x00007f5a1d7e7bd8> (a java.io.BufferedInputStream)
        at java.io.DataInputStream.readInt(DataInputStream.java:370)
        at org.apache.hadoop.hbase.ipc.HBaseClient$Connection.receiveResponse(HBaseClient.java:514)
        at org.apache.hadoop.hbase.ipc.HBaseClient$Connection.run(HBaseClient.java:454)

        Activity

        Hide
        stack added a comment -

        This is a client-side timeout. Its default is 60 seconds.

        Show
        stack added a comment - This is a client-side timeout. Its default is 60 seconds.
        Hide
        stack added a comment -

        This is what it looks like on server-side:

        2011-03-23 16:37:08,498 WARN org.apache.hadoop.ipc.HBaseServer: IPC Server Responder, call multi(org.apache.hadoop.hbase.client.MultiAction@6db16bc) from 10.4.8.34:42287: output error
        2011-03-23 16:37:08,498 WARN org.apache.hadoop.ipc.HBaseServer: IPC Server handler 9 on 61020 caught: java.nio.channels.ClosedChannelException
            at sun.nio.ch.SocketChannelImpl.ensureWriteOpen(SocketChannelImpl.java:133)
            at sun.nio.ch.SocketChannelImpl.write(SocketChannelImpl.java:324)
            at org.apache.hadoop.hbase.ipc.HBaseServer.channelIO(HBaseServer.java:1387)
            at org.apache.hadoop.hbase.ipc.HBaseServer.channelWrite(HBaseServer.java:1339)
            at org.apache.hadoop.hbase.ipc.HBaseServer$Responder.processResponse(HBaseServer.java:727)
            at org.apache.hadoop.hbase.ipc.HBaseServer$Responder.doRespond(HBaseServer.java:792)
            at org.apache.hadoop.hbase.ipc.HBaseServer$Handler.run(HBaseServer.java:1083)
        
        2011-03-23 16:37:08,515 WARN org.apache.hadoop.ipc.HBaseServer: IPC Server Responder, call multi(org.apache.hadoop.hbase.client.MultiAction@5754a4a7) from 10.4.8.34:42287: output error
        2011-03-23 16:37:08,516 WARN org.apache.hadoop.ipc.HBaseServer: IPC Server handler 0 on 61020 caught: java.nio.channels.ClosedChannelException
            at sun.nio.ch.SocketChannelImpl.ensureWriteOpen(SocketChannelImpl.java:133)
            at sun.nio.ch.SocketChannelImpl.write(SocketChannelImpl.java:324)
            at org.apache.hadoop.hbase.ipc.HBaseServer.channelIO(HBaseServer.java:1387)
            at org.apache.hadoop.hbase.ipc.HBaseServer.channelWrite(HBaseServer.java:1339)
            at org.apache.hadoop.hbase.ipc.HBaseServer$Responder.processResponse(HBaseServer.java:727)
            at org.apache.hadoop.hbase.ipc.HBaseServer$Responder.doRespond(HBaseServer.java:792)
            at org.apache.hadoop.hbase.ipc.HBaseServer$Handler.run(HBaseServer.java:1083)
        

        On client side it looks like this:

        11/03/23 17:03:16 DEBUG client.HConnectionManager$HConnectionImplementation: Failed all from sv4borg230:61020
        java.util.concurrent.ExecutionException: java.net.SocketTimeoutException: Call to sv4borg230/10.4.12.34:61020 failed on socket timeout exception: java.net.SocketTimeoutException: 1000 millis timeout while waiting for channel to
                at java.util.concurrent.FutureTask$Sync.innerGet(FutureTask.java:222)
                at java.util.concurrent.FutureTask.get(FutureTask.java:83)
                at org.apache.hadoop.hbase.client.HConnectionManager$HConnectionImplementation.processBatch(HConnectionManager.java:1158)
                at org.apache.hadoop.hbase.client.HConnectionManager$HConnectionImplementation.processBatchOfPuts(HConnectionManager.java:1246)
                at org.apache.hadoop.hbase.client.HTable.flushCommits(HTable.java:822)
                at org.apache.hadoop.hbase.client.HTable.doPut(HTable.java:678)
                at org.apache.hadoop.hbase.client.HTable.put(HTable.java:663)
                at com.yahoo.ycsb.db.HBaseClient.update(HBaseClient.java:316)
                at com.yahoo.ycsb.db.HBaseClient.insert(HBaseClient.java:390)
                at com.yahoo.ycsb.DBWrapper.insert(DBWrapper.java:155)
                at com.yahoo.ycsb.workloads.CoreWorkload.doInsert(CoreWorkload.java:372)
                at com.yahoo.ycsb.ClientThread.run(Client.java:251)
        Caused by: java.net.SocketTimeoutException: Call to sv4borg230/10.4.12.34:61020 failed on socket timeout exception: java.net.SocketTimeoutException: 1000 millis timeout while waiting for channel to be ready for read. ch : java.
                at org.apache.hadoop.hbase.ipc.HBaseClient.wrapException(HBaseClient.java:802)
                at org.apache.hadoop.hbase.ipc.HBaseClient.call(HBaseClient.java:775)
                at org.apache.hadoop.hbase.ipc.HBaseRPC$Invoker.invoke(HBaseRPC.java:257)
                at $Proxy5.multi(Unknown Source)
                at org.apache.hadoop.hbase.client.HConnectionManager$HConnectionImplementation$4$1.call(HConnectionManager.java:1078)
                at org.apache.hadoop.hbase.client.HConnectionManager$HConnectionImplementation$4$1.call(HConnectionManager.java:1076)
                at org.apache.hadoop.hbase.client.HConnectionManager$HConnectionImplementation.getRegionServerWithoutRetries(HConnectionManager.java:1035)
                at org.apache.hadoop.hbase.client.HConnectionManager$HConnectionImplementation$4.call(HConnectionManager.java:1075)
                at org.apache.hadoop.hbase.client.HConnectionManager$HConnectionImplementation$4.call(HConnectionManager.java:1073)
                at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
                at java.util.concurrent.FutureTask.run(FutureTask.java:138)
                at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
                at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
                at java.lang.Thread.run(Thread.java:662)
        Caused by: java.net.SocketTimeoutException: 1000 millis timeout while waiting for channel to be ready for read. ch : java.nio.channels.SocketChannel[connected local=/10.4.8.34:37568 remote=sv4borg230/10.4.12.34:61020]
                at org.apache.hadoop.net.SocketIOWithTimeout.doIO(SocketIOWithTimeout.java:164)
                at org.apache.hadoop.net.SocketInputStream.read(SocketInputStream.java:155)
                at org.apache.hadoop.net.SocketInputStream.read(SocketInputStream.java:128)
                at java.io.FilterInputStream.read(FilterInputStream.java:116)
                at org.apache.hadoop.hbase.ipc.HBaseClient$Connection$PingInputStream.read(HBaseClient.java:299)
                at java.io.BufferedInputStream.fill(BufferedInputStream.java:218)
                at java.io.BufferedInputStream.read(BufferedInputStream.java:237)
                at java.io.DataInputStream.readInt(DataInputStream.java:370)
                at org.apache.hadoop.hbase.ipc.HBaseClient$Connection.receiveResponse(HBaseClient.java:539)
                at org.apache.hadoop.hbase.ipc.HBaseClient$Connection.run(HBaseClient.java:477)
        
        Show
        stack added a comment - This is what it looks like on server-side: 2011-03-23 16:37:08,498 WARN org.apache.hadoop.ipc.HBaseServer: IPC Server Responder, call multi(org.apache.hadoop.hbase.client.MultiAction@6db16bc) from 10.4.8.34:42287: output error 2011-03-23 16:37:08,498 WARN org.apache.hadoop.ipc.HBaseServer: IPC Server handler 9 on 61020 caught: java.nio.channels.ClosedChannelException at sun.nio.ch.SocketChannelImpl.ensureWriteOpen(SocketChannelImpl.java:133) at sun.nio.ch.SocketChannelImpl.write(SocketChannelImpl.java:324) at org.apache.hadoop.hbase.ipc.HBaseServer.channelIO(HBaseServer.java:1387) at org.apache.hadoop.hbase.ipc.HBaseServer.channelWrite(HBaseServer.java:1339) at org.apache.hadoop.hbase.ipc.HBaseServer$Responder.processResponse(HBaseServer.java:727) at org.apache.hadoop.hbase.ipc.HBaseServer$Responder.doRespond(HBaseServer.java:792) at org.apache.hadoop.hbase.ipc.HBaseServer$Handler.run(HBaseServer.java:1083) 2011-03-23 16:37:08,515 WARN org.apache.hadoop.ipc.HBaseServer: IPC Server Responder, call multi(org.apache.hadoop.hbase.client.MultiAction@5754a4a7) from 10.4.8.34:42287: output error 2011-03-23 16:37:08,516 WARN org.apache.hadoop.ipc.HBaseServer: IPC Server handler 0 on 61020 caught: java.nio.channels.ClosedChannelException at sun.nio.ch.SocketChannelImpl.ensureWriteOpen(SocketChannelImpl.java:133) at sun.nio.ch.SocketChannelImpl.write(SocketChannelImpl.java:324) at org.apache.hadoop.hbase.ipc.HBaseServer.channelIO(HBaseServer.java:1387) at org.apache.hadoop.hbase.ipc.HBaseServer.channelWrite(HBaseServer.java:1339) at org.apache.hadoop.hbase.ipc.HBaseServer$Responder.processResponse(HBaseServer.java:727) at org.apache.hadoop.hbase.ipc.HBaseServer$Responder.doRespond(HBaseServer.java:792) at org.apache.hadoop.hbase.ipc.HBaseServer$Handler.run(HBaseServer.java:1083) On client side it looks like this: 11/03/23 17:03:16 DEBUG client.HConnectionManager$HConnectionImplementation: Failed all from sv4borg230:61020 java.util.concurrent.ExecutionException: java.net.SocketTimeoutException: Call to sv4borg230/10.4.12.34:61020 failed on socket timeout exception: java.net.SocketTimeoutException: 1000 millis timeout while waiting for channel to at java.util.concurrent.FutureTask$Sync.innerGet(FutureTask.java:222) at java.util.concurrent.FutureTask.get(FutureTask.java:83) at org.apache.hadoop.hbase.client.HConnectionManager$HConnectionImplementation.processBatch(HConnectionManager.java:1158) at org.apache.hadoop.hbase.client.HConnectionManager$HConnectionImplementation.processBatchOfPuts(HConnectionManager.java:1246) at org.apache.hadoop.hbase.client.HTable.flushCommits(HTable.java:822) at org.apache.hadoop.hbase.client.HTable.doPut(HTable.java:678) at org.apache.hadoop.hbase.client.HTable.put(HTable.java:663) at com.yahoo.ycsb.db.HBaseClient.update(HBaseClient.java:316) at com.yahoo.ycsb.db.HBaseClient.insert(HBaseClient.java:390) at com.yahoo.ycsb.DBWrapper.insert(DBWrapper.java:155) at com.yahoo.ycsb.workloads.CoreWorkload.doInsert(CoreWorkload.java:372) at com.yahoo.ycsb.ClientThread.run(Client.java:251) Caused by: java.net.SocketTimeoutException: Call to sv4borg230/10.4.12.34:61020 failed on socket timeout exception: java.net.SocketTimeoutException: 1000 millis timeout while waiting for channel to be ready for read. ch : java. at org.apache.hadoop.hbase.ipc.HBaseClient.wrapException(HBaseClient.java:802) at org.apache.hadoop.hbase.ipc.HBaseClient.call(HBaseClient.java:775) at org.apache.hadoop.hbase.ipc.HBaseRPC$Invoker.invoke(HBaseRPC.java:257) at $Proxy5.multi(Unknown Source) at org.apache.hadoop.hbase.client.HConnectionManager$HConnectionImplementation$4$1.call(HConnectionManager.java:1078) at org.apache.hadoop.hbase.client.HConnectionManager$HConnectionImplementation$4$1.call(HConnectionManager.java:1076) at org.apache.hadoop.hbase.client.HConnectionManager$HConnectionImplementation.getRegionServerWithoutRetries(HConnectionManager.java:1035) at org.apache.hadoop.hbase.client.HConnectionManager$HConnectionImplementation$4.call(HConnectionManager.java:1075) at org.apache.hadoop.hbase.client.HConnectionManager$HConnectionImplementation$4.call(HConnectionManager.java:1073) at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303) at java.util.concurrent.FutureTask.run(FutureTask.java:138) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) at java.lang. Thread .run( Thread .java:662) Caused by: java.net.SocketTimeoutException: 1000 millis timeout while waiting for channel to be ready for read. ch : java.nio.channels.SocketChannel[connected local=/10.4.8.34:37568 remote=sv4borg230/10.4.12.34:61020] at org.apache.hadoop.net.SocketIOWithTimeout.doIO(SocketIOWithTimeout.java:164) at org.apache.hadoop.net.SocketInputStream.read(SocketInputStream.java:155) at org.apache.hadoop.net.SocketInputStream.read(SocketInputStream.java:128) at java.io.FilterInputStream.read(FilterInputStream.java:116) at org.apache.hadoop.hbase.ipc.HBaseClient$Connection$PingInputStream.read(HBaseClient.java:299) at java.io.BufferedInputStream.fill(BufferedInputStream.java:218) at java.io.BufferedInputStream.read(BufferedInputStream.java:237) at java.io.DataInputStream.readInt(DataInputStream.java:370) at org.apache.hadoop.hbase.ipc.HBaseClient$Connection.receiveResponse(HBaseClient.java:539) at org.apache.hadoop.hbase.ipc.HBaseClient$Connection.run(HBaseClient.java:477)
        Hide
        stack added a comment -

        Our sense is that they wouldn't take this messy hackup (smile).

        Show
        stack added a comment - Our sense is that they wouldn't take this messy hackup (smile).
        Hide
        Hairong Kuang added a comment -

        > there is also a push to reunify with hadoop rpc...
        +1 on this! HBase should contribute your optimizations back to Hadoop.

        Show
        Hairong Kuang added a comment - > there is also a push to reunify with hadoop rpc... +1 on this! HBase should contribute your optimizations back to Hadoop.
        Hide
        Jonathan Gray added a comment -

        Committed to trunk. Thanks Hairong! Thanks for review stack.

        Show
        Jonathan Gray added a comment - Committed to trunk. Thanks Hairong! Thanks for review stack.
        Hide
        HBase Review Board added a comment -

        Message from: stack@duboce.net

        -----------------------------------------------------------
        This is an automatically generated e-mail. To reply, visit:
        http://review.cloudera.org/r/1142/#review1752
        -----------------------------------------------------------

        Ship it!

        +1 on commit because of Hairong remarks up in issue.

        • stack
        Show
        HBase Review Board added a comment - Message from: stack@duboce.net ----------------------------------------------------------- This is an automatically generated e-mail. To reply, visit: http://review.cloudera.org/r/1142/#review1752 ----------------------------------------------------------- Ship it! +1 on commit because of Hairong remarks up in issue. stack
        Hide
        stack added a comment -

        Thanks Hairong.

        HBase and Hadoop RPC diverge in a few places mostly for performance reasons; e..g. we send a code rather than method name so we don't have to pass a bunch of Text with attendant expensive (String decoding) deserialization.

        The differences are being monitored by one of the lads – he wants to make our rpc switchable so can slot in hadoop's 'secure' rpc optionally – and there is also a push to reunify with hadoop rpc... we just need to do a bit of measuring to make sure we don't lose a bunch of perf switching back.

        Show
        stack added a comment - Thanks Hairong. HBase and Hadoop RPC diverge in a few places mostly for performance reasons; e..g. we send a code rather than method name so we don't have to pass a bunch of Text with attendant expensive (String decoding) deserialization. The differences are being monitored by one of the lads – he wants to make our rpc switchable so can slot in hadoop's 'secure' rpc optionally – and there is also a push to reunify with hadoop rpc... we just need to do a bit of measuring to make sure we don't lose a bunch of perf switching back.
        Hide
        Hairong Kuang added a comment -

        I put the same change to HDFS and had a unit test there.

        For HBase, both Kannan and I tested manually.

        BTW, why doesn't HBase simply use Hadoop RPC. The code in both projects are almost the same. Maintaining the code in both places is a lot of overhead.

        Show
        Hairong Kuang added a comment - I put the same change to HDFS and had a unit test there. For HBase, both Kannan and I tested manually. BTW, why doesn't HBase simply use Hadoop RPC. The code in both projects are almost the same. Maintaining the code in both places is a lot of overhead.
        Hide
        HBase Review Board added a comment -

        Message from: stack@duboce.net

        -----------------------------------------------------------
        This is an automatically generated e-mail. To reply, visit:
        http://review.cloudera.org/r/1142/#review1745
        -----------------------------------------------------------

        This looks right. Does it work? There is no test. I put it up on my little cluster and stuff still works so its not breaking anything.

        • stack
        Show
        HBase Review Board added a comment - Message from: stack@duboce.net ----------------------------------------------------------- This is an automatically generated e-mail. To reply, visit: http://review.cloudera.org/r/1142/#review1745 ----------------------------------------------------------- This looks right. Does it work? There is no test. I put it up on my little cluster and stuff still works so its not breaking anything. stack
        Hide
        HBase Review Board added a comment -

        Message from: "Jonathan Gray" <jgray@apache.org>

        -----------------------------------------------------------
        This is an automatically generated e-mail. To reply, visit:
        http://review.cloudera.org/r/1142/
        -----------------------------------------------------------

        (Updated 2010-10-31 12:45:13.758266)

        Review request for hbase, stack and Kannan Muthukkaruppan.

        Changes
        -------

        Just whitespace cleanup

        Summary
        -------

        This patch is from Hairong. Just helping out by putting it up on RB.

        This adds a global, configurable timeout for all HBase RPCs. Uses new config parameter 'hbase.rpc.timeout' rather than overloading the lease period.

        This addresses bug HBASE-3154.
        http://issues.apache.org/jira/browse/HBASE-3154

        Diffs (updated)


        trunk/src/main/java/org/apache/hadoop/hbase/HConstants.java 1029423
        trunk/src/main/java/org/apache/hadoop/hbase/client/HConnectionManager.java 1029423
        trunk/src/main/java/org/apache/hadoop/hbase/ipc/HBaseClient.java 1029423
        trunk/src/main/java/org/apache/hadoop/hbase/ipc/HBaseRPC.java 1029423
        trunk/src/main/java/org/apache/hadoop/hbase/regionserver/HRegionServer.java 1029423

        Diff: http://review.cloudera.org/r/1142/diff

        Testing
        -------

        Not actually sure. I know that we've committed this internally at FB and I think Hairong did testing on it.

        Thanks,

        Jonathan

        Show
        HBase Review Board added a comment - Message from: "Jonathan Gray" <jgray@apache.org> ----------------------------------------------------------- This is an automatically generated e-mail. To reply, visit: http://review.cloudera.org/r/1142/ ----------------------------------------------------------- (Updated 2010-10-31 12:45:13.758266) Review request for hbase, stack and Kannan Muthukkaruppan. Changes ------- Just whitespace cleanup Summary ------- This patch is from Hairong. Just helping out by putting it up on RB. This adds a global, configurable timeout for all HBase RPCs. Uses new config parameter 'hbase.rpc.timeout' rather than overloading the lease period. This addresses bug HBASE-3154 . http://issues.apache.org/jira/browse/HBASE-3154 Diffs (updated) trunk/src/main/java/org/apache/hadoop/hbase/HConstants.java 1029423 trunk/src/main/java/org/apache/hadoop/hbase/client/HConnectionManager.java 1029423 trunk/src/main/java/org/apache/hadoop/hbase/ipc/HBaseClient.java 1029423 trunk/src/main/java/org/apache/hadoop/hbase/ipc/HBaseRPC.java 1029423 trunk/src/main/java/org/apache/hadoop/hbase/regionserver/HRegionServer.java 1029423 Diff: http://review.cloudera.org/r/1142/diff Testing ------- Not actually sure. I know that we've committed this internally at FB and I think Hairong did testing on it. Thanks, Jonathan
        Hide
        HBase Review Board added a comment -

        Message from: "Jonathan Gray" <jgray@apache.org>

        -----------------------------------------------------------
        This is an automatically generated e-mail. To reply, visit:
        http://review.cloudera.org/r/1142/
        -----------------------------------------------------------

        Review request for hbase, stack and Kannan Muthukkaruppan.

        Summary
        -------

        This patch is from Hairong. Just helping out by putting it up on RB.

        This adds a global, configurable timeout for all HBase RPCs. Uses new config parameter 'hbase.rpc.timeout' rather than overloading the lease period.

        This addresses bug HBASE-3154.
        http://issues.apache.org/jira/browse/HBASE-3154

        Diffs


        trunk/src/main/java/org/apache/hadoop/hbase/HConstants.java 1029423
        trunk/src/main/java/org/apache/hadoop/hbase/client/HConnectionManager.java 1029423
        trunk/src/main/java/org/apache/hadoop/hbase/ipc/HBaseClient.java 1029423
        trunk/src/main/java/org/apache/hadoop/hbase/ipc/HBaseRPC.java 1029423
        trunk/src/main/java/org/apache/hadoop/hbase/regionserver/HRegionServer.java 1029423

        Diff: http://review.cloudera.org/r/1142/diff

        Testing
        -------

        Not actually sure. I know that we've committed this internally at FB and I think Hairong did testing on it.

        Thanks,

        Jonathan

        Show
        HBase Review Board added a comment - Message from: "Jonathan Gray" <jgray@apache.org> ----------------------------------------------------------- This is an automatically generated e-mail. To reply, visit: http://review.cloudera.org/r/1142/ ----------------------------------------------------------- Review request for hbase, stack and Kannan Muthukkaruppan. Summary ------- This patch is from Hairong. Just helping out by putting it up on RB. This adds a global, configurable timeout for all HBase RPCs. Uses new config parameter 'hbase.rpc.timeout' rather than overloading the lease period. This addresses bug HBASE-3154 . http://issues.apache.org/jira/browse/HBASE-3154 Diffs trunk/src/main/java/org/apache/hadoop/hbase/HConstants.java 1029423 trunk/src/main/java/org/apache/hadoop/hbase/client/HConnectionManager.java 1029423 trunk/src/main/java/org/apache/hadoop/hbase/ipc/HBaseClient.java 1029423 trunk/src/main/java/org/apache/hadoop/hbase/ipc/HBaseRPC.java 1029423 trunk/src/main/java/org/apache/hadoop/hbase/regionserver/HRegionServer.java 1029423 Diff: http://review.cloudera.org/r/1142/diff Testing ------- Not actually sure. I know that we've committed this internally at FB and I think Hairong did testing on it. Thanks, Jonathan
        Hide
        Hairong Kuang added a comment -

        Here is a patch for review.

        Show
        Hairong Kuang added a comment - Here is a patch for review.

          People

          • Assignee:
            Hairong Kuang
            Reporter:
            Hairong Kuang
          • Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved:

              Development