Return-Path: X-Original-To: apmail-drill-issues-archive@minotaur.apache.org Delivered-To: apmail-drill-issues-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 184BD10DE1 for ; Sun, 4 Jan 2015 21:28:46 +0000 (UTC) Received: (qmail 94735 invoked by uid 500); 4 Jan 2015 21:28:47 -0000 Delivered-To: apmail-drill-issues-archive@drill.apache.org Received: (qmail 94704 invoked by uid 500); 4 Jan 2015 21:28:47 -0000 Mailing-List: contact issues-help@drill.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@drill.apache.org Delivered-To: mailing list issues@drill.apache.org Received: (qmail 94694 invoked by uid 99); 4 Jan 2015 21:28:47 -0000 Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 04 Jan 2015 21:28:47 +0000 Date: Sun, 4 Jan 2015 21:28:46 +0000 (UTC) From: "Jacques Nadeau (JIRA)" To: issues@drill.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Updated] (DRILL-1442) C++ Client - Synchronous API appears to hang when running many queries in parallel MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/DRILL-1442?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jacques Nadeau updated DRILL-1442: ---------------------------------- Fix Version/s: 0.9.0 > C++ Client - Synchronous API appears to hang when running many queries in parallel > ---------------------------------------------------------------------------------- > > Key: DRILL-1442 > URL: https://issues.apache.org/jira/browse/DRILL-1442 > Project: Apache Drill > Issue Type: Bug > Components: Client - C++ > Affects Versions: 0.5.0 > Reporter: Parth Chandra > Assignee: Parth Chandra > Fix For: 0.9.0 > > > The C++ client library has a synchronous version that allows a client application to submit multiple queries asynchronously but retrieve results in synchronously. > A situation may occur where the application may submit several large queries and then choose to process the results of the last submitted query first. In this case the client library buffers up the results of the first few queries and may hit its memory allocation limit before the last queries results are retrieved. > The client app then deadlocks as the last query waits for more memory and the first few queries wait for the app to consume the results. > Technically this would qualify as a client application bug, but the client library should prevent or break the deadlock if it can. > At the vary least, the querySubmitter example program should not suffer from this issue. -- This message was sent by Atlassian JIRA (v6.3.4#6332)