[
https://issues.apache.org/jira/browse/PHOENIX-3950?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16638933#comment-16638933
]
Geoffrey Jacoby commented on PHOENIX-3950:
------------------------------------------
My understanding is that the reducer proper can never start until the map tasks
are all complete, since data needed for the first reduce call could be in the
last map call, but that shuffling can start sooner by default.
> IndexTool marks index active even when index building fails
> -----------------------------------------------------------
>
> Key: PHOENIX-3950
> URL: https://issues.apache.org/jira/browse/PHOENIX-3950
> Project: Phoenix
> Issue Type: Bug
> Reporter: James Taylor
> Priority: Major
>
> We've seen cases in which the MR-based index building tool (IndexTool) marks
> an index as active when the index building clearly did not succeed. It might
> be related to a timeout occurring and then not being propagated to the client.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
