[
https://issues.apache.org/jira/browse/HDDS-1461?focusedWorklogId=234435&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-234435
]
ASF GitHub Bot logged work on HDDS-1461:
----------------------------------------
Author: ASF GitHub Bot
Created on: 29/Apr/19 10:26
Start Date: 29/Apr/19 10:26
Worklog Time Spent: 10m
Work Description: lokeshj1703 commented on pull request #782: HDDS-1461.
Optimize listStatus api in OzoneFileSystem
URL: https://github.com/apache/hadoop/pull/782
Currently in listStatus we make multiple getFileStatus calls. This can be
optimized by converting to a single rpc call for listStatus.
Also currently listStatus has to traverse a directory recursively in order
to list its immediate children. This happens because in OzoneManager all the
metadata is stored in rocksdb sorted on keynames. The Jira also aims to fix
this by using seek api provided by rocksdb.
----------------------------------------------------------------
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: 234435)
Time Spent: 10m
Remaining Estimate: 0h
> Optimize listStatus api in OzoneFileSystem
> ------------------------------------------
>
> Key: HDDS-1461
> URL: https://issues.apache.org/jira/browse/HDDS-1461
> Project: Hadoop Distributed Data Store
> Issue Type: Sub-task
> Components: Ozone Filesystem, Ozone Manager
> Reporter: Lokesh Jain
> Assignee: Lokesh Jain
> Priority: Major
> Labels: pull-request-available
> Time Spent: 10m
> Remaining Estimate: 0h
>
> Currently in listStatus we make multiple getFileStatus calls. This can be
> optimized by converting to a single rpc call for listStatus.
> Also currently listStatus has to traverse a directory recursively in order to
> list its immediate children. This happens because in OzoneManager all the
> metadata is stored in rocksdb sorted on keynames. The Jira also aims to fix
> this by using seek api provided by rocksdb.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]