[
https://issues.apache.org/jira/browse/HDDS-1666?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16885737#comment-16885737
]
Hudson commented on HDDS-1666:
------------------------------
FAILURE: Integrated in Jenkins build Hadoop-trunk-Commit #16921 (See
[https://builds.apache.org/job/Hadoop-trunk-Commit/16921/])
HDDS-1666. Issue in openKey when allocating block. (#943) (arp7: rev
ef66e4999f3cd5f0ea2fa018359facb776bf892f)
* (edit)
hadoop-ozone/integration-test/src/test/java/org/apache/hadoop/ozone/om/TestKeyManagerImpl.java
* (edit)
hadoop-ozone/ozone-manager/src/main/java/org/apache/hadoop/ozone/om/KeyManagerImpl.java
> 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]
