Steve Loughran created HADOOP-15188:
---------------------------------------
Summary: 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.1.0
Reporter: Steve Loughran
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-dev-unsubscr...@hadoop.apache.org
For additional commands, e-mail: common-dev-h...@hadoop.apache.org
