Mailing-List: contact hdfs-issues-help@hadoop.apache.org; run by ezmlm
Precedence: bulk
Date: Thu, 18 Aug 2016 17:59:20 +0000 (UTC)
From: "Kihwal Lee (JIRA)" <jira@apache.org>
To: hdfs-issues@hadoop.apache.org
Message-ID: <JIRA.12998258.1471541419000.347579.1471543160889@Atlassian.JIRA>
In-Reply-To: <JIRA.12998258.1471541419000@Atlassian.JIRA>
References: <JIRA.12998258.1471541419000@Atlassian.JIRA> <JIRA.12998258.1471541419582@arcas>
Subject: [jira] [Updated] (HDFS-10776) Revisit Hdfs Audit Logging
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable
archived-at: Thu, 18 Aug 2016 17:59:23 -0000


     [ https://issues.apache.org/jira/browse/HDFS-10776?page=3Dcom.atlassia=
n.jira.plugin.system.issuetabpanels:all-tabpanel ]

Kihwal Lee updated HDFS-10776:
------------------------------
    Description:=20
HDFS audit logging is considered critical in many scenarios, but it hasn't =
been always implemented consistently, especially for new features. As we ha=
ve seen in HDFS-9395 and the 2.7.3 release discussions in the mailing list,=
 even bug fixes are tricky since some users may get greatly impacted by the=
 resulting incompatibility.=E2=80=82The goal of this jira is to clarify wha=
t the hdfs audit logging should do and discuss potential approaches that wi=
ll allows us to move forward.

1) What is the correct way of doing the hdfs audit logging? This was discus=
sed in HDFS-9395, but needs to be revisited as there were discussions on th=
e fix being made with wrong assumptions.=E2=80=82What needs to be fixed, if=
 HDFS-9395 is incorrect or incomplete?
2) What if a single standard cannot satisfy everyone? Do we need to make th=
e audit logging more flexible and configurable?
3) What is the best way of introducing future bug fixes to the hdfs audit l=
ogging that change the output?=E2=80=82=E2=80=82Some may not want a fix, wh=
ile others may consider it critical and want it asap.
CC:[~aw]

  was:
HDFS audit logging is considered critical in many scenarios, but it hasn't =
been always implemented consistently, especially for new features. As we ha=
ve seen in HDFS-9395 and the 2.7.3 release discussions in the mailing list,=
 even bug fixes are tricky since some users may get greatly impacted by the=
 resulting incompatibility.=E2=80=82The goal of this jira is to clarify wha=
t the hdfs audit logging should do and discuss potential approaches that wi=
ll allows us to move forward.

1) What is the correct way of doing the hdfs audit logging? This was discus=
sed in HDFS-9395, but needs to be revisited as there were discussions on th=
e fix being made with wrong assumptions.=E2=80=82What needs to be fixed, if=
 HDFS-9395 is incorrect or incomplete?
2) What if a single standard cannot satisfy everyone? Do we need to make th=
e audit logging more flexible and configurable?
3) What is the best way of introducing future bug fixes to the hdfs audit l=
ogging that changes the output?=E2=80=82=E2=80=82Some may not want a fix, w=
hile others may consider it critical and want it asap.
CC:[~aw]


> Revisit Hdfs Audit Logging
> --------------------------
>
>                 Key: HDFS-10776
>                 URL: https://issues.apache.org/jira/browse/HDFS-10776
>             Project: Hadoop HDFS
>          Issue Type: Bug
>    Affects Versions: 2.7.2
>            Reporter: Kuhu Shukla
>            Assignee: Kuhu Shukla
>
> HDFS audit logging is considered critical in many scenarios, but it hasn'=
t been always implemented consistently, especially for new features. As we =
have seen in HDFS-9395 and the 2.7.3 release discussions in the mailing lis=
t, even bug fixes are tricky since some users may get greatly impacted by t=
he resulting incompatibility.=E2=80=82The goal of this jira is to clarify w=
hat the hdfs audit logging should do and discuss potential approaches that =
will allows us to move forward.
> 1) What is the correct way of doing the hdfs audit logging? This was disc=
ussed in HDFS-9395, but needs to be revisited as there were discussions on =
the fix being made with wrong assumptions.=E2=80=82What needs to be fixed, =
if HDFS-9395 is incorrect or incomplete?
> 2) What if a single standard cannot satisfy everyone? Do we need to make =
the audit logging more flexible and configurable?
> 3) What is the best way of introducing future bug fixes to the hdfs audit=
 logging that change the output?=E2=80=82=E2=80=82Some may not want a fix, =
while others may consider it critical and want it asap.
> CC:[~aw]


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

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