[
https://issues.apache.org/jira/browse/HDDS-1600?focusedWorklogId=252045&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-252045
]
ASF GitHub Bot logged work on HDDS-1600:
----------------------------------------
Author: ASF GitHub Bot
Created on: 31/May/19 20:39
Start Date: 31/May/19 20:39
Worklog Time Spent: 10m
Work Description: bharatviswa504 commented on pull request #857:
HDDS-1600. Add userName and IPAddress as part of OMRequest.
URL: https://github.com/apache/hadoop/pull/857#discussion_r289543238
##########
File path:
hadoop-ozone/ozone-manager/src/main/java/org/apache/hadoop/ozone/om/request/bucket/OMBucketDeleteRequest.java
##########
@@ -69,15 +65,21 @@ public OMClientResponse
validateAndUpdateCache(OzoneManager ozoneManager,
String volumeName = omRequest.getDeleteBucketRequest().getVolumeName();
String bucketName = omRequest.getDeleteBucketRequest().getBucketName();
- // acquire lock
- omMetadataManager.getLock().acquireBucketLock(volumeName, bucketName);
-
// Generate end user response
OMResponse.Builder omResponse = OMResponse.newBuilder()
.setStatus(OzoneManagerProtocolProtos.Status.OK)
.setCmdType(omRequest.getCmdType());
try {
+ // check Acl
+ if (ozoneManager.getAclsEnabled()) {
+ checkAcls(ozoneManager, OzoneObj.ResourceType.BUCKET,
Review comment:
Right now lock manager does not have readlock acquire on bucket. Do you mean
acquire bucket lock?
And why do we need to acquire lock here? I don't see for any requests
acquire of lock in current OzoneManager.java code.
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
[email protected]
Issue Time Tracking
-------------------
Worklog Id: (was: 252045)
Time Spent: 2h 10m (was: 2h)
> Add userName and IPAddress as part of OMRequest.
> ------------------------------------------------
>
> Key: HDDS-1600
> URL: https://issues.apache.org/jira/browse/HDDS-1600
> Project: Hadoop Distributed Data Store
> Issue Type: Sub-task
> Reporter: Bharat Viswanadham
> Assignee: Bharat Viswanadham
> Priority: Major
> Labels: pull-request-available
> Time Spent: 2h 10m
> Remaining Estimate: 0h
>
> In OM HA, the actual execution of request happens under GRPC context, so UGI
> object which we retrieve from ProtobufRpcEngine.Server.getRemoteUser(); will
> not be available.
> In similar manner ProtobufRpcEngine.Server.getRemoteIp().
>
> So, during preExecute(which happens under RPC context) extract userName and
> IPAddress and add it to the OMRequest, and then send the request to ratis
> server.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
