[
https://issues.apache.org/jira/browse/HDDS-4307?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rakesh Radhakrishnan updated HDDS-4307:
---
Status: Patch Available (was: Open)
> Start Background Service for Trash Deletion in
GlenGeng closed pull request #1510:
URL: https://github.com/apache/hadoop-ozone/pull/1510
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
[
https://issues.apache.org/jira/browse/HDDS-4386?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Glen Geng updated HDDS-4386:
Description:
In Tencent production environment, after start Recon for a while, we got
warnings that all
[
https://issues.apache.org/jira/browse/HDDS-4386?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Glen Geng updated HDDS-4386:
Description:
In Tencent production environment, after start Recon for a while, we got
warnings that all
[
https://issues.apache.org/jira/browse/HDDS-4386?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Glen Geng updated HDDS-4386:
Description:
In Tencent production environment, after start Recon for a while, we got
warnings that all
[
https://issues.apache.org/jira/browse/HDDS-4386?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Glen Geng updated HDDS-4386:
Description:
In Tencent production environment, after start Recon for a while, we got
warnings that all
[
https://issues.apache.org/jira/browse/HDDS-4386?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Glen Geng updated HDDS-4386:
Description:
In Tencent production environment, after start Recon for a while, we got
warnings that all
[
https://issues.apache.org/jira/browse/HDDS-4339?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17219456#comment-17219456
]
Li Cheng commented on HDDS-4339:
I created https://issues.apache.org/jira/browse/HDDS-4361 to track s3g
[
https://issues.apache.org/jira/browse/HDDS-4386?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Glen Geng updated HDDS-4386:
Description:
In Tencent production environment, after start Recon for a while, we got
warnings that all
[
https://issues.apache.org/jira/browse/HDDS-4386?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Glen Geng updated HDDS-4386:
Description:
In Tencent production environment, after start Recon for a while, we got
warnings that all
[
https://issues.apache.org/jira/browse/HDDS-4386?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Glen Geng updated HDDS-4386:
Description:
In Tencent production environment, after start Recon for a while, we got
warnings that all
[
https://issues.apache.org/jira/browse/HDDS-4386?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Glen Geng updated HDDS-4386:
Description:
In Tencent production environment, after start Recon for a while, we got
warnings that all
[
https://issues.apache.org/jira/browse/HDDS-4386?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Glen Geng updated HDDS-4386:
Description:
In Tencent production environment, after start Recon for a while, we got
warnings that all
[
https://issues.apache.org/jira/browse/HDDS-4386?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Glen Geng updated HDDS-4386:
Affects Version/s: (was: 1.0.0)
1.1.0
> Each EndpointStateMachine uses its own
[
https://issues.apache.org/jira/browse/HDDS-4384?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sammi Chen resolved HDDS-4384.
--
Resolution: Duplicate
> Container sequence ID is not loaded after SCM restart
>
[
https://issues.apache.org/jira/browse/HDDS-4385?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sammi Chen updated HDDS-4385:
-
Summary: It would be nice if there is a search function using container ID
on Recon Missing Container
[
https://issues.apache.org/jira/browse/HDDS-4386?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Glen Geng updated HDDS-4386:
Description:
In Tencent production environment, after start Recon for a while, we got
warnings that all
[
https://issues.apache.org/jira/browse/HDDS-4386?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Glen Geng updated HDDS-4386:
Description:
In Tencent production environment, after start Recon for a while, we got
warnings that all
[
https://issues.apache.org/jira/browse/HDDS-4386?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Glen Geng updated HDDS-4386:
Description: (was: Configured goofys and s3g on different hosts and
Fiotest writes files on the goofys
[
https://issues.apache.org/jira/browse/HDDS-4386?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Glen Geng updated HDDS-4386:
Summary: Each EndpointStateMachine uses its own thread pool to talk with
SCM/Recon (was:
[
https://issues.apache.org/jira/browse/HDDS-4386?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Glen Geng updated HDDS-4386:
Labels: (was: pull-request-available)
> Each EndpointStateMachine uses its own thread pool to talk with
[
https://issues.apache.org/jira/browse/HDDS-4385?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sammi Chen updated HDDS-4385:
-
Description: In production cluster, there can be many missing containers to
investigate. It would be
[
https://issues.apache.org/jira/browse/HDDS-4386?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Glen Geng reassigned HDDS-4386:
---
Assignee: Glen Geng (was: Li Cheng)
> CLONE - Ozone S3 gateway throws NPE with goofys
>
[
https://issues.apache.org/jira/browse/HDDS-4386?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Glen Geng updated HDDS-4386:
Summary: EndpointStateMachine (was: CLONE - Ozone S3 gateway throws NPE
with goofys)
>
Glen Geng created HDDS-4386:
---
Summary: CLONE - Ozone S3 gateway throws NPE with goofys
Key: HDDS-4386
URL: https://issues.apache.org/jira/browse/HDDS-4386
Project: Hadoop Distributed Data Store
Sammi Chen created HDDS-4385:
Summary: It would be nice if there is a search function using
container ID
Key: HDDS-4385
URL: https://issues.apache.org/jira/browse/HDDS-4385
Project: Hadoop Distributed
xiaoyuyao commented on a change in pull request #1514:
URL: https://github.com/apache/hadoop-ozone/pull/1514#discussion_r510581749
##
File path:
hadoop-hdds/framework/src/main/java/org/apache/hadoop/hdds/scm/proxy/SCMContainerLocationFailoverProxyProvider.java
##
@@ -0,0
[
https://issues.apache.org/jira/browse/HDDS-4384?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sammi Chen updated HDDS-4384:
-
Labels: newbie (was: )
> Container sequence ID is not loaded after SCM restart
>
Sammi Chen created HDDS-4384:
Summary: Container sequence ID is not loaded after SCM restart
Key: HDDS-4384
URL: https://issues.apache.org/jira/browse/HDDS-4384
Project: Hadoop Distributed Data Store
[
https://issues.apache.org/jira/browse/HDDS-4384?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sammi Chen reassigned HDDS-4384:
Assignee: (was: Sammi Chen)
> Container sequence ID is not loaded after SCM restart
>
[
https://issues.apache.org/jira/browse/HDDS-4384?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sammi Chen updated HDDS-4384:
-
Description:
{noformat}
{
"state" : "CLOSED",
"replicationFactor" : "THREE",
"replicationType" :
captainzmc commented on pull request #1516:
URL: https://github.com/apache/hadoop-ozone/pull/1516#issuecomment-714884328
Thanks @xiaoyuyao 's review. I have submitted a new commit fix the above
issues.
This is an automated
captainzmc commented on a change in pull request #1516:
URL: https://github.com/apache/hadoop-ozone/pull/1516#discussion_r510568534
##
File path: hadoop-hdds/docs/content/feature/Quota.md
##
@@ -0,0 +1,67 @@
+---
+title: "Quota in Ozone"
+date: "2020-October-22"
+weight: 4
captainzmc commented on a change in pull request #1516:
URL: https://github.com/apache/hadoop-ozone/pull/1516#discussion_r510568737
##
File path: hadoop-hdds/docs/content/feature/Quota.md
##
@@ -0,0 +1,67 @@
+---
+title: "Quota in Ozone"
+date: "2020-October-22"
+weight: 4
captainzmc commented on a change in pull request #1516:
URL: https://github.com/apache/hadoop-ozone/pull/1516#discussion_r510568534
##
File path: hadoop-hdds/docs/content/feature/Quota.md
##
@@ -0,0 +1,67 @@
+---
+title: "Quota in Ozone"
+date: "2020-October-22"
+weight: 4
[
https://issues.apache.org/jira/browse/HDDS-4378?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
runzhiwang reopened HDDS-4378:
--
> Ozone shell support truncate API
>
>
> Key: HDDS-4378
>
[
https://issues.apache.org/jira/browse/HDDS-4378?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
runzhiwang resolved HDDS-4378.
--
Assignee: runzhiwang
Resolution: Fixed
> Ozone shell support truncate API
>
[
https://issues.apache.org/jira/browse/HDDS-4382?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
runzhiwang updated HDDS-4382:
-
Description: SCM starts a background thread to send
TruncateBlocksCommandProto to the datanode.
> SCM
[
https://issues.apache.org/jira/browse/HDDS-4379?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
runzhiwang updated HDDS-4379:
-
Description: Append mean ozone client can append some content to the tail
of some key. So if Client1
[
https://issues.apache.org/jira/browse/HDDS-4383?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
runzhiwang updated HDDS-4383:
-
Description: Datanode starts a background thread to process
. If it is FilePerBlock, we use
[
https://issues.apache.org/jira/browse/HDDS-4379?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
runzhiwang updated HDDS-4379:
-
Summary: OM marks truncated blocks (was: Mark truncated blocks in OM)
> OM marks truncated blocks
>
runzhiwang created HDDS-4383:
Summary: Datanode truncates blocks on the disk
Key: HDDS-4383
URL: https://issues.apache.org/jira/browse/HDDS-4383
Project: Hadoop Distributed Data Store
Issue
[
https://issues.apache.org/jira/browse/HDDS-4377?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
runzhiwang updated HDDS-4377:
-
Description: When Datanode receives TruncateBlocksCommand, in the RocksDB,
Datanode deletes the chunks
[
https://issues.apache.org/jira/browse/HDDS-4377?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
runzhiwang updated HDDS-4377:
-
Summary: Datanode changes the block length in rocksdb (was: Datanode
truncates blocks on the disk)
>
runzhiwang created HDDS-4382:
Summary: SCM send truncate block to datanode
Key: HDDS-4382
URL: https://issues.apache.org/jira/browse/HDDS-4382
Project: Hadoop Distributed Data Store
Issue Type:
[
https://issues.apache.org/jira/browse/HDDS-4376?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
runzhiwang updated HDDS-4376:
-
Description:
When scm receives TruncateScmKeyRequestProto, for the deleteBlocks, scm has
already
[
https://issues.apache.org/jira/browse/HDDS-4381?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
runzhiwang updated HDDS-4381:
-
Description: OM starts a background thread to select a certain number of
entries from truncateTable, and
runzhiwang created HDDS-4381:
Summary: OM send truncate key to SCM
Key: HDDS-4381
URL: https://issues.apache.org/jira/browse/HDDS-4381
Project: Hadoop Distributed Data Store
Issue Type: Sub-task
runzhiwang created HDDS-4380:
Summary: OM stores truncate key in truncateTable
Key: HDDS-4380
URL: https://issues.apache.org/jira/browse/HDDS-4380
Project: Hadoop Distributed Data Store
Issue
[
https://issues.apache.org/jira/browse/HDDS-4380?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
runzhiwang updated HDDS-4380:
-
Description: OM stores in truncateTable.
The TruncateKey in RepeatedTruncateOmKeyInfo represents one
[
https://issues.apache.org/jira/browse/HDDS-4375?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
runzhiwang updated HDDS-4375:
-
Description: When OM receives truncate(key, newLength),in the keyTable, OM
deletes the blocks which are
[
https://issues.apache.org/jira/browse/HDDS-4375?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
ASF GitHub Bot updated HDDS-4375:
-
Labels: pull-request-available (was: )
> OM changes the block length when receives truncate
runzhiwang opened a new pull request #1517:
URL: https://github.com/apache/hadoop-ozone/pull/1517
## What changes were proposed in this pull request?
1. When OM receives truncate(key, newLength),in the keyTable, OM deletes the
blocks which are fully truncated, and updates the block
[
https://issues.apache.org/jira/browse/HDDS-4375?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
runzhiwang updated HDDS-4375:
-
Summary: OM changes the block length when receives truncate request (was:
OM changes the block length
[
https://issues.apache.org/jira/browse/HDDS-4375?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
runzhiwang updated HDDS-4375:
-
Summary: OM changes the block length when receive truncate request (was:
Client asks OM to change the
runzhiwang created HDDS-4379:
Summary: Mark truncated blocks in OM
Key: HDDS-4379
URL: https://issues.apache.org/jira/browse/HDDS-4379
Project: Hadoop Distributed Data Store
Issue Type: Sub-task
runzhiwang created HDDS-4378:
Summary: Ozone shell support truncate API
Key: HDDS-4378
URL: https://issues.apache.org/jira/browse/HDDS-4378
Project: Hadoop Distributed Data Store
Issue Type:
runzhiwang created HDDS-4376:
Summary: SCM create transaction for truncated blocks
Key: HDDS-4376
URL: https://issues.apache.org/jira/browse/HDDS-4376
Project: Hadoop Distributed Data Store
runzhiwang created HDDS-4377:
Summary: Datanode truncates blocks on the disk
Key: HDDS-4377
URL: https://issues.apache.org/jira/browse/HDDS-4377
Project: Hadoop Distributed Data Store
Issue
[
https://issues.apache.org/jira/browse/HDDS-4375?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
runzhiwang updated HDDS-4375:
-
Parent: HDDS-4239
Issue Type: Sub-task (was: New Feature)
> Client asks OM to change the block
runzhiwang created HDDS-4375:
Summary: Client asks OM to change the block length when truncate
Key: HDDS-4375
URL: https://issues.apache.org/jira/browse/HDDS-4375
Project: Hadoop Distributed Data Store
[
https://issues.apache.org/jira/browse/HDDS-4239?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
runzhiwang updated HDDS-4239:
-
Parent: (was: HDDS-3714)
Issue Type: New Feature (was: Sub-task)
> Ozone support truncate
prashantpogde commented on a change in pull request #1486:
URL: https://github.com/apache/hadoop-ozone/pull/1486#discussion_r510505108
##
File path:
hadoop-hdds/server-scm/src/main/java/org/apache/hadoop/hdds/scm/node/SCMNodeManager.java
##
@@ -400,6 +405,66 @@ public void
xiaoyuyao commented on a change in pull request #1514:
URL: https://github.com/apache/hadoop-ozone/pull/1514#discussion_r510497229
##
File path:
hadoop-hdds/framework/src/main/java/org/apache/hadoop/hdds/scm/proxy/SCMContainerLocationFailoverProxyProvider.java
##
@@ -0,0
xiaoyuyao commented on a change in pull request #1301:
URL: https://github.com/apache/hadoop-ozone/pull/1301#discussion_r510486990
##
File path:
hadoop-ozone/ozone-manager/src/main/java/org/apache/hadoop/ozone/om/request/volume/acl/OMVolumeAddAclRequest.java
##
@@ -48,6
xiaoyuyao commented on a change in pull request #1301:
URL: https://github.com/apache/hadoop-ozone/pull/1301#discussion_r510486544
##
File path:
hadoop-ozone/ozone-manager/src/main/java/org/apache/hadoop/ozone/om/request/key/acl/OMKeyRemoveAclRequest.java
##
@@ -43,6 +45,19
xiaoyuyao commented on a change in pull request #1301:
URL: https://github.com/apache/hadoop-ozone/pull/1301#discussion_r510486787
##
File path:
hadoop-ozone/ozone-manager/src/main/java/org/apache/hadoop/ozone/om/request/key/acl/OMKeySetAclRequest.java
##
@@ -44,6 +46,19 @@
xiaoyuyao commented on a change in pull request #1301:
URL: https://github.com/apache/hadoop-ozone/pull/1301#discussion_r510486443
##
File path:
hadoop-ozone/ozone-manager/src/main/java/org/apache/hadoop/ozone/om/request/key/acl/OMKeyAddAclRequest.java
##
@@ -43,6 +45,19 @@
Ethan Rose created HDDS-4374:
Summary: Share RocskDB cache in new datanode DB utilities
Key: HDDS-4374
URL: https://issues.apache.org/jira/browse/HDDS-4374
Project: Hadoop Distributed Data Store
[
https://issues.apache.org/jira/browse/HDDS-4337?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ethan Rose reassigned HDDS-4337:
Assignee: Ethan Rose
> Implement RocksDB options cache for new datanode DB utilities
>
xiaoyuyao commented on a change in pull request #1395:
URL: https://github.com/apache/hadoop-ozone/pull/1395#discussion_r510410249
##
File path:
hadoop-ozone/ozone-manager/src/main/java/org/apache/hadoop/ozone/om/OzoneManager.java
##
@@ -1642,25 +1644,42 @@ private boolean
smengcl commented on a change in pull request #1395:
URL: https://github.com/apache/hadoop-ozone/pull/1395#discussion_r510376263
##
File path:
hadoop-ozone/ozone-manager/src/main/java/org/apache/hadoop/ozone/om/OzoneManager.java
##
@@ -1642,25 +1644,42 @@ private boolean
smengcl commented on a change in pull request #1395:
URL: https://github.com/apache/hadoop-ozone/pull/1395#discussion_r510375521
##
File path:
hadoop-ozone/ozone-manager/src/main/java/org/apache/hadoop/ozone/om/OzoneManager.java
##
@@ -1642,25 +1644,42 @@ private boolean
xiaoyuyao commented on a change in pull request #1516:
URL: https://github.com/apache/hadoop-ozone/pull/1516#discussion_r510364763
##
File path: hadoop-hdds/docs/content/feature/Quota.md
##
@@ -0,0 +1,67 @@
+---
+title: "Quota in Ozone"
+date: "2020-October-22"
+weight: 4
xiaoyuyao commented on a change in pull request #1516:
URL: https://github.com/apache/hadoop-ozone/pull/1516#discussion_r510363980
##
File path: hadoop-hdds/docs/content/feature/Quota.md
##
@@ -0,0 +1,67 @@
+---
+title: "Quota in Ozone"
+date: "2020-October-22"
+weight: 4
xiaoyuyao commented on a change in pull request #1516:
URL: https://github.com/apache/hadoop-ozone/pull/1516#discussion_r510361614
##
File path: hadoop-hdds/docs/content/feature/Quota.md
##
@@ -0,0 +1,67 @@
+---
+title: "Quota in Ozone"
+date: "2020-October-22"
+weight: 4
xiaoyuyao commented on a change in pull request #1516:
URL: https://github.com/apache/hadoop-ozone/pull/1516#discussion_r510360994
##
File path: hadoop-hdds/docs/content/feature/Quota.md
##
@@ -0,0 +1,67 @@
+---
+title: "Quota in Ozone"
+date: "2020-October-22"
+weight: 4
xiaoyuyao commented on a change in pull request #1395:
URL: https://github.com/apache/hadoop-ozone/pull/1395#discussion_r510293188
##
File path:
hadoop-ozone/ozone-manager/src/main/java/org/apache/hadoop/ozone/om/OzoneManager.java
##
@@ -1642,25 +1644,42 @@ private boolean
linyiqun commented on a change in pull request #1480:
URL: https://github.com/apache/hadoop-ozone/pull/1480#discussion_r510272665
##
File path:
hadoop-ozone/ozone-manager/src/main/java/org/apache/hadoop/ozone/om/OzoneManager.java
##
@@ -394,6 +403,8 @@ private
linyiqun commented on a change in pull request #1480:
URL: https://github.com/apache/hadoop-ozone/pull/1480#discussion_r510272665
##
File path:
hadoop-ozone/ozone-manager/src/main/java/org/apache/hadoop/ozone/om/OzoneManager.java
##
@@ -394,6 +403,8 @@ private
linyiqun commented on a change in pull request #1480:
URL: https://github.com/apache/hadoop-ozone/pull/1480#discussion_r510268648
##
File path:
hadoop-ozone/common/src/main/java/org/apache/hadoop/ozone/OmUtils.java
##
@@ -524,6 +535,48 @@ public static OmKeyInfo
avijayanhwx commented on a change in pull request #1486:
URL: https://github.com/apache/hadoop-ozone/pull/1486#discussion_r510187543
##
File path:
hadoop-hdds/server-scm/src/main/java/org/apache/hadoop/hdds/scm/node/SCMNodeManager.java
##
@@ -400,6 +405,66 @@ public void
[
https://issues.apache.org/jira/browse/HDDS-3731?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
ASF GitHub Bot updated HDDS-3731:
-
Labels: pull-request-available (was: )
> add storage space quota doc
>
captainzmc opened a new pull request #1516:
URL: https://github.com/apache/hadoop-ozone/pull/1516
## What changes were proposed in this pull request?
The space Quota feature is now nearly complete, so add a description of how
to use it
## What is the link to the Apache JIRA
[
https://issues.apache.org/jira/browse/HDDS-3731?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
mingchao zhao updated HDDS-3731:
Summary: add storage space quota doc (was: Relative Unit Test)
> add storage space quota doc
>
codecov-io commented on pull request #1514:
URL: https://github.com/apache/hadoop-ozone/pull/1514#issuecomment-714483581
#
[Codecov](https://codecov.io/gh/apache/hadoop-ozone/pull/1514?src=pr=h1)
Report
> Merging
[#1514](https://codecov.io/gh/apache/hadoop-ozone/pull/1514?src=pr=desc)
[
https://issues.apache.org/jira/browse/HDDS-4373?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
ASF GitHub Bot updated HDDS-4373:
-
Labels: pull-request-available (was: )
> Add append design documentation
>
captainzmc opened a new pull request #1515:
URL: https://github.com/apache/hadoop-ozone/pull/1515
## What changes were proposed in this pull request?
This is a design doc, which is moved from google doc to make it easier to
track the progress.
## What is the link to the
smengcl commented on a change in pull request #1395:
URL: https://github.com/apache/hadoop-ozone/pull/1395#discussion_r510108891
##
File path:
hadoop-ozone/ozone-manager/src/main/java/org/apache/hadoop/ozone/om/OzoneManager.java
##
@@ -1642,25 +1644,42 @@ private boolean
timmylicheng commented on a change in pull request #1498:
URL: https://github.com/apache/hadoop-ozone/pull/1498#discussion_r510107592
##
File path:
hadoop-ozone/s3gateway/src/main/java/org/apache/hadoop/ozone/s3/OzoneClientProducer.java
##
@@ -116,6 +116,13 @@ private
timmylicheng closed pull request #1514:
URL: https://github.com/apache/hadoop-ozone/pull/1514
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL
mingchao zhao created HDDS-4373:
---
Summary: Add append design documentation
Key: HDDS-4373
URL: https://issues.apache.org/jira/browse/HDDS-4373
Project: Hadoop Distributed Data Store
Issue
[
https://issues.apache.org/jira/browse/HDDS-4366?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Lokesh Jain updated HDDS-4366:
--
Status: Patch Available (was: Open)
> SCM deletion service should delete configured number of blocks
[
https://issues.apache.org/jira/browse/HDDS-4371?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Lokesh Jain updated HDDS-4371:
--
Component/s: Ozone Datanode
> Datanode should have deletion service thread per volume
>
[
https://issues.apache.org/jira/browse/HDDS-4369?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Lokesh Jain updated HDDS-4369:
--
Component/s: Ozone Datanode
> Datanode should store the delete transaction as is in rocksDB
>
[
https://issues.apache.org/jira/browse/HDDS-4370?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Lokesh Jain updated HDDS-4370:
--
Component/s: Ozone Datanode
> Datanode deletion service can avoid storing deleted blocks
>
Lokesh Jain created HDDS-4372:
-
Summary: Datanode delete operations should not impact rocksDB cache
Key: HDDS-4372
URL: https://issues.apache.org/jira/browse/HDDS-4372
Project: Hadoop Distributed Data
Lokesh Jain created HDDS-4371:
-
Summary: Datanode should have deletion service thread per volume
Key: HDDS-4371
URL: https://issues.apache.org/jira/browse/HDDS-4371
Project: Hadoop Distributed Data Store
Lokesh Jain created HDDS-4370:
-
Summary: Datanode deletion service can avoid storing deleted blocks
Key: HDDS-4370
URL: https://issues.apache.org/jira/browse/HDDS-4370
Project: Hadoop Distributed Data
Lokesh Jain created HDDS-4369:
-
Summary: Datanode should store the delete transaction as is in
rocksDB
Key: HDDS-4369
URL: https://issues.apache.org/jira/browse/HDDS-4369
Project: Hadoop Distributed Data
1 - 100 of 115 matches
Mail list logo
