[ 
https://issues.apache.org/jira/browse/HBASE-6841?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13460674#comment-13460674
 ] 

Jean-Daniel Cryans commented on HBASE-6841:
-------------------------------------------

bq. @J-D: Since this is (presumably) a long standing condition, how do you feel 
about moving this to 0.94.3?

I'm ok.

bq. Which client did you jstack? There're at least two clients at work here: 
The one the attempts the truncate and the ones that still perform the requests.

The clients. I truncated separately.

bq. I am beginning to doubt that prefetching is a issue here. This has to do 
with how these clients connect. There should not need to be a connection setup 
each time.

Something is broken, we agree there :)
                
> Meta prefetching is slower than doing multiple meta lookups
> -----------------------------------------------------------
>
>                 Key: HBASE-6841
>                 URL: https://issues.apache.org/jira/browse/HBASE-6841
>             Project: HBase
>          Issue Type: Improvement
>            Reporter: Jean-Daniel Cryans
>            Assignee: Lars Hofhansl
>            Priority: Critical
>             Fix For: 0.94.3
>
>         Attachments: 6841-0.94.txt, 6841-0.96.txt
>
>
> I got myself into a situation where I needed to truncate a massive table 
> while it was getting hits and surprisingly the clients were not recovering. 
> What I see in the logs is that every time we prefetch .META. we setup a new 
> HConnection because we close it on the way out. It's awfully slow.
> We should just turn it off or make it useful. jstacks coming up.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira

Reply via email to