[
https://issues.apache.org/jira/browse/HDDS-9679?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ivan Andika updated HDDS-9679:
------------------------------
Description:
In the Ozone Manager, there are requests related to Multipart Upload (MPU),
they are:
* MPU Init Request: S3InitiateMultipartUploadRequest &
S3InitiateMultipartUploadRequestWithFSO
* MPU Commit Part Request: S3MultipartUploadCommitPartRequest &
S3MultipartUploadCommitPartRequestWithFSO
* MPU Complete Request: S3MultipartUploadCompleteRequest &
S3MultipartUploadCompleteRequestWithFSO
* MPU Abort Request: S3MultipartUploadAbortRequest &
S3MultipartUploadAbortRequestWithFSO
In these requests, an audit map is created using
RequestAuditor#buildKeyArgsAuditMap which includes information related to
general Ozone key (e.g. volume, bucket, key, data size, replication config).
Since the same multipart key can be created using different multipart upload
ID, it will be useful to add upload ID into requests related to multipart
upload. This can be used to trace the status of a single MPU (which has a
unique upload ID)
This can be done by including the upload ID (keyArgs#getMultipartUploadID) in
the audit map.
was:
In the Ozone Manager, there are requests related to Multipart Upload (MPU),
they are:
* MPU Init Request: S3InitiateMultipartUploadRequest &
S3InitiateMultipartUploadRequestWithFSO
* MPU Commit Part Request: S3MultipartUploadCommitPartRequest &
S3MultipartUploadCommitPartRequestWithFSO
* MPU Complete Request: S3MultipartUploadCompleteRequest &
S3MultipartUploadCompleteRequestWithFSO
* MPU Abort Request: S3MultipartUploadAbortRequest &
S3MultipartUploadAbortRequestWithFSO
In these requests, an audit map is created using
RequestAuditor#buildKeyArgsAuditMap which includes information related to
general Ozone key (e.g. volume, bucket, key, data size, replication config).
Since the same multipart key can be created using different multipart upload
ID, it will be useful to add upload ID into requests related to multipart
upload.
This can be done by including the uploadId in the audit map.
> Add Multipart Upload ID into the audit logs
> -------------------------------------------
>
> Key: HDDS-9679
> URL: https://issues.apache.org/jira/browse/HDDS-9679
> Project: Apache Ozone
> Issue Type: Improvement
> Reporter: Ivan Andika
> Priority: Minor
> Labels: newbie
>
> In the Ozone Manager, there are requests related to Multipart Upload (MPU),
> they are:
> * MPU Init Request: S3InitiateMultipartUploadRequest &
> S3InitiateMultipartUploadRequestWithFSO
> * MPU Commit Part Request: S3MultipartUploadCommitPartRequest &
> S3MultipartUploadCommitPartRequestWithFSO
> * MPU Complete Request: S3MultipartUploadCompleteRequest &
> S3MultipartUploadCompleteRequestWithFSO
> * MPU Abort Request: S3MultipartUploadAbortRequest &
> S3MultipartUploadAbortRequestWithFSO
> In these requests, an audit map is created using
> RequestAuditor#buildKeyArgsAuditMap which includes information related to
> general Ozone key (e.g. volume, bucket, key, data size, replication config).
> Since the same multipart key can be created using different multipart upload
> ID, it will be useful to add upload ID into requests related to multipart
> upload. This can be used to trace the status of a single MPU (which has a
> unique upload ID)
> This can be done by including the upload ID (keyArgs#getMultipartUploadID) in
> the audit map.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
