[jira] [Commented] (HDFS-14646) Standby NameNode should not upload fsimage to an inappropriate NameNode.

2023-09-18 Thread Matthew Sharp (Jira)


[ 
https://issues.apache.org/jira/browse/HDFS-14646?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17766559#comment-17766559
 ] 

Matthew Sharp commented on HDFS-14646:
--

We hit this running Hadoop 3.3.0 as well with 3 NNs.  It stayed quiet for years 
until we saw enough write activity.  The txns since last checkpoint metrics 
would show a really bad lag and eventually got far enough out that one of the 
SNNs would crash since it couldn't find the older txn id. Shutting down one SNN 
over the last few weeks seems to have resolved this so it does appear to be an 
active issue running 3 NNs.  It may be worth noting that the fsimage size did 
not seem to play too much of a factor.  We see this logging exceptions in a dev 
cluster which is only hundreds of MBs.

> Standby NameNode should not upload fsimage to an inappropriate NameNode.
> 
>
> Key: HDFS-14646
> URL: https://issues.apache.org/jira/browse/HDFS-14646
> Project: Hadoop HDFS
>  Issue Type: Bug
>  Components: hdfs
>Affects Versions: 3.1.2
>Reporter: Xudong Cao
>Assignee: Xudong Cao
>Priority: Major
>  Labels: multi-sbnn
> Attachments: HDFS-14646.000.patch, HDFS-14646.001.patch, 
> HDFS-14646.002.patch
>
>
> *Problem Description:*
>  In the multi-NameNode scenario, when a SNN uploads a FsImage, it will put 
> the image to all other NNs (whether the peer NN is an ANN or not), and even 
> if the peer NN immediately replies an error (such as 
> TransferResult.NOT_ACTIVE_NAMENODE_FAILURE, TransferResult 
> .OLD_TRANSACTION_ID_FAILURE, etc.), the local SNN will not terminate the put 
> process immediately, but will put the FsImage completely to the peer NN, and 
> will not read the peer NN's reply until the put is completed.
> Depending on the version of Jetty, this behavior can lead to different 
> consequences : 
> *1.Under Hadoop 2.7.2 (with Jetty 6.1.26)*
>  After peer NN called HttpServletResponse.sendError(), the underlying TCP 
> connection will still be established, and the data SNN sent will be read by 
> Jetty framework itself in the peer NN side, so the SNN will insignificantly 
> send the FsImage to the peer NN continuously, causing a waste of time and 
> bandwidth. In a relatively large HDFS cluster, the size of FsImage can often 
> reach about 30GB, This is indeed a big waste.
> *2.Under newest release-3.2.0-RC1 (with Jetty 9.3.24) and trunk (with Jetty 
> 9.3.27)*
>  After peer NN called HttpServletResponse.sendError(), the underlying TCP 
> connection will be auto closed, and then SNN will directly get an "Error 
> writing request body to server" exception, as below, note this test needs a 
> relatively big FSImage (e.g. 10MB level):
> {code:java}
> 2019-08-17 03:59:25,413 INFO namenode.TransferFsImage: Sending fileName: 
> /tmp/hadoop-root/dfs/name/current/fsimage_3364240, fileSize: 
> 9864721. Sent total: 524288 bytes. Size of last segment intended to send: 
> 4096 bytes.
>  java.io.IOException: Error writing request body to server
>  at 
> sun.net.www.protocol.http.HttpURLConnection$StreamingOutputStream.checkError(HttpURLConnection.java:3587)
>  at 
> sun.net.www.protocol.http.HttpURLConnection$StreamingOutputStream.write(HttpURLConnection.java:3570)
>  at 
> org.apache.hadoop.hdfs.server.namenode.TransferFsImage.copyFileToStream(TransferFsImage.java:396)
>  at 
> org.apache.hadoop.hdfs.server.namenode.TransferFsImage.writeFileToPutRequest(TransferFsImage.java:340)
>  at 
> org.apache.hadoop.hdfs.server.namenode.TransferFsImage.uploadImage(TransferFsImage.java:314)
>  at 
> org.apache.hadoop.hdfs.server.namenode.TransferFsImage.uploadImageFromStorage(TransferFsImage.java:249)
>  at 
> org.apache.hadoop.hdfs.server.namenode.ha.StandbyCheckpointer$1.call(StandbyCheckpointer.java:277)
>  at 
> org.apache.hadoop.hdfs.server.namenode.ha.StandbyCheckpointer$1.call(StandbyCheckpointer.java:272)
>  at java.util.concurrent.FutureTask.run(FutureTask.java:266)
>  at 
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
>  at 
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
>  at java.lang.Thread.run(Thread.java:748)
>  2019-08-17 03:59:25,422 INFO namenode.TransferFsImage: Sending fileName: 
> /tmp/hadoop-root/dfs/name/current/fsimage_3364240, fileSize: 
> 9864721. Sent total: 851968 bytes. Size of last segment intended to send: 
> 4096 bytes.
>  java.io.IOException: Error writing request body to server
>  at 
> sun.net.www.protocol.http.HttpURLConnection$StreamingOutputStream.checkError(HttpURLConnection.java:3587)
>  at 
> sun.net.www.protocol.http.HttpURLConnection$StreamingOutputStream.write(HttpURLConnection.java:3570)
>  at 
> org.apache.hadoop.hdfs.server.namenode.TransferFsImage.copy

[jira] [Created] (HDDS-2537) Opentracing - Deprecated Members

2019-11-18 Thread Matthew Sharp (Jira)
Matthew Sharp created HDDS-2537:
---

 Summary: Opentracing - Deprecated Members
 Key: HDDS-2537
 URL: https://issues.apache.org/jira/browse/HDDS-2537
 Project: Hadoop Distributed Data Store
  Issue Type: Improvement
Reporter: Matthew Sharp


When the opentracing-util dependency is upgraded, there will be future cleanup 
work needed with a couple deprecated members starting with 0.31.0 (current 
version used today).

 

A full deprecated members list can be found here:

[https://github.com/opentracing/opentracing-java]



--
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] [Created] (HDDS-2512) Sonar TraceAllMethod NPE Could be Thrown

2019-11-15 Thread Matthew Sharp (Jira)
Matthew Sharp created HDDS-2512:
---

 Summary: Sonar TraceAllMethod NPE Could be Thrown
 Key: HDDS-2512
 URL: https://issues.apache.org/jira/browse/HDDS-2512
 Project: Hadoop Distributed Data Store
  Issue Type: Bug
Reporter: Matthew Sharp
Assignee: Matthew Sharp


Sonar cleanup: 
[https://sonarcloud.io/project/issues?id=hadoop-ozone&issues=AW5md-2WKcVY8lQ4ZsNQ&open=AW5md-2WKcVY8lQ4ZsNQ]

 

 



--
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-2495) Sonar - "notify" may not wake up the appropriate thread

2019-11-14 Thread Matthew Sharp (Jira)


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

Matthew Sharp updated HDDS-2495:

Description: 
Addresses same issue within ReplicationManager:

[https://sonarcloud.io/project/issues?id=hadoop-ozone&issues=AW5md-sVKcVY8lQ4ZsDi&open=AW5md-sVKcVY8lQ4ZsDi]

[https://sonarcloud.io/project/issues?id=hadoop-ozone&issues=AW5md-sVKcVY8lQ4ZsDh&open=AW5md-sVKcVY8lQ4ZsDh]

  was:
[https://sonarcloud.io/project/issues?id=hadoop-ozone&issues=AW5md-sVKcVY8lQ4ZsDi&open=AW5md-sVKcVY8lQ4ZsDi]

 

[https://sonarcloud.io/project/issues?id=hadoop-ozone&issues=AW5md-sVKcVY8lQ4ZsDh&open=AW5md-sVKcVY8lQ4ZsDh]


> Sonar - "notify" may not wake up the appropriate thread
> ---
>
> Key: HDDS-2495
> URL: https://issues.apache.org/jira/browse/HDDS-2495
> Project: Hadoop Distributed Data Store
>  Issue Type: Bug
>Reporter: Matthew Sharp
>Assignee: Matthew Sharp
>Priority: Minor
>
> Addresses same issue within ReplicationManager:
> [https://sonarcloud.io/project/issues?id=hadoop-ozone&issues=AW5md-sVKcVY8lQ4ZsDi&open=AW5md-sVKcVY8lQ4ZsDi]
> [https://sonarcloud.io/project/issues?id=hadoop-ozone&issues=AW5md-sVKcVY8lQ4ZsDh&open=AW5md-sVKcVY8lQ4ZsDh]



--
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] [Created] (HDDS-2495) Sonar - "notify" may not wake up the appropriate thread

2019-11-14 Thread Matthew Sharp (Jira)
Matthew Sharp created HDDS-2495:
---

 Summary: Sonar - "notify" may not wake up the appropriate thread
 Key: HDDS-2495
 URL: https://issues.apache.org/jira/browse/HDDS-2495
 Project: Hadoop Distributed Data Store
  Issue Type: Bug
Reporter: Matthew Sharp
Assignee: Matthew Sharp


[https://sonarcloud.io/project/issues?id=hadoop-ozone&issues=AW5md-sVKcVY8lQ4ZsDi&open=AW5md-sVKcVY8lQ4ZsDi]

 

[https://sonarcloud.io/project/issues?id=hadoop-ozone&issues=AW5md-sVKcVY8lQ4ZsDh&open=AW5md-sVKcVY8lQ4ZsDh]



--
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] [Work started] (HDDS-2494) Sonar - BigDecimal(double) should not be used

2019-11-14 Thread Matthew Sharp (Jira)


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

Work on HDDS-2494 started by Matthew Sharp.
---
> Sonar - BigDecimal(double) should not be used
> -
>
> Key: HDDS-2494
> URL: https://issues.apache.org/jira/browse/HDDS-2494
> Project: Hadoop Distributed Data Store
>  Issue Type: Bug
>Reporter: Matthew Sharp
>Assignee: Matthew Sharp
>Priority: Minor
>
> Sonar Issue:  
> [https://sonarcloud.io/project/issues?id=hadoop-ozone&issues=AW5md-0AKcVY8lQ4ZsKR&open=AW5md-0AKcVY8lQ4ZsKR]
>  
>  



--
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] [Created] (HDDS-2494) Sonar - BigDecimal(double) should not be used

2019-11-14 Thread Matthew Sharp (Jira)
Matthew Sharp created HDDS-2494:
---

 Summary: Sonar - BigDecimal(double) should not be used
 Key: HDDS-2494
 URL: https://issues.apache.org/jira/browse/HDDS-2494
 Project: Hadoop Distributed Data Store
  Issue Type: Bug
Reporter: Matthew Sharp
Assignee: Matthew Sharp


Sonar Issue:  
[https://sonarcloud.io/project/issues?id=hadoop-ozone&issues=AW5md-0AKcVY8lQ4ZsKR&open=AW5md-0AKcVY8lQ4ZsKR]

 

 



--
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] [Created] (HDDS-2484) Ozone Manager - New Metrics for Trash Key Lists and Fails

2019-11-14 Thread Matthew Sharp (Jira)
Matthew Sharp created HDDS-2484:
---

 Summary: Ozone Manager - New Metrics for Trash Key Lists and Fails
 Key: HDDS-2484
 URL: https://issues.apache.org/jira/browse/HDDS-2484
 Project: Hadoop Distributed Data Store
  Issue Type: Sub-task
Reporter: Matthew Sharp
Assignee: Matthew Sharp


We should add new metrics to track trash key lists and fails to OMMetrics

Naming recommendations: NumTrashKeyLists, NumTrashKeyListFails



--
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] [Assigned] (HDDS-2457) Add the ability to get the list of buckets that are deleted

2019-11-10 Thread Matthew Sharp (Jira)


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

Matthew Sharp reassigned HDDS-2457:
---

Assignee: Matthew Sharp

> Add the ability to get the list of buckets that are deleted
> ---
>
> Key: HDDS-2457
> URL: https://issues.apache.org/jira/browse/HDDS-2457
> Project: Hadoop Distributed Data Store
>  Issue Type: Sub-task
>Reporter: Matthew Sharp
>Assignee: Matthew Sharp
>Priority: Major
>
> The initial focus is returning a list of deleted keys, but showing the 
> deleted buckets should be explored further.



--
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] [Assigned] (HDDS-2440) Add empty-trash to ozone shell.

2019-11-10 Thread Matthew Sharp (Jira)


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

Matthew Sharp reassigned HDDS-2440:
---

Assignee: Matthew Sharp

> Add empty-trash to ozone shell.
> ---
>
> Key: HDDS-2440
> URL: https://issues.apache.org/jira/browse/HDDS-2440
> Project: Hadoop Distributed Data Store
>  Issue Type: Sub-task
>  Components: Ozone CLI
>Reporter: Anu Engineer
>Assignee: Matthew Sharp
>Priority: Major
>
> Add emptry-trash command to Ozone shell. We should decide if we want to add 
> this to the admin shell or normal shell.



--
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] [Assigned] (HDDS-2439) Add robot tests for empty-trash as owner.

2019-11-10 Thread Matthew Sharp (Jira)


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

Matthew Sharp reassigned HDDS-2439:
---

Assignee: Matthew Sharp

> Add robot tests for empty-trash as owner.
> -
>
> Key: HDDS-2439
> URL: https://issues.apache.org/jira/browse/HDDS-2439
> Project: Hadoop Distributed Data Store
>  Issue Type: Sub-task
>  Components: Ozone Manager
>Reporter: Anu Engineer
>Assignee: Matthew Sharp
>Priority: Major
>
> We need to make sure that only Owner or Admins can execute the empty-trash 
> command. We need to verify this using end-to-end tests, for example, robot 
> tests



--
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] [Assigned] (HDDS-2441) Add documentation for Empty-Trash command.

2019-11-10 Thread Matthew Sharp (Jira)


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

Matthew Sharp reassigned HDDS-2441:
---

Assignee: Matthew Sharp

> Add documentation for Empty-Trash command.
> --
>
> Key: HDDS-2441
> URL: https://issues.apache.org/jira/browse/HDDS-2441
> Project: Hadoop Distributed Data Store
>  Issue Type: Sub-task
>  Components: documentation
>Reporter: Anu Engineer
>Assignee: Matthew Sharp
>Priority: Major
>
> Add documentation for empty-trash command.



--
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] [Assigned] (HDDS-2434) Add server side support for empty-trash command.

2019-11-10 Thread Matthew Sharp (Jira)


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

Matthew Sharp reassigned HDDS-2434:
---

Assignee: Matthew Sharp

> Add server side support for empty-trash command.
> 
>
> Key: HDDS-2434
> URL: https://issues.apache.org/jira/browse/HDDS-2434
> Project: Hadoop Distributed Data Store
>  Issue Type: Sub-task
>  Components: Ozone Manager
>Reporter: Anu Engineer
>Assignee: Matthew Sharp
>Priority: Major
>
> Add server side support for empty-trash command.



--
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] [Assigned] (HDDS-2438) Add the core logic for empty-trash

2019-11-10 Thread Matthew Sharp (Jira)


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

Matthew Sharp reassigned HDDS-2438:
---

Assignee: Matthew Sharp

> Add the core logic for empty-trash
> --
>
> Key: HDDS-2438
> URL: https://issues.apache.org/jira/browse/HDDS-2438
> Project: Hadoop Distributed Data Store
>  Issue Type: Sub-task
>  Components: Ozone Manager
>Reporter: Anu Engineer
>Assignee: Matthew Sharp
>Priority: Major
>




--
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] [Assigned] (HDDS-2433) Add client side support for the empty-trash command.

2019-11-10 Thread Matthew Sharp (Jira)


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

Matthew Sharp reassigned HDDS-2433:
---

Assignee: Matthew Sharp

> Add client side support for the empty-trash command.
> 
>
> Key: HDDS-2433
> URL: https://issues.apache.org/jira/browse/HDDS-2433
> Project: Hadoop Distributed Data Store
>  Issue Type: Sub-task
>  Components: Ozone Manager
>Reporter: Anu Engineer
>Assignee: Matthew Sharp
>Priority: Major
>
> Add client side support for the empty-trash command.



--
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] [Assigned] (HDDS-2437) Restrict empty-trash to admins and owners only

2019-11-10 Thread Matthew Sharp (Jira)


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

Matthew Sharp reassigned HDDS-2437:
---

Assignee: Matthew Sharp

> Restrict empty-trash to admins and owners only
> --
>
> Key: HDDS-2437
> URL: https://issues.apache.org/jira/browse/HDDS-2437
> Project: Hadoop Distributed Data Store
>  Issue Type: Sub-task
>  Components: Ozone Manager
>Reporter: Anu Engineer
>Assignee: Matthew Sharp
>Priority: Major
>
> Make sure that only the owner of a key/adminstrator can empty-trash. The 
> delete ACL is not enough to empty-trash. This is becasue a shared bucket can 
> have deletes but the owner should be able to recover them. Once empty-trash 
> is executed even the owner will be able to recover the deleted keys



--
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] [Assigned] (HDDS-2436) Add security profile support for empty-trash command

2019-11-10 Thread Matthew Sharp (Jira)


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

Matthew Sharp reassigned HDDS-2436:
---

Assignee: Matthew Sharp

> Add security profile support for empty-trash command
> 
>
> Key: HDDS-2436
> URL: https://issues.apache.org/jira/browse/HDDS-2436
> Project: Hadoop Distributed Data Store
>  Issue Type: Sub-task
>  Components: Ozone Manager
>Reporter: Anu Engineer
>Assignee: Matthew Sharp
>Priority: Major
>
> Add support for a certain groups to have the ability to have empty-trash. It 
> might be the case where we want this command only to be run by admins.



--
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] [Assigned] (HDDS-2435) Add the ability to disable empty-trash command.

2019-11-10 Thread Matthew Sharp (Jira)


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

Matthew Sharp reassigned HDDS-2435:
---

Assignee: Matthew Sharp

> Add the ability to disable empty-trash command.
> ---
>
> Key: HDDS-2435
> URL: https://issues.apache.org/jira/browse/HDDS-2435
> Project: Hadoop Distributed Data Store
>  Issue Type: Sub-task
>Reporter: Anu Engineer
>Assignee: Matthew Sharp
>Priority: Major
>
> Add a configuration key to disable empty-trash command. We can discuss if 
> this should be a system-wide setting or per bucket. It is easier to do this 
> system-wide I guess.



--
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] [Created] (HDDS-2457) Add the ability to get the list of buckets that are deleted

2019-11-10 Thread Matthew Sharp (Jira)
Matthew Sharp created HDDS-2457:
---

 Summary: Add the ability to get the list of buckets that are 
deleted
 Key: HDDS-2457
 URL: https://issues.apache.org/jira/browse/HDDS-2457
 Project: Hadoop Distributed Data Store
  Issue Type: Sub-task
Reporter: Matthew Sharp


The initial focus is returning a list of deleted keys, but showing the deleted 
buckets should be explored further.



--
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] [Assigned] (HDDS-2422) Add robot tests for list-trash command.

2019-11-07 Thread Matthew Sharp (Jira)


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

Matthew Sharp reassigned HDDS-2422:
---

Assignee: Matthew Sharp

> Add robot tests for list-trash command.
> ---
>
> Key: HDDS-2422
> URL: https://issues.apache.org/jira/browse/HDDS-2422
> Project: Hadoop Distributed Data Store
>  Issue Type: Sub-task
>  Components: test
>Reporter: Anu Engineer
>Assignee: Matthew Sharp
>Priority: Major
>
> Add robot tests for list-trash command and add those tests to integration.sh 
> so these commands are run as part of CI.



--
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] [Assigned] (HDDS-2418) Add the list trash command server side handling.

2019-11-07 Thread Matthew Sharp (Jira)


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

Matthew Sharp reassigned HDDS-2418:
---

Assignee: Matthew Sharp

> Add the list trash command server side handling.
> 
>
> Key: HDDS-2418
> URL: https://issues.apache.org/jira/browse/HDDS-2418
> Project: Hadoop Distributed Data Store
>  Issue Type: Sub-task
>  Components: Ozone Manager
>Reporter: Anu Engineer
>Assignee: Matthew Sharp
>Priority: Major
>
> Add the standard code for any command handling in the server side.



--
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] [Assigned] (HDDS-2420) Add the Ozone shell support for list-trash command.

2019-11-07 Thread Matthew Sharp (Jira)


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

Matthew Sharp reassigned HDDS-2420:
---

Assignee: Matthew Sharp

> Add the Ozone shell support for list-trash command.
> ---
>
> Key: HDDS-2420
> URL: https://issues.apache.org/jira/browse/HDDS-2420
> Project: Hadoop Distributed Data Store
>  Issue Type: Sub-task
>  Components: Ozone CLI
>Reporter: Anu Engineer
>Assignee: Matthew Sharp
>Priority: Major
>
> Add support for list-trash command in Ozone CLI. Please see the attached 
> design doc.



--
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] [Assigned] (HDDS-2419) Add the core logic to process list trash command.

2019-11-07 Thread Matthew Sharp (Jira)


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

Matthew Sharp reassigned HDDS-2419:
---

Assignee: Matthew Sharp

> Add the core logic to process list trash command.
> -
>
> Key: HDDS-2419
> URL: https://issues.apache.org/jira/browse/HDDS-2419
> Project: Hadoop Distributed Data Store
>  Issue Type: Sub-task
>  Components: Ozone Manager
>Reporter: Anu Engineer
>Assignee: Matthew Sharp
>Priority: Major
>
> Add the core logic of reading from the deleted table, and return the entries 
> that match the user query.



--
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] [Assigned] (HDDS-2421) Add documentation for list trash command.

2019-11-07 Thread Matthew Sharp (Jira)


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

Matthew Sharp reassigned HDDS-2421:
---

Assignee: Matthew Sharp

> Add documentation for list trash command.
> -
>
> Key: HDDS-2421
> URL: https://issues.apache.org/jira/browse/HDDS-2421
> Project: Hadoop Distributed Data Store
>  Issue Type: Sub-task
>  Components: documentation
>Reporter: Anu Engineer
>Assignee: Matthew Sharp
>Priority: Major
>
> Add documentation about the list-trash command.



--
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] [Assigned] (HDDS-2417) Add the list trash command to the client side

2019-11-07 Thread Matthew Sharp (Jira)


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

Matthew Sharp reassigned HDDS-2417:
---

Assignee: Matthew Sharp

> Add the list trash command to the client side
> -
>
> Key: HDDS-2417
> URL: https://issues.apache.org/jira/browse/HDDS-2417
> Project: Hadoop Distributed Data Store
>  Issue Type: Sub-task
>  Components: Ozone Manager
>Reporter: Anu Engineer
>Assignee: Matthew Sharp
>Priority: Major
>
> Add the list-trash command to the protobuf files and to the client side 
> translator.



--
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] [Created] (HDDS-2416) Ozone Trash Feature

2019-11-07 Thread Matthew Sharp (Jira)
Matthew Sharp created HDDS-2416:
---

 Summary: Ozone Trash Feature
 Key: HDDS-2416
 URL: https://issues.apache.org/jira/browse/HDDS-2416
 Project: Hadoop Distributed Data Store
  Issue Type: New Feature
Reporter: Matthew Sharp
Assignee: Matthew Sharp
 Attachments: Ozone_Trash_Feature.docx

This Jira is a proposal to add a new feature to Ozone that provides a user with 
the ability to recover keys that may have been deleted accidentally.  This 
would be similar to the HDFS trash feature.

 

The attached document outlines the proposal and considerations for this feature.



--
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