[jira] [Commented] (HADOOP-15188) azure datalake AzureADAuthenticator failing, no error info provided

["Steve Loughran (JIRA)" <ji...@apache.org>]

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

Steve Loughran commented on HADOOP-15188:
-----------------------------------------

Update on this : you see it if there is a proxy in the way and the returned message is not JSON

# the ADL SDK should be checking content-type for being JSON and content length >0 before trying to parse the JSON; reporting the failures differently.
# reporting proxy settings at debug level would also be useful.

see also [[https://github.com/steveloughran/cloudstore]], which was used to track down this issue

> azure datalake AzureADAuthenticator failing, no error info provided
> -------------------------------------------------------------------
>
>                 Key: HADOOP-15188
>                 URL: https://issues.apache.org/jira/browse/HADOOP-15188
>             Project: Hadoop Common
>          Issue Type: Bug
>          Components: fs/adl
>    Affects Versions: 3.0.0, 3.1.0
>            Reporter: Steve Loughran
>            Assignee: Atul Sikaria
>            Priority: Major
>
> Get a failure in ADLS client, but nothing useful in terms of failure description
> {code}
> DEBUG oauth2.AzureADAuthenticator: AADToken: starting to fetch token using client creds for client ID <omitted>
> DEBUG store.HttpTransport: HTTPRequest,Failed,cReqId:<omitted>,lat:127370,err:HTTP0(null),Reqlen:0,Resplen:0,token_ns:<omitted>,sReqId:null,path:<omitted>,qp:op=GETFILESTATUS&tooid=true&api-version=2016-11-01
> {code}
> so: we had a failure but the response code is 0, error(null); "something happened but we don't know what"
> Looks like this log message is in the ADLS SDK, and can be translated like this.
> {code}
> String logline =
>   "HTTPRequest," + outcome +
>   ",cReqId:" + opts.requestid +
>   ",lat:" + Long.toString(resp.lastCallLatency) +
>   ",err:" + error +
>   ",Reqlen:" + length +
>   ",Resplen:" + respLength +
>   ",token_ns:" + Long.toString(resp.tokenAcquisitionLatency) +
>   ",sReqId:" + resp.requestId +
>   ",path:" + path +
>   ",qp:" + queryParams.serialize();
> {code}
> It looks like whatever code tries to parse the JSON response from the OAuth service couldn't make sense of the response, and we end up with nothing back. 
> Not sure what can be done in hadoop to handle this, except maybe provide more diags on request failures.



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

---------------------------------------------------------------------
To unsubscribe, e-mail: common-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: common-issues-help@hadoop.apache.org