You are viewing a plain text version of this content. The canonical link for it is here.
Posted to hdfs-issues@hadoop.apache.org by "Arpit Agarwal (Jira)" <ji...@apache.org> on 2019/09/06 19:13:00 UTC
[jira] [Updated] (HDDS-1666) Improve logic in openKey when
allocating block
[ https://issues.apache.org/jira/browse/HDDS-1666?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Arpit Agarwal updated HDDS-1666:
--------------------------------
Fix Version/s: (was: 0.5.0)
0.4.1
> 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.4.1
>
> 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
(v8.3.2#803003)
---------------------------------------------------------------------
To unsubscribe, e-mail: hdfs-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-help@hadoop.apache.org