[
https://issues.apache.org/jira/browse/HBASE-6085?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13286194#comment-13286194
]
Himanshu Vashishtha commented on HBASE-6085:
--------------------------------------------
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:
{code}
[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 ~]$
{code}
Failed one:
{code}
[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>
{code}
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.
> SaslServer intermittently ignoring SaslClient's requests
> --------------------------------------------------------
>
> Key: HBASE-6085
> URL: https://issues.apache.org/jira/browse/HBASE-6085
> Project: HBase
> Issue Type: Bug
> Components: security
> 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
