[jira] [Updated] (HDDS-1987) Fix listStatus API

2019-11-18 Thread Siyao Meng (Jira)


 [ 
https://issues.apache.org/jira/browse/HDDS-1987?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Siyao Meng updated HDDS-1987:
-
Status: Patch Available  (was: In Progress)

> Fix listStatus API
> --
>
> Key: HDDS-1987
> URL: https://issues.apache.org/jira/browse/HDDS-1987
> Project: Hadoop Distributed Data Store
>  Issue Type: Sub-task
>Reporter: Bharat Viswanadham
>Assignee: Siyao Meng
>Priority: Major
>  Labels: pull-request-available
>  Time Spent: 10m
>  Remaining Estimate: 0h
>
> This Jira is to fix listStatus API in HA code path.
> In HA, we have an in-memory cache, where we put the result to in-memory cache 
> and return the response. It will be picked by double buffer thread and 
> flushed to disk later. So when user call listStatus, it should use both 
> in-memory cache and rocksdb key table to return the correct result.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

-
To unsubscribe, e-mail: hdfs-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org



[jira] [Updated] (HDDS-1987) Fix listStatus API

2019-10-30 Thread ASF GitHub Bot (Jira)


 [ 
https://issues.apache.org/jira/browse/HDDS-1987?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

ASF GitHub Bot updated HDDS-1987:
-
Labels: pull-request-available  (was: )

> Fix listStatus API
> --
>
> Key: HDDS-1987
> URL: https://issues.apache.org/jira/browse/HDDS-1987
> Project: Hadoop Distributed Data Store
>  Issue Type: Sub-task
>Reporter: Bharat Viswanadham
>Assignee: Siyao Meng
>Priority: Major
>  Labels: pull-request-available
>
> This Jira is to fix listStatus API in HA code path.
> In HA, we have an in-memory cache, where we put the result to in-memory cache 
> and return the response. It will be picked by double buffer thread and 
> flushed to disk later. So when user call listStatus, it should use both 
> in-memory cache and rocksdb key table to return the correct result.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

-
To unsubscribe, e-mail: hdfs-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org



[jira] [Updated] (HDDS-1987) Fix listStatus API

2019-10-30 Thread Siyao Meng (Jira)


 [ 
https://issues.apache.org/jira/browse/HDDS-1987?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Siyao Meng updated HDDS-1987:
-
Description: 
This Jira is to fix listStatus API in HA code path.

In HA, we have an in-memory cache, where we put the result to in-memory cache 
and return the response. It will be picked by double buffer thread and flushed 
to disk later. So when user call listStatus, it should use both in-memory cache 
and rocksdb key table to return the correct result.

  was:
This Jira is to fix listStatus API in HA code path.

In HA, we have an in-memory cache, where we put the result to in-memory cache 
and return the response, later it will be picked by double buffer thread and it 
will flush to disk. So, now when do listStatus, it should use both in-memory 
cache and rocksdb key table to listStatus in a bucket.


> Fix listStatus API
> --
>
> Key: HDDS-1987
> URL: https://issues.apache.org/jira/browse/HDDS-1987
> Project: Hadoop Distributed Data Store
>  Issue Type: Sub-task
>Reporter: Bharat Viswanadham
>Assignee: Siyao Meng
>Priority: Major
>
> This Jira is to fix listStatus API in HA code path.
> In HA, we have an in-memory cache, where we put the result to in-memory cache 
> and return the response. It will be picked by double buffer thread and 
> flushed to disk later. So when user call listStatus, it should use both 
> in-memory cache and rocksdb key table to return the correct result.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

-
To unsubscribe, e-mail: hdfs-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org



[jira] [Updated] (HDDS-1987) Fix listStatus API

2019-10-14 Thread Siyao Meng (Jira)


 [ 
https://issues.apache.org/jira/browse/HDDS-1987?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Siyao Meng updated HDDS-1987:
-
Description: 
This Jira is to fix listStatus API in HA code path.

In HA, we have an in-memory cache, where we put the result to in-memory cache 
and return the response, later it will be picked by double buffer thread and it 
will flush to disk. So, now when do listStatus, it should use both in-memory 
cache and rocksdb key table to listStatus in a bucket.

  was:
This Jira is to fix listKeys API in HA code path.

In HA, we have an in-memory cache, where we put the result to in-memory cache 
and return the response, later it will be picked by double buffer thread and it 
will flush to disk. So, now when do listStatus, it should use both in-memory 
cache and rocksdb key table to list Status of Keys in a bucket.


> Fix listStatus API
> --
>
> Key: HDDS-1987
> URL: https://issues.apache.org/jira/browse/HDDS-1987
> Project: Hadoop Distributed Data Store
>  Issue Type: Sub-task
>Reporter: Bharat Viswanadham
>Assignee: Siyao Meng
>Priority: Major
>
> This Jira is to fix listStatus API in HA code path.
> In HA, we have an in-memory cache, where we put the result to in-memory cache 
> and return the response, later it will be picked by double buffer thread and 
> it will flush to disk. So, now when do listStatus, it should use both 
> in-memory cache and rocksdb key table to listStatus in a bucket.



--
This message was sent by Atlassian Jira
(v8.3.4#803005)

-
To unsubscribe, e-mail: hdfs-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org



[jira] [Updated] (HDDS-1987) Fix listStatus API

2019-08-19 Thread Bharat Viswanadham (Jira)


 [ 
https://issues.apache.org/jira/browse/HDDS-1987?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Bharat Viswanadham updated HDDS-1987:
-
Description: 
This Jira is to fix listKeys API in HA code path.

In HA, we have an in-memory cache, where we put the result to in-memory cache 
and return the response, later it will be picked by double buffer thread and it 
will flush to disk. So, now when do listStatus, it should use both in-memory 
cache and rocksdb key table to list Status of Keys in a bucket.

  was:
This Jira is to fix listKeys API in HA code path.

In HA, we have an in-memory cache, where we put the result to in-memory cache 
and return the response, later it will be picked by double buffer thread and it 
will flush to disk. So, now when do listkeys, it should use both in-memory 
cache and rocksdb key table to list keys in a bucket.


> Fix listStatus API
> --
>
> Key: HDDS-1987
> URL: https://issues.apache.org/jira/browse/HDDS-1987
> Project: Hadoop Distributed Data Store
>  Issue Type: Sub-task
>Reporter: Bharat Viswanadham
>Priority: Major
>
> This Jira is to fix listKeys API in HA code path.
> In HA, we have an in-memory cache, where we put the result to in-memory cache 
> and return the response, later it will be picked by double buffer thread and 
> it will flush to disk. So, now when do listStatus, it should use both 
> in-memory cache and rocksdb key table to list Status of Keys in a bucket.



--
This message was sent by Atlassian Jira
(v8.3.2#803003)

-
To unsubscribe, e-mail: hdfs-issues-unsubscr...@hadoop.apache.org
For additional commands, e-mail: hdfs-issues-h...@hadoop.apache.org