[jira] [Updated] (HDDS-1461) Optimize listStatus api in OzoneFileSystem
[ https://issues.apache.org/jira/browse/HDDS-1461?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nanda kumar updated HDDS-1461: -- Fix Version/s: 0.4.1 > 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 > Fix For: 0.5.0, 0.4.1 > > Time Spent: 2h 20m > 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: hdfs-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org
[jira] [Updated] (HDDS-1461) Optimize listStatus api in OzoneFileSystem
[ https://issues.apache.org/jira/browse/HDDS-1461?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lokesh Jain updated HDDS-1461: -- Resolution: Fixed Fix Version/s: 0.5.0 Status: Resolved (was: Patch Available) > 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 > Fix For: 0.5.0 > > Time Spent: 2h 20m > 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: hdfs-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org
[jira] [Updated] (HDDS-1461) Optimize listStatus api in OzoneFileSystem
[ https://issues.apache.org/jira/browse/HDDS-1461?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lokesh Jain updated HDDS-1461: -- Status: Patch Available (was: Open) > 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: hdfs-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org
[jira] [Updated] (HDDS-1461) Optimize listStatus api in OzoneFileSystem
[ https://issues.apache.org/jira/browse/HDDS-1461?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated HDDS-1461: - Labels: pull-request-available (was: ) > 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 > > 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: hdfs-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org
[jira] [Updated] (HDDS-1461) Optimize listStatus api in OzoneFileSystem
[ https://issues.apache.org/jira/browse/HDDS-1461?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lokesh Jain updated HDDS-1461: -- Summary: Optimize listStatus api in OzoneFileSystem (was: Optimize listStatus api in OzoneFileStatus) > 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 > > 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: hdfs-issues-unsubscr...@hadoop.apache.org For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org
