[
https://issues.apache.org/jira/browse/PHOENIX-5478?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16958708#comment-16958708
]
Hudson commented on PHOENIX-5478:
---------------------------------
SUCCESS: Integrated in Jenkins build Phoenix-4.x-HBase-1.4 #289 (See
[https://builds.apache.org/job/Phoenix-4.x-HBase-1.4/289/])
PHOENIX-5478 IndexTool mapper task should not timeout (kadir: rev
4a11397d3127d333b36ab9b6febd70dbb515d959)
* (edit) phoenix-core/src/it/java/org/apache/phoenix/end2end/IndexToolIT.java
* (edit)
phoenix-core/src/main/java/org/apache/phoenix/mapreduce/PhoenixServerBuildIndexInputFormat.java
* (edit)
phoenix-core/src/main/java/org/apache/phoenix/query/QueryServicesOptions.java
* (edit)
phoenix-core/src/main/java/org/apache/phoenix/index/GlobalIndexChecker.java
* (edit) phoenix-core/src/main/java/org/apache/phoenix/query/QueryServices.java
* (edit)
phoenix-core/src/main/java/org/apache/phoenix/mapreduce/index/IndexTool.java
* (edit)
phoenix-core/src/main/java/org/apache/phoenix/coprocessor/UngroupedAggregateRegionObserver.java
* (edit)
phoenix-core/src/main/java/org/apache/phoenix/coprocessor/BaseScannerRegionObserver.java
> IndexTool mapper task should not timeout
> -----------------------------------------
>
> Key: PHOENIX-5478
> URL: https://issues.apache.org/jira/browse/PHOENIX-5478
> Project: Phoenix
> Issue Type: Bug
> Affects Versions: 5.0.0, 4.15.0
> Reporter: Kadir OZDEMIR
> Assignee: Kadir OZDEMIR
> Priority: Major
> Attachments: PHOENIX-5478.master.001.patch,
> PHOENIX-5478.master.002.patch, PHOENIX-5478.master.003.patch
>
> Time Spent: 2.5h
> Remaining Estimate: 0h
>
> In the old design, the IndexTool MR job mapper first scanned the data table
> rows one by one using a Phoenix client code, then constructed the index rows
> and finally sent these row mutations to region servers to update the rows on
> the index table regions. In the new design, this entire process is done on
> the server side (within a coprocessor). So, the mapper just issues one RPC
> call to instruct the coprocessor to build the entire table region. This RPC
> call can timeout if the table region is large. The temporary solution that is
> currently used is to set very large timeout values. We should break up single
> table region rebuild into smaller operations and eliminate setting large
> timeout values.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
