[
https://issues.apache.org/jira/browse/PHOENIX-1677?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14361932#comment-14361932
]
Hudson commented on PHOENIX-1677:
---------------------------------
FAILURE: Integrated in Phoenix-3.0-hadoop1 #375 (See
[https://builds.apache.org/job/Phoenix-3.0-hadoop1/375/])
PHOENIX-1677 Immutable index deadlocks when number of guideposts are one half
of thread pool size (jtaylor: rev 1c6e46ab23561a312bda90b0db99145034d2f7ba)
* phoenix-core/src/main/java/org/apache/phoenix/query/HTableFactory.java
*
phoenix-core/src/main/java/org/apache/phoenix/query/ConnectionQueryServicesImpl.java
*
phoenix-core/src/it/java/org/apache/phoenix/end2end/index/ImmutableIndexWithStatsIT.java
*
phoenix-core/src/main/java/org/apache/phoenix/coprocessor/MetaDataProtocol.java
> Immutable index deadlocks when number of guideposts are one half of thread
> pool size
> ------------------------------------------------------------------------------------
>
> Key: PHOENIX-1677
> URL: https://issues.apache.org/jira/browse/PHOENIX-1677
> Project: Phoenix
> Issue Type: Bug
> Affects Versions: 5.0.0, 4.3
> Reporter: Mujtaba Chohan
> Assignee: James Taylor
> Fix For: 3.3.1, 4.3.1, 4.4
>
> Attachments: PHOENIX-1677_utest.patch, PHOENIX-1677_v2.patch
>
>
> If total number of parallel iterators + mutation count exceeds Phoenix thread
> pool size then immutable index remains at 0 rows with no activity on client
> and server.
> Ex. Only with guide post count of 64 or lower does immutable index gets build
> with default 128 thread pool. By changing guide post width to get with >64
> guideposts, index fails to build. Also if thread pool size is lowered from
> 128 then index fails to build for 64 guide posts.
> Let me know if you need a utest as I think it would be easy to repro in it
> too.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
