[jira] [Commented] (HAWQ-416) core dump when cancel delegation token if fatal error happened when setup connection to NAMENODE

["Zhanwei Wang (JIRA)" <ji...@apache.org>]

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

Zhanwei Wang commented on HAWQ-416:
-----------------------------------

Fatal error will happen at this case.

1) HAWQ try to login to kerberos and connect Namenode to apply delegation token. This step may be blocked for some network issue.
2) Customer lose patience and cancel the query. But cancelation is blocked too since applying delegation is a block operation.
3) Customer become crazy and close the connection to master.  
4) Applying delegation token failed and try to report error. 
5) HAWQ try to send error message to master and found the cancelation flag.
6) HAWQ found that connection has been closed and escalate to FATAL.

{code}
if (ClientConnectionLost)
	{
		QueryCancelPending = false;		/* lost connection trumps QueryCancel */
		ImmediateInterruptOK = false;	/* not idle anymore */
		DisableNotifyInterrupt();
		DisableCatchupInterrupt();
		/* don't send to client, we already know the connection to be dead. */
		whereToSendOutput = DestNone;
		ereport(FATAL,
				(errcode(ERRCODE_CONNECTION_FAILURE),
				 errmsg("connection to client lost")));
	}
{code}

> core dump when cancel delegation token if fatal error happened when setup connection to NAMENODE
> ------------------------------------------------------------------------------------------------
>
>                 Key: HAWQ-416
>                 URL: https://issues.apache.org/jira/browse/HAWQ-416
>             Project: Apache HAWQ
>          Issue Type: Bug
>          Components: Core
>            Reporter: Zhanwei Wang
>            Assignee: Lei Chang
>




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