You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@hbase.apache.org by "Himanshu Vashishtha (JIRA)" <ji...@apache.org> on 2012/05/24 04:55:41 UTC
[jira] [Commented] (HBASE-6085) SaslServer intermittently ignoring
SaslClient's requests
[ https://issues.apache.org/jira/browse/HBASE-6085?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13282145#comment-13282145 ]
Himanshu Vashishtha commented on HBASE-6085:
--------------------------------------------
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:
{code}
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::
{code}
> SaslServer intermittently ignoring SaslClient's requests
> --------------------------------------------------------
>
> Key: HBASE-6085
> URL: https://issues.apache.org/jira/browse/HBASE-6085
> Project: HBase
> Issue Type: Bug
> Reporter: Himanshu Vashishtha
>
> 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.
--
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