[
https://issues.apache.org/jira/browse/HBASE-3438?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12980907#action_12980907
]
Jonathan Gray commented on HBASE-3438:
--------------------------------------
Sounds like a large number of small, evenly distributed writes. With every
client hitting every region frequently, you can certainly run into an issue
where data unavailability of a single region could cause a "global pause".
Lots of work has been done to make this faster, and there's plenty more work
that can be done. Like Todd said, be sure to check on your client retries and
you might turn up client-side debugging to look for more signs. You are also
going to pay the cost of a re-lookup in META. There's been some discussion for
a while about clients more proactively learning of new region locations via ZK
(this could also trigger a retry, negating the need to do frequent retries
after an NSRE).
> Cluster Wide Pauses
> -------------------
>
> Key: HBASE-3438
> URL: https://issues.apache.org/jira/browse/HBASE-3438
> Project: HBase
> Issue Type: Bug
> Affects Versions: 0.89.20100924
> Environment: CentOS 5.5, 10 Nodes, 24GB RAM, 4 1TB Disks, 8GB Heap
> Reporter: Wayne
>
> Under heavy write load the entire cluster seems to pause with all nodes
> pausing writes/reads for several seconds at a time. This seems to be worse
> with larger region sizes. One possible explanation is that a single node gets
> caught/paused/stuck during a split and that all other nodes are waiting on
> that one node so it looks like a cluster wide pause.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
