You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@trafodion.apache.org by "Selvaganesan Govindarajan (JIRA)" <ji...@apache.org> on 2017/10/12 21:49:00 UTC

[jira] [Resolved] (TRAFODION-2696) control query cancel qid fails with error 8031 sometimes

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

Selvaganesan Govindarajan resolved TRAFODION-2696.
--------------------------------------------------
    Resolution: Fixed

> control query cancel qid fails with error 8031 sometimes
> --------------------------------------------------------
>
>                 Key: TRAFODION-2696
>                 URL: https://issues.apache.org/jira/browse/TRAFODION-2696
>             Project: Apache Trafodion
>          Issue Type: Bug
>          Components: sql-exe
>    Affects Versions: any
>            Reporter: Selvaganesan Govindarajan
>            Assignee: Selvaganesan Govindarajan
>             Fix For: 2.2-incubating
>
>
> At times even the long running query fails with the following error message
> *** ERROR[8031] Server declined cancel request for query ID MXID11000025653212367983150736000000000000206U3333300_106___SQLCI_DML_LAST__. The query is not registered with the cancel broker.
> This error  can happen if the ssmp process is restarted after the query start executing. When the ssmp is restarted, the posted query started message is lost and hence the query can't be cancelled. However, we can minimize this failure by avoiding ssmp restarts within the engine whereever possible.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)