Mailing-List: contact mapreduce-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Reply-To: mapreduce-issues@hadoop.apache.org
Date: Sat, 12 Mar 2016 21:03:03 +0000 (UTC)
From: "Shyam Gavulla (JIRA)" <jira@apache.org>
To: mapreduce-issues@hadoop.apache.org
Message-ID: <JIRA.12601649.1344304112000.361.1457816583955@Atlassian.JIRA>
In-Reply-To: <JIRA.12601649.1344304112000@Atlassian.JIRA>
References: <JIRA.12601649.1344304112000@Atlassian.JIRA>
 <JIRA.12601649.1344304112550@arcas>
Subject: [jira] [Updated] (MAPREDUCE-4522) DBOutputFormat Times out on large
 batch inserts
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Shyam Gavulla updated MAPREDUCE-4522:
-------------------------------------
    Attachment: MAPREDUCE-4522.001.patch

> DBOutputFormat Times out on large batch inserts
> -----------------------------------------------
>
>                 Key: MAPREDUCE-4522
>                 URL: https://issues.apache.org/jira/browse/MAPREDUCE-4522
>             Project: Hadoop Map/Reduce
>          Issue Type: Bug
>          Components: task-controller
>    Affects Versions: 0.20.205.0
>            Reporter: Nathan Jarus
>            Assignee: Shyam Gavulla
>              Labels: newbie
>             Fix For: 3.0.0
>
>         Attachments: MAPREDUCE-4522.001.patch
>
>
> In DBRecordWriter#close(), progress is never updated. In large batch inserts, this can cause the reduce task to time out due to the amount of time it takes the SQL engine to process that insert. 
> Potential solutions I can see:
> Don't batch inserts; do the insert when DBRecordWriter#write() is called (awful)
> Spin up a thread in DBRecordWriter#close() and update progress in that. (gross)
> I can provide code for either if you're interested. 


--
This message was sent by Atlassian JIRA
(v6.3.4#6332)