[
https://issues.apache.org/jira/browse/HBASE-14378?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14907415#comment-14907415
]
Andrew Purtell commented on HBASE-14378:
----------------------------------------
bq. Reivews? Just ups priority handlers on tests that have been exhibiting
zombie symptoms and adding timeouts.
+1, seems reasonable to me until we can better address the underlying issue
about running out of priority handlers if the queue is sized too small (i.e.
make the setting a core pool size and allow it to grow up to another
configurable limit set pretty high by default)
> Get TestAccessController* passing again on branch-1
> ---------------------------------------------------
>
> Key: HBASE-14378
> URL: https://issues.apache.org/jira/browse/HBASE-14378
> Project: HBase
> Issue Type: Sub-task
> Reporter: stack
> Assignee: stack
> Fix For: 2.0.0, 1.2.0, 1.3.0
>
> Attachments: 14378.branch-1.txt, 14378.branch-1.v2.txt,
> 14378.branch-1.v2.txt, 14378.branch-1.v2.txt, 14378.branch-1.v6.txt,
> 14378.branch-1.v7.txt, 14386.branch-1.v3 (1).txt, 14386.branch-1.v3.txt,
> 14386.branch-1.v3.txt, 14386.branch-1.v4.do.nothing.txt, 14386.branch-1.v5.txt
>
>
> TestAccessController* are failing reliably on branch-1. They go zombie. I
> learned that setting the junit test timeout facility on the class doesn't
> make the zombie timeout nor does setting a timeout on each test turn zombies
> to test failures; the test goes zombie on the way out in the tear down of the
> cluster.
> Digging, we are out of handlers... all are occupied.
> 3dacee6 HBASE-14290 Spin up less threads in tests cut the default thread
> count to 3 from 10. Putting the value back on these tests seems to make them
> pass reliably when I run locally. For good measure, I'll add in the timeouts
> .
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
