[HADOOP-14518] Customize User-Agent header sent in HTTP/HTTPS requests by WASB.

• Type: Sub-task
• Status: Resolved
• Priority: Minor
• Resolution: Fixed
• Affects Version/s: 3.0.0-beta1
• Fix Version/s: 2.9.0, 3.0.0-beta1
• Component/s: fs/azure
• Target Version/s: 3.0.0-beta1, 2.8.1

Release Note

WASB now includes the current Apache Hadoop version in the User-Agent string passed to Azure Blob service. Users also may include optional additional information to identify their application. See the documentation of configuration property fs.wasb.user.agent.id for further details.

• Flags: Patch
• Assignee: Georgi Chalakov
• Reporter: Georgi Chalakov
• Created: 10/Jun/17 03:12
• Updated: 25/Jul/17 18:22
• Resolved: 25/Jul/17 15:43

Description

WASB passes a User-Agent header to the Azure back-end. Right now, it uses the default value set by the Azure Client SDK, so Hadoop traffic doesn't appear any different from general Blob traffic. If we customize the User-Agent header, then it will enable better troubleshooting and analysis by Azure service.

The following configuration
<property>
<name>fs.azure.user.agent.prefix</name>
<value>MSFT</value>
</property>

set the user agent to
User-Agent: WASB/3.0.0-alpha4-SNAPSHOT (MSFT) Azure-Storage/4.2.0 (JavaJRE 1.8.0_131; WindowsServer2012R2 6.3)

Test Results :
Tests run: 703, Failures: 0, Errors: 0, Skipped: 119

Issue Links

• is depended upon by: HADOOP-14552 Über-jira: WASB client phase II: performance and testing