Mailing-List: contact issues-help@drill.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@drill.apache.org
Date: Thu, 25 Jun 2015 21:02:05 +0000 (UTC)
From: "Chris Westin (JIRA)" <jira@apache.org>
To: issues@drill.apache.org
Message-ID: <JIRA.12839181.1434733779000.20007.1435266125321@Atlassian.JIRA>
In-Reply-To: <JIRA.12839181.1434733779000@Atlassian.JIRA>
References: <JIRA.12839181.1434733779000@Atlassian.JIRA>
 <JIRA.12839181.1434733779844@arcas>
Subject: [jira] [Updated] (DRILL-3322) Something broken in or around RPC
 timeout setup?
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Chris Westin updated DRILL-3322:
--------------------------------
    Affects Version/s: 1.0.0

> Something broken in or around RPC timeout setup?
> ------------------------------------------------
>
>                 Key: DRILL-3322
>                 URL: https://issues.apache.org/jira/browse/DRILL-3322
>             Project: Apache Drill
>          Issue Type: Bug
>          Components: Execution - RPC
>    Affects Versions: 1.0.0
>            Reporter: Daniel Barclay (Drill)
>            Assignee: Jacques Nadeau
>             Fix For: 1.1.0
>
>
> Something(s) in the overall setup for RPC timeouts (heartbeats/watchdog) seems broken.
> Running in the debugger (setting breakpoints, lettings things time out, etc.) has led to a state where the JDBC layer's RPC client code never gets any callbacks (not even an exception callback), and so the JDBC execute..(...) call never returns or even throws.


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