HBase
  1. HBase
  2. HBASE-6085

SaslServer intermittently ignoring SaslClient's requests

    Details

    • Type: Bug Bug
    • Status: Resolved
    • Priority: Major Major
    • Resolution: Later
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: security
    • Labels:
      None

      Description

      I often hit this problem where the client request is just ignored* by the server.
      The logs at the server doesn't reflect anything about the client, and then it does process the request in the next trial.

        Activity

        Hide
        Himanshu Vashishtha added a comment -

        ok, as you say Andrew.

        Show
        Himanshu Vashishtha added a comment - ok, as you say Andrew.
        Hide
        Andrew Purtell added a comment -

        I've not been able to reproduce this, made 100s of secure shell connections via bash script with 0.94 and Hadoop 2.0.0-alpha. Suggest resolving issue as 'Later'. It's not actionable but not invalid either.

        Show
        Andrew Purtell added a comment - I've not been able to reproduce this, made 100s of secure shell connections via bash script with 0.94 and Hadoop 2.0.0-alpha. Suggest resolving issue as 'Later'. It's not actionable but not invalid either.
        Hide
        Himanshu Vashishtha added a comment -

        I was trying it on a single node. Client, zk, master and rs all on one node.
        tcpdump also suggested that there was indeed no response from server for a minute in case request was not successful.

        Here are the tcpdump I find for a successful and failed "list" request from shell:

        [himanshu@c0319 ~]$ grep 40869 masterTcp/successList2
        07:02:22.751435 IP c0319.hal.cloudera.com.40869 >
        c0319.hal.cloudera.com.40000: S 2797432318:2797432318(0) win 32792
        <mss 16396,sackOK,timestamp 3153221090 0,nop,wscale 7>
        07:02:22.751454 IP c0319.hal.cloudera.com.40000 >
        c0319.hal.cloudera.com.40869: S 2802101336:2802101336(0) ack
        2797432319 win 32768 <mss 16396,sackOK,timestamp 3153221090
        3153221090,nop,wscale 7>
        07:02:22.751465 IP c0319.hal.cloudera.com.40869 >
        c0319.hal.cloudera.com.40000: . ack 1 win 257 <nop,nop,timestamp
        3153221090 3153221090>
        07:02:22.751656 IP c0319.hal.cloudera.com.40869 >
        c0319.hal.cloudera.com.40000: P 1:7(6) ack 1 win 257
        <nop,nop,timestamp 3153221091 3153221090>
        07:02:22.751666 IP c0319.hal.cloudera.com.40000 >
        c0319.hal.cloudera.com.40869: . ack 7 win 256 <nop,nop,timestamp
        3153221091 3153221091>
        07:02:22.754652 IP c0319.hal.cloudera.com.40869 >
        c0319.hal.cloudera.com.40000: P 7:551(544) ack 1 win 257
        <nop,nop,timestamp 3153221094 3153221091>
        07:02:22.754663 IP c0319.hal.cloudera.com.40000 >
        c0319.hal.cloudera.com.40869: . ack 551 win 265 <nop,nop,timestamp
        3153221094 3153221094>
        07:02:22.758010 IP c0319.hal.cloudera.com.40000 >
        c0319.hal.cloudera.com.40869: P 1:111(110) ack 551 win 265
        <nop,nop,timestamp 3153221097 3153221094>
        07:02:22.758020 IP c0319.hal.cloudera.com.40869 >
        c0319.hal.cloudera.com.40000: . ack 111 win 257 <nop,nop,timestamp
        3153221097 3153221097>
        07:02:22.758692 IP c0319.hal.cloudera.com.40869 >
        c0319.hal.cloudera.com.40000: P 551:555(4) ack 111 win 257
        <nop,nop,timestamp 3153221098 3153221097>
        07:02:22.759194 IP c0319.hal.cloudera.com.40000 >
        c0319.hal.cloudera.com.40869: P 111:176(65) ack 555 win 265
        <nop,nop,timestamp 3153221098 3153221098>
        07:02:22.760662 IP c0319.hal.cloudera.com.40869 >
        c0319.hal.cloudera.com.40000: P 555:612(57) ack 176 win 257
        <nop,nop,timestamp 3153221100 3153221098>
        07:02:22.801021 IP c0319.hal.cloudera.com.40000 >
        c0319.hal.cloudera.com.40869: . ack 612 win 265 <nop,nop,timestamp
        3153221140 3153221100>
        07:02:22.801035 IP c0319.hal.cloudera.com.40869 >
        c0319.hal.cloudera.com.40000: P 612:753(141) ack 176 win 257
        <nop,nop,timestamp 3153221140 3153221140>
        07:02:22.801044 IP c0319.hal.cloudera.com.40000 >
        c0319.hal.cloudera.com.40869: . ack 753 win 273 <nop,nop,timestamp
        3153221140 3153221140>
        07:02:22.907009 IP c0319.hal.cloudera.com.40000 >
        c0319.hal.cloudera.com.40869: P 176:5537(5361) ack 753 win 273
        <nop,nop,timestamp 3153221246 3153221140>
        07:02:22.947065 IP c0319.hal.cloudera.com.40869 >
        c0319.hal.cloudera.com.40000: . ack 5537 win 385 <nop,nop,timestamp
        3153221286 3153221246>
        [himanshu@c0319 ~]$
        

        Failed one:

        [himanshu@c0319 ~]$
        [himanshu@c0319 ~]$ cat masterTcp/failedListReq
        06:43:14.225674 IP c0319.hal.cloudera.com.45551 >
        c0319.hal.cloudera.com.40000: S 1589303657:1589303657(0) win 32792
        <mss 16396,sackOK,timestamp 3152072554 0,nop,wscale 7>
        06:43:14.225693 IP c0319.hal.cloudera.com.40000 >
        c0319.hal.cloudera.com.45551: S 1589991199:1589991199(0) ack
        1589303658 win 32768 <mss 16396,sackOK,timestamp 3152072554
        3152072554,nop,wscale 7>
        06:43:14.225705 IP c0319.hal.cloudera.com.45551 >
        c0319.hal.cloudera.com.40000: . ack 1 win 257 <nop,nop,timestamp
        3152072554 3152072554>
        06:43:14.225951 IP c0319.hal.cloudera.com.45551 >
        c0319.hal.cloudera.com.40000: P 1:7(6) ack 1 win 257
        <nop,nop,timestamp 3152072555 3152072554>
        06:43:14.225961 IP c0319.hal.cloudera.com.40000 >
        c0319.hal.cloudera.com.45551: . ack 7 win 256 <nop,nop,timestamp
        3152072555 3152072555>
        06:43:14.229954 IP c0319.hal.cloudera.com.45551 >
        c0319.hal.cloudera.com.40000: P 7:551(544) ack 1 win 257
        <nop,nop,timestamp 3152072558 3152072555>
        06:43:14.229968 IP c0319.hal.cloudera.com.40000 >
        c0319.hal.cloudera.com.45551: . ack 551 win 265 <nop,nop,timestamp
        3152072559 3152072558>
        06:44:14.232171 IP c0319.hal.cloudera.com.45551 >
        c0319.hal.cloudera.com.40000: F 551:551(0) ack 1 win 257
        <nop,nop,timestamp 3152132561 3152072559>
        06:44:14.272194 IP c0319.hal.cloudera.com.40000 >
        c0319.hal.cloudera.com.45551: . ack 552 win 265 <nop,nop,timestamp
        3152132601 3152132561>
        

        Upgrading to hadoop 2.0 based cloudera version, i couldn't reproduce it, even after trying out 50+ times. Initially it was occurring at freq of about 1/10.

        Show
        Himanshu Vashishtha added a comment - I was trying it on a single node. Client, zk, master and rs all on one node. tcpdump also suggested that there was indeed no response from server for a minute in case request was not successful. Here are the tcpdump I find for a successful and failed "list" request from shell: [himanshu@c0319 ~]$ grep 40869 masterTcp/successList2 07:02:22.751435 IP c0319.hal.cloudera.com.40869 > c0319.hal.cloudera.com.40000: S 2797432318:2797432318(0) win 32792 <mss 16396,sackOK,timestamp 3153221090 0,nop,wscale 7> 07:02:22.751454 IP c0319.hal.cloudera.com.40000 > c0319.hal.cloudera.com.40869: S 2802101336:2802101336(0) ack 2797432319 win 32768 <mss 16396,sackOK,timestamp 3153221090 3153221090,nop,wscale 7> 07:02:22.751465 IP c0319.hal.cloudera.com.40869 > c0319.hal.cloudera.com.40000: . ack 1 win 257 <nop,nop,timestamp 3153221090 3153221090> 07:02:22.751656 IP c0319.hal.cloudera.com.40869 > c0319.hal.cloudera.com.40000: P 1:7(6) ack 1 win 257 <nop,nop,timestamp 3153221091 3153221090> 07:02:22.751666 IP c0319.hal.cloudera.com.40000 > c0319.hal.cloudera.com.40869: . ack 7 win 256 <nop,nop,timestamp 3153221091 3153221091> 07:02:22.754652 IP c0319.hal.cloudera.com.40869 > c0319.hal.cloudera.com.40000: P 7:551(544) ack 1 win 257 <nop,nop,timestamp 3153221094 3153221091> 07:02:22.754663 IP c0319.hal.cloudera.com.40000 > c0319.hal.cloudera.com.40869: . ack 551 win 265 <nop,nop,timestamp 3153221094 3153221094> 07:02:22.758010 IP c0319.hal.cloudera.com.40000 > c0319.hal.cloudera.com.40869: P 1:111(110) ack 551 win 265 <nop,nop,timestamp 3153221097 3153221094> 07:02:22.758020 IP c0319.hal.cloudera.com.40869 > c0319.hal.cloudera.com.40000: . ack 111 win 257 <nop,nop,timestamp 3153221097 3153221097> 07:02:22.758692 IP c0319.hal.cloudera.com.40869 > c0319.hal.cloudera.com.40000: P 551:555(4) ack 111 win 257 <nop,nop,timestamp 3153221098 3153221097> 07:02:22.759194 IP c0319.hal.cloudera.com.40000 > c0319.hal.cloudera.com.40869: P 111:176(65) ack 555 win 265 <nop,nop,timestamp 3153221098 3153221098> 07:02:22.760662 IP c0319.hal.cloudera.com.40869 > c0319.hal.cloudera.com.40000: P 555:612(57) ack 176 win 257 <nop,nop,timestamp 3153221100 3153221098> 07:02:22.801021 IP c0319.hal.cloudera.com.40000 > c0319.hal.cloudera.com.40869: . ack 612 win 265 <nop,nop,timestamp 3153221140 3153221100> 07:02:22.801035 IP c0319.hal.cloudera.com.40869 > c0319.hal.cloudera.com.40000: P 612:753(141) ack 176 win 257 <nop,nop,timestamp 3153221140 3153221140> 07:02:22.801044 IP c0319.hal.cloudera.com.40000 > c0319.hal.cloudera.com.40869: . ack 753 win 273 <nop,nop,timestamp 3153221140 3153221140> 07:02:22.907009 IP c0319.hal.cloudera.com.40000 > c0319.hal.cloudera.com.40869: P 176:5537(5361) ack 753 win 273 <nop,nop,timestamp 3153221246 3153221140> 07:02:22.947065 IP c0319.hal.cloudera.com.40869 > c0319.hal.cloudera.com.40000: . ack 5537 win 385 <nop,nop,timestamp 3153221286 3153221246> [himanshu@c0319 ~]$ Failed one: [himanshu@c0319 ~]$ [himanshu@c0319 ~]$ cat masterTcp/failedListReq 06:43:14.225674 IP c0319.hal.cloudera.com.45551 > c0319.hal.cloudera.com.40000: S 1589303657:1589303657(0) win 32792 <mss 16396,sackOK,timestamp 3152072554 0,nop,wscale 7> 06:43:14.225693 IP c0319.hal.cloudera.com.40000 > c0319.hal.cloudera.com.45551: S 1589991199:1589991199(0) ack 1589303658 win 32768 <mss 16396,sackOK,timestamp 3152072554 3152072554,nop,wscale 7> 06:43:14.225705 IP c0319.hal.cloudera.com.45551 > c0319.hal.cloudera.com.40000: . ack 1 win 257 <nop,nop,timestamp 3152072554 3152072554> 06:43:14.225951 IP c0319.hal.cloudera.com.45551 > c0319.hal.cloudera.com.40000: P 1:7(6) ack 1 win 257 <nop,nop,timestamp 3152072555 3152072554> 06:43:14.225961 IP c0319.hal.cloudera.com.40000 > c0319.hal.cloudera.com.45551: . ack 7 win 256 <nop,nop,timestamp 3152072555 3152072555> 06:43:14.229954 IP c0319.hal.cloudera.com.45551 > c0319.hal.cloudera.com.40000: P 7:551(544) ack 1 win 257 <nop,nop,timestamp 3152072558 3152072555> 06:43:14.229968 IP c0319.hal.cloudera.com.40000 > c0319.hal.cloudera.com.45551: . ack 551 win 265 <nop,nop,timestamp 3152072559 3152072558> 06:44:14.232171 IP c0319.hal.cloudera.com.45551 > c0319.hal.cloudera.com.40000: F 551:551(0) ack 1 win 257 <nop,nop,timestamp 3152132561 3152072559> 06:44:14.272194 IP c0319.hal.cloudera.com.40000 > c0319.hal.cloudera.com.45551: . ack 552 win 265 <nop,nop,timestamp 3152132601 3152132561> Upgrading to hadoop 2.0 based cloudera version, i couldn't reproduce it, even after trying out 50+ times. Initially it was occurring at freq of about 1/10.
        Hide
        stack added a comment -

        A note of Andrew's on this issue:

        Anything of note appear in the server side logs at DEBUG level? Have
        you tried duplicating this in an all-localhost configuration? If it is
        possible to reproduce in an all-localhost configuration, or on a
        cluster not otherwise occupied, then we can turn on additional
        SASL/GSSAPI level debugging that may shed light but will be quite
        verbose.
        
        Show
        stack added a comment - A note of Andrew's on this issue: Anything of note appear in the server side logs at DEBUG level? Have you tried duplicating this in an all-localhost configuration? If it is possible to reproduce in an all-localhost configuration, or on a cluster not otherwise occupied, then we can turn on additional SASL/GSSAPI level debugging that may shed light but will be quite verbose.
        Hide
        Himanshu Vashishtha added a comment -

        In this context, I send a shell command to create a table. The master makes a SASL client and tries to connect to the region server, but it gets nothing from the region server for a minute. It then tries again and this time, request is successful.

        The relevant master server logs:

        2012-05-23 19:41:38,894 DEBUG org.apache.hadoop.hbase.security.HBaseSaslRpcClient: Creating SASL GSSAPI client. Server's Kerberos principal name is hbase/c0319.hal.cloudera.com@CLOUDERA.COM
        2012-05-23 19:41:38,896 DEBUG org.apache.hadoop.hbase.security.HBaseSaslRpcClient: Have sent token of size 540 from initSASLContext.
        2012-05-23 19:41:41,266 DEBUG org.apache.zookeeper.ClientCnxn: Got ping response for sessionid: 0x1377a5de16b0015 after 0ms
        2012-05-23 19:41:48,204 DEBUG org.apache.zookeeper.ClientCnxn: Got ping response for sessionid: 0x1377a5de16b0013 after 0ms
        2012-05-23 19:41:49,870 DEBUG org.apache.zookeeper.ClientCnxn: Got ping response for sessionid: 0x1377a5de16b0028 after 0ms
        2012-05-23 19:41:51,452 DEBUG org.apache.zookeeper.ClientCnxn: Got ping response for sessionid: 0x1377a5de16b0014 after 0ms
        2012-05-23 19:41:54,599 DEBUG org.apache.zookeeper.ClientCnxn: Got ping response for sessionid: 0x1377a5de16b0015 after 0ms
        2012-05-23 19:42:01,538 DEBUG org.apache.zookeeper.ClientCnxn: Got ping response for sessionid: 0x1377a5de16b0013 after 0ms
        2012-05-23 19:42:03,204 DEBUG org.apache.zookeeper.ClientCnxn: Got ping response for sessionid: 0x1377a5de16b0028 after 0ms
        2012-05-23 19:42:04,785 DEBUG org.apache.zookeeper.ClientCnxn: Got ping response for sessionid: 0x1377a5de16b0014 after 0ms
        2012-05-23 19:42:07,932 DEBUG org.apache.zookeeper.ClientCnxn: Got ping response for sessionid: 0x1377a5de16b0015 after 0ms
        2012-05-23 19:42:14,872 DEBUG org.apache.zookeeper.ClientCnxn: Got ping response for sessionid: 0x1377a5de16b0013 after 0ms
        2012-05-23 19:42:16,538 DEBUG org.apache.zookeeper.ClientCnxn: Got ping response for sessionid: 0x1377a5de16b0028 after 0ms
        2012-05-23 19:42:18,118 DEBUG org.apache.zookeeper.ClientCnxn: Got ping response for sessionid: 0x1377a5de16b0014 after 0ms
        2012-05-23 19:42:21,265 DEBUG org.apache.zookeeper.ClientCnxn: Got ping response for sessionid: 0x1377a5de16b0015 after 0ms
        2012-05-23 19:42:28,206 DEBUG org.apache.zookeeper.ClientCnxn: Got ping response for sessionid: 0x1377a5de16b0013 after 0ms
        2012-05-23 19:42:29,873 DEBUG org.apache.zookeeper.ClientCnxn: Got ping response for sessionid: 0x1377a5de16b0028 after 0ms
        2012-05-23 19:42:31,452 DEBUG org.apache.zookeeper.ClientCnxn: Got ping response for sessionid: 0x1377a5de16b0014 after 0ms
        2012-05-23 19:42:34,598 DEBUG org.apache.zookeeper.ClientCnxn: Got ping response for sessionid: 0x1377a5de16b0015 after 0ms
        2012-05-23 19:42:38,896 ERROR org.apache.hadoop.security.UserGroupInformation: PriviledgedActionException as:hbase/c0319.hal.cloudera.com@CLOUDERA.COM (auth:KERBEROS) cause:java.net.SocketTimeoutException: 60000 millis timeout while waiting for channel to be ready for read. ch : java.nio.channels.SocketChannel[connected local=/172.29.81.101:44593 remote=c0319.hal.cloudera.com/172.29.81.101:40020]
        2012-05-23 19:42:40,543 DEBUG org.apache.hadoop.hbase.security.HBaseSaslRpcClient: Creating SASL GSSAPI client. Server's Kerberos principal name is hbase/c0319.hal.cloudera.com@CLOUDERA.COM
        2012-05-23 19:42:40,546 DEBUG org.apache.hadoop.hbase.security.HBaseSaslRpcClient: Have sent token of size 540 from initSASLContext.
        2012-05-23 19:42:40,549 DEBUG org.apache.hadoop.hbase.security.HBaseSaslRpcClient: Will read input token of size 98 for processing by initSASLContext
        2012-05-23 19:42:40,550 DEBUG org.apache.hadoop.hbase.security.HBaseSaslRpcClient: Will send token of size 0 from initSASLContext.
        2012-05-23 19:42:40,550 DEBUG org.apache.hadoop.hbase.security.HBaseSaslRpcClient: Will read input token of size 53 for processing by initSASLContext
        2012-05-23 19:42:40,551 DEBUG org.apache.hadoop.hbase.security.HBaseSaslRpcClient: Will send token of size 53 from initSASLContext.
        2012-05-23 19:42:40,551 DEBUG org.apache.hadoop.hbase.security.HBaseSaslRpcClient: SASL client context established. Negotiated QoP: auth
        2012-05-23 19:42:40,593 DEBUG org.apache.hadoop.hbase.client.HTable$ClientScanner: Creating scanner over .META. starting at key 'm7,,'
        2012-05-23 19:42:40,593 DEBUG org.apache.hadoop.hbase.client.HTable$ClientScanner: Advancing internal scanner to startKey at 'm7,,'
        2012-05-23 19:42:40,596 DEBUG org.apache.zookeeper.ClientCnxn: Reading reply sessionid:0x1377a5de16b0013, packet:: clientPath:null serverPath:null finished:false header:: 1919,3  replyHeader:: 1919,2101,-101  request:: '/hbase/table/m7,F  response::
        
        
        Show
        Himanshu Vashishtha added a comment - In this context, I send a shell command to create a table. The master makes a SASL client and tries to connect to the region server, but it gets nothing from the region server for a minute. It then tries again and this time, request is successful. The relevant master server logs: 2012-05-23 19:41:38,894 DEBUG org.apache.hadoop.hbase.security.HBaseSaslRpcClient: Creating SASL GSSAPI client. Server's Kerberos principal name is hbase/c0319.hal.cloudera.com@CLOUDERA.COM 2012-05-23 19:41:38,896 DEBUG org.apache.hadoop.hbase.security.HBaseSaslRpcClient: Have sent token of size 540 from initSASLContext. 2012-05-23 19:41:41,266 DEBUG org.apache.zookeeper.ClientCnxn: Got ping response for sessionid: 0x1377a5de16b0015 after 0ms 2012-05-23 19:41:48,204 DEBUG org.apache.zookeeper.ClientCnxn: Got ping response for sessionid: 0x1377a5de16b0013 after 0ms 2012-05-23 19:41:49,870 DEBUG org.apache.zookeeper.ClientCnxn: Got ping response for sessionid: 0x1377a5de16b0028 after 0ms 2012-05-23 19:41:51,452 DEBUG org.apache.zookeeper.ClientCnxn: Got ping response for sessionid: 0x1377a5de16b0014 after 0ms 2012-05-23 19:41:54,599 DEBUG org.apache.zookeeper.ClientCnxn: Got ping response for sessionid: 0x1377a5de16b0015 after 0ms 2012-05-23 19:42:01,538 DEBUG org.apache.zookeeper.ClientCnxn: Got ping response for sessionid: 0x1377a5de16b0013 after 0ms 2012-05-23 19:42:03,204 DEBUG org.apache.zookeeper.ClientCnxn: Got ping response for sessionid: 0x1377a5de16b0028 after 0ms 2012-05-23 19:42:04,785 DEBUG org.apache.zookeeper.ClientCnxn: Got ping response for sessionid: 0x1377a5de16b0014 after 0ms 2012-05-23 19:42:07,932 DEBUG org.apache.zookeeper.ClientCnxn: Got ping response for sessionid: 0x1377a5de16b0015 after 0ms 2012-05-23 19:42:14,872 DEBUG org.apache.zookeeper.ClientCnxn: Got ping response for sessionid: 0x1377a5de16b0013 after 0ms 2012-05-23 19:42:16,538 DEBUG org.apache.zookeeper.ClientCnxn: Got ping response for sessionid: 0x1377a5de16b0028 after 0ms 2012-05-23 19:42:18,118 DEBUG org.apache.zookeeper.ClientCnxn: Got ping response for sessionid: 0x1377a5de16b0014 after 0ms 2012-05-23 19:42:21,265 DEBUG org.apache.zookeeper.ClientCnxn: Got ping response for sessionid: 0x1377a5de16b0015 after 0ms 2012-05-23 19:42:28,206 DEBUG org.apache.zookeeper.ClientCnxn: Got ping response for sessionid: 0x1377a5de16b0013 after 0ms 2012-05-23 19:42:29,873 DEBUG org.apache.zookeeper.ClientCnxn: Got ping response for sessionid: 0x1377a5de16b0028 after 0ms 2012-05-23 19:42:31,452 DEBUG org.apache.zookeeper.ClientCnxn: Got ping response for sessionid: 0x1377a5de16b0014 after 0ms 2012-05-23 19:42:34,598 DEBUG org.apache.zookeeper.ClientCnxn: Got ping response for sessionid: 0x1377a5de16b0015 after 0ms 2012-05-23 19:42:38,896 ERROR org.apache.hadoop.security.UserGroupInformation: PriviledgedActionException as:hbase/c0319.hal.cloudera.com@CLOUDERA.COM (auth:KERBEROS) cause:java.net.SocketTimeoutException: 60000 millis timeout while waiting for channel to be ready for read. ch : java.nio.channels.SocketChannel[connected local=/172.29.81.101:44593 remote=c0319.hal.cloudera.com/172.29.81.101:40020] 2012-05-23 19:42:40,543 DEBUG org.apache.hadoop.hbase.security.HBaseSaslRpcClient: Creating SASL GSSAPI client. Server's Kerberos principal name is hbase/c0319.hal.cloudera.com@CLOUDERA.COM 2012-05-23 19:42:40,546 DEBUG org.apache.hadoop.hbase.security.HBaseSaslRpcClient: Have sent token of size 540 from initSASLContext. 2012-05-23 19:42:40,549 DEBUG org.apache.hadoop.hbase.security.HBaseSaslRpcClient: Will read input token of size 98 for processing by initSASLContext 2012-05-23 19:42:40,550 DEBUG org.apache.hadoop.hbase.security.HBaseSaslRpcClient: Will send token of size 0 from initSASLContext. 2012-05-23 19:42:40,550 DEBUG org.apache.hadoop.hbase.security.HBaseSaslRpcClient: Will read input token of size 53 for processing by initSASLContext 2012-05-23 19:42:40,551 DEBUG org.apache.hadoop.hbase.security.HBaseSaslRpcClient: Will send token of size 53 from initSASLContext. 2012-05-23 19:42:40,551 DEBUG org.apache.hadoop.hbase.security.HBaseSaslRpcClient: SASL client context established. Negotiated QoP: auth 2012-05-23 19:42:40,593 DEBUG org.apache.hadoop.hbase.client.HTable$ClientScanner: Creating scanner over .META. starting at key 'm7,,' 2012-05-23 19:42:40,593 DEBUG org.apache.hadoop.hbase.client.HTable$ClientScanner: Advancing internal scanner to startKey at 'm7,,' 2012-05-23 19:42:40,596 DEBUG org.apache.zookeeper.ClientCnxn: Reading reply sessionid:0x1377a5de16b0013, packet:: clientPath: null serverPath: null finished: false header:: 1919,3 replyHeader:: 1919,2101,-101 request:: '/hbase/table/m7,F response::

          People

          • Assignee:
            Unassigned
            Reporter:
            Himanshu Vashishtha
          • Votes:
            0 Vote for this issue
            Watchers:
            7 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved:

              Development