[ 
https://issues.apache.org/jira/browse/HDDS-1666?focusedWorklogId=277092&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-277092
 ]

ASF GitHub Bot logged work on HDDS-1666:
----------------------------------------

                Author: ASF GitHub Bot
            Created on: 16/Jul/19 00:54
            Start Date: 16/Jul/19 00:54
    Worklog Time Spent: 10m 
      Work Description: arp7 commented on pull request #943: HDDS-1666. Issue 
in openKey when allocating block.
URL: https://github.com/apache/hadoop/pull/943
 
 
   
 
----------------------------------------------------------------
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: 277092)
    Time Spent: 50m  (was: 40m)

> Improve logic in openKey when allocating block
> ----------------------------------------------
>
>                 Key: HDDS-1666
>                 URL: https://issues.apache.org/jira/browse/HDDS-1666
>             Project: Hadoop Distributed Data Store
>          Issue Type: Bug
>            Reporter: Bharat Viswanadham
>            Assignee: Bharat Viswanadham
>            Priority: Major
>              Labels: pull-request-available
>          Time Spent: 50m
>  Remaining Estimate: 0h
>
> We set size as below
> {code}
> final long size = args.getDataSize() >= 0 ?
>  args.getDataSize() : scmBlockSize;
> {code}
>  
> and create OmKeyInfo with below size set. But when allocating Block for 
> openKey, we use as below.
> allocateBlockInKey(keyInfo, args.getDataSize(), currentTime);
>  
> I feel here, we should use size which is set above so that we allocate at 
> least a block when the openKey call happens.



--
This message was sent by Atlassian JIRA
(v7.6.14#76016)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to