[HADOOP-15188] azure datalake AzureADAuthenticator failing, no error info provided

• Type: Bug
• Status: Open
• Priority: Minor
• Resolution: Unresolved
• Affects Version/s: 3.0.0, 3.1.0
• Component/s: fs/adl
• Assignee: Atul Sikaria
• Reporter: Steve Loughran
• Created: 23/Jan/18 17:43
• Updated: 26/Mar/18 18:12

Description

Get a failure in ADLS client, but nothing useful in terms of failure description

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

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.

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();

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.

Issue Links

• Is contained by: HADOOP-15342 Update ADLS connector to use the current SDK version (2.2.7)