You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@drill.apache.org by "Pritesh Maker (JIRA)" <ji...@apache.org> on 2018/07/12 21:29:00 UTC

[jira] [Updated] (DRILL-6602) Drill query cancellation should log the originator

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

Pritesh Maker updated DRILL-6602:
---------------------------------
    Issue Type: Improvement  (was: Bug)

> Drill query cancellation should log the originator
> --------------------------------------------------
>
>                 Key: DRILL-6602
>                 URL: https://issues.apache.org/jira/browse/DRILL-6602
>             Project: Apache Drill
>          Issue Type: Improvement
>          Components: Execution - Flow
>            Reporter: Khurram Faraaz
>            Priority: Major
>
> The Drill query Cancel functionality does not log the origin of the Cancel request.
> (1). security issue, we don't know who (which user) canceled the query.
> (2). debugging such a canceled query can be a pain to find the origin and the root cause of why a query was canceled.
> On Apache Drill 1.14.0 git.commit.id.abbrev=b0314a3, we have observed this problem, and it can be consistently reproduced. There is no information at all about the origin of why the query was canceled in the drillbit.log
>  



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)