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

Arpit Agarwal updated HDDS-1666:
--------------------------------
          Resolution: Fixed
       Fix Version/s: 0.5.0
    Target Version/s:   (was: 0.4.1)
              Status: Resolved  (was: Patch Available)

+1.

I've committed this via GitHub. Thanks for the contribution [~bharatviswa]!

> 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
>             Fix For: 0.5.0
>
>          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