[ 
https://issues.apache.org/jira/browse/HDDS-4228?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Glen Geng updated HDDS-4228:
----------------------------
    Description: 
 

The scm audit log for ALLOCATE_BLOCK is as follows:
{code:java}
2020-09-10 03:42:08,196 | INFO | SCMAudit | user=root | ip=172.16.90.221 | 
op=ALLOCATE_BLOCK {owner=7da0b4c4-d053-4fa0-8648-44ff0b8ba1bf, size=268435456, 
type=RATIS, factor=THREE} | ret=SUCCESS |{code}
 

One might be interested about the num of blocks allocated, better add field 
'num' to  ALLOCATE_BLOCK of scm audit log.

  was:
 

The scm audit log for ALLOCATE_BLOCK is as follows:
{code:java}
2020-09-10 03:42:08,196 | INFO | SCMAudit | user=root | ip=172.16.90.221 | 
op=ALLOCATE_BLOCK {owner=7da0b4c4-d053-4fa0-8648-44ff0b8ba1bf, size=268435456, 
type=RATIS, factor=THREE} | ret=SUCCESS |{code}
 

Better add num of blocks allocated into the audit log, one might be interested 
about the num of blocks allocated, better add field 'num' to 


> add field 'num' to ALLOCATE_BLOCK of scm audit log.
> ---------------------------------------------------
>
>                 Key: HDDS-4228
>                 URL: https://issues.apache.org/jira/browse/HDDS-4228
>             Project: Hadoop Distributed Data Store
>          Issue Type: Improvement
>            Reporter: Glen Geng
>            Assignee: Glen Geng
>            Priority: Minor
>
>  
> The scm audit log for ALLOCATE_BLOCK is as follows:
> {code:java}
> 2020-09-10 03:42:08,196 | INFO | SCMAudit | user=root | ip=172.16.90.221 | 
> op=ALLOCATE_BLOCK {owner=7da0b4c4-d053-4fa0-8648-44ff0b8ba1bf, 
> size=268435456, type=RATIS, factor=THREE} | ret=SUCCESS |{code}
>  
> One might be interested about the num of blocks allocated, better add field 
> 'num' to  ALLOCATE_BLOCK of scm audit log.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

---------------------------------------------------------------------
To unsubscribe, e-mail: ozone-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: ozone-issues-h...@hadoop.apache.org

Reply via email to