[
https://issues.apache.org/jira/browse/HBASE-14559?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14945864#comment-14945864
]
stack commented on HBASE-14559:
-------------------------------
bq. stack when you traced the tests using excessive number of threads, did they
timeout because they run slower with lower number of threads, or did they
deadlock?
At the extreme, the test would not run (OOME could not create native thread). I
cut the thread count down and then they would not complete (smile).
bq. I think there're still bugs lurking around in the implementation If we
have number of thread handlers 3 rather than 40, I might expect things running
noticeably slower, but not the deadlock?
The deadlock was handlers all occupied.. not enough for the test to complete.
> branch-1 test tweeks; disable assert explicit region lands post-restart and
> up a few handlers
> ---------------------------------------------------------------------------------------------
>
> Key: HBASE-14559
> URL: https://issues.apache.org/jira/browse/HBASE-14559
> Project: HBase
> Issue Type: Sub-task
> Components: test
> Reporter: stack
> Assignee: stack
> Fix For: 2.0.0, 1.2.0, 1.3.0
>
> Attachments: 14559.branch-1.txt, 14559.master.txt
>
>
> Running branch-1 on internal rig (trying to stabilize branch-1/branch-1.2).
> Small tweaks get tests to pass. Small one liners that up priority handler
> count and disable assert that seems wrong -- that we'll always get an explcit
> region to land on a newly started server.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
