drill-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Laurent Goujon (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (DRILL-5218) Support Disabling Heartbeats in C++ Client
Date Tue, 24 Jan 2017 22:23:27 GMT

    [ https://issues.apache.org/jira/browse/DRILL-5218?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15836750#comment-15836750
] 

Laurent Goujon commented on DRILL-5218:
---------------------------------------

https://issues.apache.org/jira/browse/DRILL-5218?focusedCommentId=15836652&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-15836652
{quote}
Doesn't sound like a good idea. A heartbeat is the only reliable way of knowing that the connection
to a drillbit is still alive (and not just taking a very long time to return the results of
a query execution). The client app might be a server application maintaining a connection
pool in which case knowing the health of the connection is an important requirement. 
{quote}

I was wondering about that too. [~sudheeshkatkam], do you have an exemple where it would be
beneficial to disable the heartbeat?

> Support Disabling Heartbeats in C++ Client
> ------------------------------------------
>
>                 Key: DRILL-5218
>                 URL: https://issues.apache.org/jira/browse/DRILL-5218
>             Project: Apache Drill
>          Issue Type: Bug
>          Components: Client - C++
>            Reporter: Sudheesh Katkam
>            Assignee: Sudheesh Katkam
>
> Heartbeats between bits allow for detecting health of remotes, but heartbeats between
client and bit may not be necessary? So allow to (at least) disable heartbeats between C++
client and bit.



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

Mime
View raw message