Mailing-List: contact issues-help@impala.incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@impala.incubator.apache.org
Date: Thu, 30 Mar 2017 20:02:41 +0000 (UTC)
From: "Tim Armstrong (JIRA)" <jira@apache.org>
To: issues@impala.incubator.apache.org
Message-ID: <JIRA.13052903.1441204987000.168655.1490904161978@Atlassian.JIRA>
In-Reply-To: <JIRA.13052903.1441204987000@Atlassian.JIRA>
References: <JIRA.13052903.1441204987000@Atlassian.JIRA> <JIRA.13052903.1441204987000@jira-lw-us.apache.org>
Subject: [jira] [Resolved] (IMPALA-2285) Query should return error not
 cancelled when failing to flush blocks due to lack of disk space
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
archived-at: Thu, 30 Mar 2017 20:02:48 -0000


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

Tim Armstrong resolved IMPALA-2285.
-----------------------------------
    Resolution: Won't Fix

This issue stems from the old BufferedBlockMgr code paths. We won't fix it directly, instead it will be indirectly fixed by the IMPALA-3200 work.

> Query should return error not cancelled when failing to flush blocks due to lack of disk space
> ----------------------------------------------------------------------------------------------
>
>                 Key: IMPALA-2285
>                 URL: https://issues.apache.org/jira/browse/IMPALA-2285
>             Project: IMPALA
>          Issue Type: Bug
>          Components: Backend
>    Affects Versions: Impala 2.1.2
>            Reporter: Matthew Jacobs
>            Assignee: Tim Armstrong
>            Priority: Minor
>              Labels: ramp-up, resource-management
>
> When BufferedBlockMgr blocks must be flushed to disk but the write cannot be completed due to lack of disk space on the scratch disks, queries fail with a cancelled status and no further information. Queries should instead fail with an exception status and an error message indicating the scratch disk was full.
> This can be reproduced by setting the scratch dir to a disk with negligible space and forcing a query to spill to disk. The way to determine this occurred is by looking for the following in the impalad log:
> I0831 14:13:35.791662 14318 buffered-block-mgr.cc:769] Query: f74317d168f9d915:58d67871e44fa2a2 write complete callback with error.
> I0831 14:13:35.791698 14318 runtime-state.cc:225] Error from query f74317d168f9d915:58d67871e44fa2a2: posix_fallocate(279, 17095983104, 8388527) failed for file /tmp/impala-scratch/f74317d168f9d915:58d67871e44fa2a2_747758b8-ff16-4a00-8d1f-0566ab71c787 with returnval=28 description=Error(11): Resource temporarily unavailable
> There is no workaround.


--
This message was sent by Atlassian JIRA
(v6.3.15#6346)