phoenix-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Kadir OZDEMIR (Jira)" <j...@apache.org>
Subject [jira] [Assigned] (PHOENIX-5478) IndexTool mapper task should not timeout
Date Sun, 15 Sep 2019 21:28:00 GMT

     [ https://issues.apache.org/jira/browse/PHOENIX-5478?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Kadir OZDEMIR reassigned PHOENIX-5478:
--------------------------------------

    Assignee: Kadir OZDEMIR

> 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
>
> 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.2#803003)

Mime
View raw message