[
https://issues.apache.org/jira/browse/HDDS-14355?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ivan Andika updated HDDS-14355:
-------------------------------
Description:
Currently, it seems that OMKeyRequest#allocateBlock calls SCM's allocateBlock
RPC even if the requested size is 0, we can skip this call since the
allocateBlock is redundant. However, for Ozone FS use case
(OMFileCreateRequest), the dataSize is always 0 since Hadoop FileSystem#create
does not specify the data size in advance.
Test should validate that SCM allocateBlock should never be called when
uploading a zero-sized key (either by OMKeyCreateRequest or
OMAllocateBlockRequest (from the BlockOutputStreamEntryPool#allocateNewBlock)).
This might be useful if we only want to test the write OM metadata performance
without involving HDDS layer (i.e. SCM and DN).
was:
Currently, it seems that OMKeyRequest#allocateBlock calls SCM's allocateBlock
RPC even if the requested size is 0, we can skip this call since the
allocateBlock is redundant.
Test should validate that SCM allocateBlock should never be called when
uploading a zero-sized key either by OMKeyCreateRequest or
OMAllocateBlockRequest (from the BlockOutputStreamEntryPool#allocateNewBlock).
This might be useful if we only want to test the write OM metadata performance
without involving HDDS layer (i.e. SCM and DN).
> Allow OM to skip allocateBlock for zero-sized key
> -------------------------------------------------
>
> Key: HDDS-14355
> URL: https://issues.apache.org/jira/browse/HDDS-14355
> Project: Apache Ozone
> Issue Type: Improvement
> Reporter: Ivan Andika
> Assignee: Ivan Andika
> Priority: Major
>
> Currently, it seems that OMKeyRequest#allocateBlock calls SCM's allocateBlock
> RPC even if the requested size is 0, we can skip this call since the
> allocateBlock is redundant. However, for Ozone FS use case
> (OMFileCreateRequest), the dataSize is always 0 since Hadoop
> FileSystem#create does not specify the data size in advance.
> Test should validate that SCM allocateBlock should never be called when
> uploading a zero-sized key (either by OMKeyCreateRequest or
> OMAllocateBlockRequest (from the
> BlockOutputStreamEntryPool#allocateNewBlock)).
> This might be useful if we only want to test the write OM metadata
> performance without involving HDDS layer (i.e. SCM and DN).
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
