[
https://issues.apache.org/jira/browse/PHOENIX-2154?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14700509#comment-14700509
]
Thomas D'Silva commented on PHOENIX-2154:
-----------------------------------------
perf results for a 8 node cluster
narrow table
100 million rows
MR : 16mins, 49sec
Regular : 9mins, 53sec
1 billion rows
MR : 2hrs, 40mins, 56sec
Regular : 1hr, 15mins, 42 seconds
wide table
1 billion rows
MR : 22hrs, 54mins, 48sec *
Regular : 8hrs, 30mins, 47sec
* Job fails while trying to load HFiles
> Failure of one mapper should not affect other mappers in MR index build
> -----------------------------------------------------------------------
>
> Key: PHOENIX-2154
> URL: https://issues.apache.org/jira/browse/PHOENIX-2154
> Project: Phoenix
> Issue Type: Bug
> Reporter: James Taylor
> Attachments: IndexTool.java
>
>
> Once a mapper in the MR index job succeeds, it should not need to be re-done
> in the event of the failure of one of the other mappers. The initial
> population of an index is based on a snapshot in time, so new rows getting
> *after* the index build has started and/or failed do not impact it.
> Also, there's a 1:1 correspondence between index rows and table rows, so
> there's really no need to dedup. However, the index rows will have a
> different row key than the data table, so I'm not sure how the HFiles are
> split. Will they potentially overlap and is this an issue?
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
