Mailing-List: contact common-dev-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Date: Tue, 1 Nov 2016 23:07:58 +0000 (UTC)
From: "NITIN VERMA (JIRA)" <jira@apache.org>
To: common-dev@hadoop.apache.org
Message-ID: <JIRA.13017033.1478041663000.150386.1478041678410@Atlassian.JIRA>
In-Reply-To: <JIRA.13017033.1478041663000@Atlassian.JIRA>
References: <JIRA.13017033.1478041663000@Atlassian.JIRA> <JIRA.13017033.1478041663906@arcas>
Subject: [jira] [Created] (HADOOP-13783) Improve efficiency of WASB over
 page blobs
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
archived-at: Tue, 01 Nov 2016 23:08:00 -0000

NITIN VERMA created HADOOP-13783:
------------------------------------

             Summary: Improve efficiency of WASB over page blobs
                 Key: HADOOP-13783
                 URL: https://issues.apache.org/jira/browse/HADOOP-13783
             Project: Hadoop Common
          Issue Type: Bug
          Components: azure
            Reporter: NITIN VERMA


1)=09Add telemetry to WASB driver. WASB driver is lack of any log or teleme=
try which makes trouble shoot very difficult. For example, we don=E2=80=99t=
 know where is high e2e latency between HBase and Azure storage came from w=
hen Azure storage server latency was very low. Also we don=E2=80=99t know w=
hy WASB can only do 166 IOPs which is way below azure storage 500 IOPs. And=
 we had several incidents before related to storage latency, because of lac=
king logs, we couldn=E2=80=99t find the ownership of the incident quickly.

2)=09Resolving the hot spotting issue when WASB driver partition the azure =
page blobs by changing the key. Current key design is causing the hot spott=
ing on azure storage.=20


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

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