[PHOENIX-5478] IndexTool mapper task should not timeout

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 5.0.0, 4.15.0
• Fix Version/s: 5.1.0
• Assignee: Kadir OZDEMIR
• Reporter: Kadir OZDEMIR
• Created: 15/Sep/19 21:26
• Updated: 10/Feb/21 10:01
• Resolved: 28/Oct/19 22:43

Description

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.

Issue Links

• links to: GitHub Pull Request #603