accumulo-notifications mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "James Mello (JIRA)" <>
Subject [jira] [Commented] (ACCUMULO-3946) Not all accumulo events are audited for Audit logging
Date Thu, 06 Aug 2015 21:14:07 GMT


James Mello commented on ACCUMULO-3946:

So looking at the code it appears that rolling up things into a single audit event is going
to be difficult. I can take the MasterRepo classes that are executed by Fate and instrument
the steps. But because this appears to be a chain of command pattern there is no one event
that I can use in the Fate execution calls to say that an operation is done. For the termination
of the chain I can mention success, but for intermediate failures I won't be able to.

For example the flow for a create table

CreateTable -> SetupPermissions -> PopulateZookeeper -> CreateDir -> PopulateMetadata
-> FinishCreateTable

I suppose since these classes are imperatively tied to each other I can log the start (CreateTable)
and the end (FinishCreateTable) for a successful create. And for the intermediate steps log
that table creation failed during one of the other operations. Does this sound good?

> Not all accumulo events are audited for Audit logging
> -----------------------------------------------------
>                 Key: ACCUMULO-3946
>                 URL:
>             Project: Accumulo
>          Issue Type: Bug
>    Affects Versions: 1.5.3
>            Reporter: James Mello
>            Assignee: James Mello
>             Fix For: 1.5.4
> Currently accumulo does not log all the major events such as table creation and permissions
changes. Please modify the existing logging to include missing auditing. Note this is related
to ticket ACCUMUO-3939.

This message was sent by Atlassian JIRA

View raw message