Return-Path: X-Original-To: archive-asf-public-internal@cust-asf2.ponee.io Delivered-To: archive-asf-public-internal@cust-asf2.ponee.io Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183]) by cust-asf2.ponee.io (Postfix) with ESMTP id 1B27A200C15 for ; Wed, 25 Jan 2017 01:55:32 +0100 (CET) Received: by cust-asf.ponee.io (Postfix) id 19E56160B4B; Wed, 25 Jan 2017 00:55:32 +0000 (UTC) Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by cust-asf.ponee.io (Postfix) with SMTP id 642D8160B3E for ; Wed, 25 Jan 2017 01:55:31 +0100 (CET) Received: (qmail 518 invoked by uid 500); 25 Jan 2017 00:55:30 -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 504 invoked by uid 99); 25 Jan 2017 00:55:30 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd1-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 25 Jan 2017 00:55:30 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd1-us-west.apache.org (ASF Mail Server at spamd1-us-west.apache.org) with ESMTP id 3FF58C126C for ; Wed, 25 Jan 2017 00:55:30 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd1-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -1.998 X-Spam-Level: X-Spam-Status: No, score=-1.998 tagged_above=-999 required=6.31 tests=[KAM_LAZY_DOMAIN_SECURITY=1, RP_MATCHES_RCVD=-2.999, URIBL_BLOCKED=0.001] autolearn=disabled Received: from mx1-lw-eu.apache.org ([10.40.0.8]) by localhost (spamd1-us-west.apache.org [10.40.0.7]) (amavisd-new, port 10024) with ESMTP id umSW4LxdtFR8 for ; Wed, 25 Jan 2017 00:55:29 +0000 (UTC) Received: from mailrelay1-us-west.apache.org (mailrelay1-us-west.apache.org [209.188.14.139]) by mx1-lw-eu.apache.org (ASF Mail Server at mx1-lw-eu.apache.org) with ESMTP id ED2F35F296 for ; Wed, 25 Jan 2017 00:55:28 +0000 (UTC) Received: from jira-lw-us.apache.org (unknown [207.244.88.139]) by mailrelay1-us-west.apache.org (ASF Mail Server at mailrelay1-us-west.apache.org) with ESMTP id C7D60E0389 for ; Wed, 25 Jan 2017 00:55:26 +0000 (UTC) Received: from jira-lw-us.apache.org (localhost [127.0.0.1]) by jira-lw-us.apache.org (ASF Mail Server at jira-lw-us.apache.org) with ESMTP id 685682528B for ; Wed, 25 Jan 2017 00:55:26 +0000 (UTC) Date: Wed, 25 Jan 2017 00:55:26 +0000 (UTC) From: "Laurent Goujon (JIRA)" To: issues@drill.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (DRILL-5217) Heartbeat Fails when C++ client receives a large ResultSet MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 archived-at: Wed, 25 Jan 2017 00:55:32 -0000 [ https://issues.apache.org/jira/browse/DRILL-5217?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15836950#comment-15836950 ] Laurent Goujon commented on DRILL-5217: --------------------------------------- maybe I misunderstood what the issue is: I thought the client was closing the connection because it was not receiving the pong notification in a timely manner. > Heartbeat Fails when C++ client receives a large ResultSet > ---------------------------------------------------------- > > Key: DRILL-5217 > URL: https://issues.apache.org/jira/browse/DRILL-5217 > Project: Apache Drill > Issue Type: Bug > Components: Client - C++ > Reporter: Sudheesh Katkam > Priority: Critical > > If the listener thread is occupied for longer than 15 seconds (heartbeat timeout) while [handling a message from the drillbit|https://github.com/apache/drill/blob/master/contrib/native/client/src/clientlib/drillClientImpl.cpp#L1286] e.g. [processing query data blocks if the query result listener's buffer is full|https://github.com/apache/drill/blob/master/contrib/native/client/src/clientlib/drillClientImpl.cpp#L899], heartbeats fail because the same thread is responsible for sending heartbeats! > Fix is to [handle long running operations|http://stackoverflow.com/questions/17648725/long-running-blocking-operations-in-boost-asio-handlers] separately using boost asio. -- This message was sent by Atlassian JIRA (v6.3.4#6332)