[
https://issues.apache.org/jira/browse/HDDS-3168?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nanda kumar resolved HDDS-3168.
---
Fix Version/s: 0.6.0
Resolution: Fixed
Thanks [~yjxxtd] for the contribution. Merged the
xiaoyuyao commented on issue #724:
URL: https://github.com/apache/hadoop-ozone/pull/724#issuecomment-617552862
These two tests are not very reliable they both passed in my local setup but
failed on CI.
org.apache.hadoop.ozone.client.rpc.Test2WayCommitInRatis
captainzmc commented on issue #716:
URL: https://github.com/apache/hadoop-ozone/pull/716#issuecomment-617522501
hi @bshashikant Thanks for your review, now I had delete useless metrics in
new ut testFlushChunkDelay.
This
captainzmc removed a comment on issue #716:
URL: https://github.com/apache/hadoop-ozone/pull/716#issuecomment-615879601
Hi @lokeshj1703 I had fixed review issue and added ut. Could you please
review this pr again?
This is
bharatviswa504 commented on a change in pull request #691:
URL: https://github.com/apache/hadoop-ozone/pull/691#discussion_r412628975
##
File path:
hadoop-ozone/ozone-manager/src/main/java/org/apache/hadoop/ozone/om/ratis/OzoneManagerDoubleBuffer.java
##
@@ -147,7 +160,11 @@
bharatviswa504 edited a comment on issue #691:
URL: https://github.com/apache/hadoop-ozone/pull/691#issuecomment-617514763
Overall LGTM. One minor comment and a general question.
I have one question in general, will this add some overhead and is there a
way to disable it?
The reason
bharatviswa504 commented on issue #691:
URL: https://github.com/apache/hadoop-ozone/pull/691#issuecomment-617514763
I have one question in general, will this add some overhead and is there a
way to disable it?
The reason is because, in non-HA, we wait for flush to DB future to be
bharatviswa504 commented on a change in pull request #691:
URL: https://github.com/apache/hadoop-ozone/pull/691#discussion_r412625536
##
File path:
hadoop-ozone/ozone-manager/src/main/java/org/apache/hadoop/ozone/om/ratis/OzoneManagerDoubleBuffer.java
##
@@ -135,10 +138,20 @@
umamaheswararao commented on issue #853:
URL: https://github.com/apache/hadoop-ozone/pull/853#issuecomment-617512700
Thank you Bharat for reviews!!!
This is an automated message from the Apache Git Service.
To respond to the
[
https://issues.apache.org/jira/browse/HDDS-3001?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17089217#comment-17089217
]
Prashant Pogde commented on HDDS-3001:
--
I created a https://issues.apache.org/jira/browse/HDDS-3462
bharatviswa504 commented on issue #853:
URL: https://github.com/apache/hadoop-ozone/pull/853#issuecomment-617506820
Thank You @umamaheswararao for the contribution.
This is an automated message from the Apache Git Service.
bharatviswa504 commented on issue #854:
URL: https://github.com/apache/hadoop-ozone/pull/854#issuecomment-617506943
Thank You @vivekratnavel for the contribution.
This is an automated message from the Apache Git Service.
To
prashantpogde commented on issue #828:
URL: https://github.com/apache/hadoop-ozone/pull/828#issuecomment-617506817
@elek @mukul1987 I will be ok either way with a separate branch or
directly on the master. Mostly changes would be isolated in NFS directly with
few hooks occasionally
[
https://issues.apache.org/jira/browse/HDDS-3467?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bharat Viswanadham resolved HDDS-3467.
--
Resolution: Fixed
> OM Client RPC failover retries happening more than configured.
>
[
https://issues.apache.org/jira/browse/HDDS-3393?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bharat Viswanadham updated HDDS-3393:
-
Fix Version/s: 0.6.0
Resolution: Fixed
Status: Resolved (was: Patch
[
https://issues.apache.org/jira/browse/HDDS-2809?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Xiaoyu Yao resolved HDDS-2809.
--
Fix Version/s: 0.6.0
Resolution: Fixed
Thanks [~iamabug] for the contribution. I've merged the
[
https://issues.apache.org/jira/browse/HDDS-3388?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Xiaoyu Yao updated HDDS-3388:
-
Fix Version/s: 0.6.0
> Add bucket encryption key info to bucket create audit log
>
[
https://issues.apache.org/jira/browse/HDDS-3388?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17089145#comment-17089145
]
Xiaoyu Yao commented on HDDS-3388:
--
Thanks [~vivekratnavel] for the review. I've merged the PR to master.
[
https://issues.apache.org/jira/browse/HDDS-3476?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bharat Viswanadham reassigned HDDS-3476:
Assignee: Bharat Viswanadham
> Use persisted transaction info during OM startup in
[
https://issues.apache.org/jira/browse/HDDS-3475?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bharat Viswanadham updated HDDS-3475:
-
Status: Patch Available (was: Open)
> Use transactionInfo table to persist transaction
[
https://issues.apache.org/jira/browse/HDDS-3354?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bharat Viswanadham updated HDDS-3354:
-
Issue Type: Improvement (was: Bug)
> OM HA replay optimization
>
[
https://issues.apache.org/jira/browse/HDDS-3476?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bharat Viswanadham updated HDDS-3476:
-
Parent: HDDS-3354
Issue Type: Sub-task (was: Bug)
> Use persisted transaction
[
https://issues.apache.org/jira/browse/HDDS-3476?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bharat Viswanadham updated HDDS-3476:
-
Description: HDDS-3475 persisted transaction info into DB. This Jira is to
use
Bharat Viswanadham created HDDS-3476:
Summary: Use persisted transaction info during OM startup in OM
StateMachine
Key: HDDS-3476
URL: https://issues.apache.org/jira/browse/HDDS-3476
Project:
[
https://issues.apache.org/jira/browse/HDDS-3459?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17088754#comment-17088754
]
runzhiwang edited comment on HDDS-3459 at 4/21/20, 11:28 PM:
-
[~nanda] Hi,
bharatviswa504 opened a new pull request #856:
URL: https://github.com/apache/hadoop-ozone/pull/856
## What changes were proposed in this pull request?
Commit the transaction info as part of double buffer flush.
This requires #855. Posted this for CI run.
## What is the
vivekratnavel commented on a change in pull request #854:
URL: https://github.com/apache/hadoop-ozone/pull/854#discussion_r412542919
##
File path:
hadoop-ozone/recon/src/main/resources/webapps/recon/ozone-recon-web/api/db.json
##
@@ -378,11 +378,11 @@
}
],
bharatviswa504 commented on a change in pull request #854:
URL: https://github.com/apache/hadoop-ozone/pull/854#discussion_r412537904
##
File path:
hadoop-ozone/recon/src/main/java/org/apache/hadoop/ozone/recon/recovery/ReconOmMetadataManagerImpl.java
##
@@ -120,4 +122,11 @@
smengcl commented on a change in pull request #797:
URL: https://github.com/apache/hadoop-ozone/pull/797#discussion_r412504182
##
File path: hadoop-hdds/docs/content/recipe/SparkOzoneFSK8S.zh.md
##
@@ -0,0 +1,185 @@
+---
+title: Kubernetes 上运行 Spark 和 OzoneFS
+linktitle: Spark
smengcl commented on a change in pull request #796:
URL: https://github.com/apache/hadoop-ozone/pull/796#discussion_r412502150
##
File path: hadoop-hdds/docs/content/recipe/Prometheus.zh.md
##
@@ -0,0 +1,93 @@
+---
+title: 使用 Prometheus 监控
+summary: 使用 Prometheus 监控 Ozone
[
https://issues.apache.org/jira/browse/HDDS-3393?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vivek Ratnavel Subramanian updated HDDS-3393:
-
Status: Patch Available (was: Open)
> Recon throws NPE in clusterState
[
https://issues.apache.org/jira/browse/HDDS-3056?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Siyao Meng updated HDDS-3056:
-
Resolution: Fixed
Status: Resolved (was: Patch Available)
> Allow users to list volumes they
smengcl commented on issue #696:
URL: https://github.com/apache/hadoop-ozone/pull/696#issuecomment-617374333
Got a green run after the rebase. Will commit shortly.
Thanks @xiaoyuyao and @dineshchitlangia for the review.
bharatviswa504 commented on a change in pull request #843:
URL: https://github.com/apache/hadoop-ozone/pull/843#discussion_r412437219
##
File path:
hadoop-ozone/s3gateway/src/main/java/org/apache/hadoop/ozone/s3/io/S3WrapperInputStream.java
##
@@ -76,4 +79,87 @@ public long
Bharat Viswanadham created HDDS-3475:
Summary: Use transactionInfo table to persist transaction
information
Key: HDDS-3475
URL: https://issues.apache.org/jira/browse/HDDS-3475
Project: Hadoop
[
https://issues.apache.org/jira/browse/HDDS-3474?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bharat Viswanadham updated HDDS-3474:
-
Status: Patch Available (was: In Progress)
> Create transactionInfo Table in
[
https://issues.apache.org/jira/browse/HDDS-3474?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
ASF GitHub Bot updated HDDS-3474:
-
Labels: pull-request-available (was: )
> Create transactionInfo Table in OmMetadataManager
>
bharatviswa504 opened a new pull request #855:
URL: https://github.com/apache/hadoop-ozone/pull/855
## What changes were proposed in this pull request?
1. introduce a new transaction info table which stores transactionInfo.
Key = TRANSACTIONINFO
value =
vivekratnavel commented on a change in pull request #854:
URL: https://github.com/apache/hadoop-ozone/pull/854#discussion_r412412225
##
File path:
hadoop-ozone/recon/src/main/java/org/apache/hadoop/ozone/recon/api/ClusterStateEndpoint.java
##
@@ -81,20 +82,26 @@ public
bharatviswa504 commented on issue #825:
URL: https://github.com/apache/hadoop-ozone/pull/825#issuecomment-617344891
> Thanks to start this discussion @maobaolong. I agree with @bharatviswa504
, I like when the de-serialization and the serialization logic is close to the
data object itself
nandakumar131 commented on issue #700:
URL: https://github.com/apache/hadoop-ozone/pull/700#issuecomment-617344219
Thanks @elek for updating the patch.
> Do you prefer rename or removal? I am not sure if it's required or not.
I'm leaning more towards renaming and using it, as
bharatviswa504 commented on a change in pull request #854:
URL: https://github.com/apache/hadoop-ozone/pull/854#discussion_r412395406
##
File path:
hadoop-ozone/recon/src/main/java/org/apache/hadoop/ozone/recon/api/ClusterStateEndpoint.java
##
@@ -81,20 +82,26 @@ public
bharatviswa504 commented on a change in pull request #854:
URL: https://github.com/apache/hadoop-ozone/pull/854#discussion_r412395406
##
File path:
hadoop-ozone/recon/src/main/java/org/apache/hadoop/ozone/recon/api/ClusterStateEndpoint.java
##
@@ -81,20 +82,26 @@ public
[
https://issues.apache.org/jira/browse/HDDS-3474?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Bharat Viswanadham reassigned HDDS-3474:
Assignee: Bharat Viswanadham
> Create transactionInfo Table in OmMetadataManager
>
Bharat Viswanadham created HDDS-3474:
Summary: Create transactionInfo Table in OmMetadataManager
Key: HDDS-3474
URL: https://issues.apache.org/jira/browse/HDDS-3474
Project: Hadoop Distributed
[
https://issues.apache.org/jira/browse/HDDS-3393?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
ASF GitHub Bot updated HDDS-3393:
-
Labels: pull-request-available (was: )
> Recon throws NPE in clusterState endpoint
>
arp7 commented on issue #578:
URL: https://github.com/apache/hadoop-ozone/pull/578#issuecomment-617318392
The change looks good to me. In multi-RAFT setup will we end up creating
10*numDisks*numPipelines threads, or will the total number of threads be the
same as single RAFT?
[
https://issues.apache.org/jira/browse/HDDS-3290?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17088902#comment-17088902
]
Arpit Agarwal commented on HDDS-3290:
-
Hi [~elek] what's the correct pull request for this Jira? The
[
https://issues.apache.org/jira/browse/HDDS-3473?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nilotpal Nandi updated HDDS-3473:
-
Description:
sample chunkinfo output :
{
"container Id :12blockId :104035271344128004": {
[
https://issues.apache.org/jira/browse/HDDS-3473?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mukul Kumar Singh reassigned HDDS-3473:
---
Assignee: Sadanand Shenoy
> ozone chunkinfo CLI should display block file path info
Nilotpal Nandi created HDDS-3473:
Summary: ozone chunkinfo CLI should display block file path info
Key: HDDS-3473
URL: https://issues.apache.org/jira/browse/HDDS-3473
Project: Hadoop Distributed Data
aryangupta1998 commented on a change in pull request #782:
URL: https://github.com/apache/hadoop-ozone/pull/782#discussion_r412310599
##
File path: hadoop-ozone/native-client/libo3fs-examples/libo3fs_read.c
##
@@ -0,0 +1,65 @@
+/**
+ * Licensed to the Apache Software
aryangupta1998 commented on a change in pull request #782:
URL: https://github.com/apache/hadoop-ozone/pull/782#discussion_r412310797
##
File path: hadoop-ozone/native-client/libo3fs/o3fs.h
##
@@ -0,0 +1,44 @@
+/**
+ * Licensed to the Apache Software Foundation (ASF) under one
[
https://issues.apache.org/jira/browse/HDDS-3380?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Uma Maheswara Rao G resolved HDDS-3380.
---
Resolution: Fixed
> MiniOzoneHAClusterImpl#initOMRatisConf will reset the configs and
umamaheswararao opened a new pull request #853:
URL: https://github.com/apache/hadoop-ozone/pull/853
## What changes were proposed in this pull request?
fixed the condition for failover retries.
Added join after OM stop.
assertions to failover counts
## What is the link
[
https://issues.apache.org/jira/browse/HDDS-3451?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mukul Kumar Singh updated HDDS-3451:
Fix Version/s: 0.6.0
Resolution: Fixed
Status: Resolved (was: Patch
[
https://issues.apache.org/jira/browse/HDDS-3451?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17088833#comment-17088833
]
Mukul Kumar Singh commented on HDDS-3451:
-
Thanks for the contribution [~nanda] and [~xyao] for
[
https://issues.apache.org/jira/browse/HDDS-3459?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17088754#comment-17088754
]
runzhiwang edited comment on HDDS-3459 at 4/21/20, 4:13 PM:
[~nanda] Hi,
[
https://issues.apache.org/jira/browse/HDDS-3459?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17088754#comment-17088754
]
runzhiwang edited comment on HDDS-3459 at 4/21/20, 4:06 PM:
[~nanda] Hi,
[
https://issues.apache.org/jira/browse/HDDS-3459?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17088754#comment-17088754
]
runzhiwang edited comment on HDDS-3459 at 4/21/20, 4:06 PM:
[~nanda] Hi,
[
https://issues.apache.org/jira/browse/HDDS-3459?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17088754#comment-17088754
]
runzhiwang edited comment on HDDS-3459 at 4/21/20, 4:05 PM:
[~nanda] Hi,
[
https://issues.apache.org/jira/browse/HDDS-3456?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Attila Doroszlai updated HDDS-3456:
---
Labels: (was: pull-request-available)
> Fix Acceptance test failures due to disk out of
[
https://issues.apache.org/jira/browse/HDDS-3472?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
ASF GitHub Bot updated HDDS-3472:
-
Labels: pull-request-available (was: )
> Remove redundant hdds.version from
mukul1987 opened a new pull request #852:
URL: https://github.com/apache/hadoop-ozone/pull/852
## What changes were proposed in this pull request?
Remove redundant hdds.version from hadoop-hdds/common/pom.xml
## What is the link to the Apache JIRA
Mukul Kumar Singh created HDDS-3472:
---
Summary: Remove redundant hdds.version from
hadoop-hdds/common/pom.xml
Key: HDDS-3472
URL: https://issues.apache.org/jira/browse/HDDS-3472
Project: Hadoop
mukul1987 commented on a change in pull request #782:
URL: https://github.com/apache/hadoop-ozone/pull/782#discussion_r412272959
##
File path: hadoop-ozone/native-client/libo3fs-examples/libo3fs_read.c
##
@@ -0,0 +1,65 @@
+/**
+ * Licensed to the Apache Software Foundation
[
https://issues.apache.org/jira/browse/HDDS-3139?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stephen O'Donnell resolved HDDS-3139.
-
Target Version/s: 0.6.0
Resolution: Fixed
> Pipeline placement should select
[
https://issues.apache.org/jira/browse/HDDS-3459?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17088754#comment-17088754
]
runzhiwang edited comment on HDDS-3459 at 4/21/20, 3:02 PM:
[~nanda] Hi,
elek commented on issue #13:
URL:
https://github.com/apache/hadoop-docker-ozone/pull/13#issuecomment-617231288
Merged and tagged. Thanks the review @adoroszlai
This is an automated message from the Apache Git Service.
To
[
https://issues.apache.org/jira/browse/HDDS-3459?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17088754#comment-17088754
]
runzhiwang commented on HDDS-3459:
--
[~nanda] Hi, thanks for your explanation. My basic opinion is:
1.
[
https://issues.apache.org/jira/browse/HDDS-3459?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17088739#comment-17088739
]
Nanda kumar commented on HDDS-3459:
---
Even though the issue seems different from HDDS-3451, both are
[
https://issues.apache.org/jira/browse/HDDS-3459?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
runzhiwang updated HDDS-3459:
-
Description:
*What's the problem ?*
Datanode use a single [command-processor-thread
[
https://issues.apache.org/jira/browse/HDDS-3459?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17088721#comment-17088721
]
runzhiwang edited comment on HDDS-3459 at 4/21/20, 2:05 PM:
[~msingh] I think
[
https://issues.apache.org/jira/browse/HDDS-3471?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Shashikant Banerjee resolved HDDS-3471.
---
Resolution: Fixed
Thanks [~msingh] for the review. I have committed this.
> Update
[
https://issues.apache.org/jira/browse/HDDS-3459?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17088721#comment-17088721
]
runzhiwang commented on HDDS-3459:
--
[~msingh] I think it's not similar to HDDS-3451.
> Datanode use a
mukul1987 commented on issue #845:
URL: https://github.com/apache/hadoop-ozone/pull/845#issuecomment-617200484
Thanks for updating the patch @nandakumar131 . +1 the patch looks good to me.
This is an automated message from
[
https://issues.apache.org/jira/browse/HDDS-3459?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
runzhiwang updated HDDS-3459:
-
Description:
*What's the problem ?*
Datanode use a single [command-processor-thread
[
https://issues.apache.org/jira/browse/HDDS-3459?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
runzhiwang updated HDDS-3459:
-
Attachment: screenshot-7.png
> Datanode use a single thread to process the command of scm
>
[
https://issues.apache.org/jira/browse/HDDS-3459?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
runzhiwang updated HDDS-3459:
-
Attachment: screenshot-6.png
> Datanode use a single thread to process the command of scm
>
[
https://issues.apache.org/jira/browse/HDDS-3459?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
runzhiwang updated HDDS-3459:
-
Attachment: screenshot-4.png
> Datanode use a single thread to process the command of scm
>
[
https://issues.apache.org/jira/browse/HDDS-3459?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
runzhiwang updated HDDS-3459:
-
Attachment: screenshot-5.png
> Datanode use a single thread to process the command of scm
>
[
https://issues.apache.org/jira/browse/HDDS-3459?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
runzhiwang updated HDDS-3459:
-
Attachment: screenshot-3.png
> Datanode use a single thread to process the command of scm
>
[
https://issues.apache.org/jira/browse/HDDS-3459?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
runzhiwang updated HDDS-3459:
-
Attachment: screenshot-2.png
> Datanode use a single thread to process the command of scm
>
[
https://issues.apache.org/jira/browse/HDDS-3459?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
runzhiwang updated HDDS-3459:
-
Attachment: screenshot-1.png
> Datanode use a single thread to process the command of scm
>
[
https://issues.apache.org/jira/browse/HDDS-3459?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
runzhiwang updated HDDS-3459:
-
Description:
*What's the problem ?*
Datanode use a single [command-processor-thread
[
https://issues.apache.org/jira/browse/HDDS-3459?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
runzhiwang updated HDDS-3459:
-
Attachment: (was: screenshot-9.png)
> Datanode use a single thread to process the command of scm
>
[
https://issues.apache.org/jira/browse/HDDS-3459?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
runzhiwang updated HDDS-3459:
-
Attachment: (was: screenshot-14.png)
> Datanode use a single thread to process the command of scm
>
[
https://issues.apache.org/jira/browse/HDDS-3459?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
runzhiwang updated HDDS-3459:
-
Attachment: (was: screenshot-12.png)
> Datanode use a single thread to process the command of scm
>
[
https://issues.apache.org/jira/browse/HDDS-3459?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
runzhiwang updated HDDS-3459:
-
Attachment: (was: screenshot-6.png)
> Datanode use a single thread to process the command of scm
>
[
https://issues.apache.org/jira/browse/HDDS-3459?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
runzhiwang updated HDDS-3459:
-
Attachment: (was: screenshot-4.png)
> Datanode use a single thread to process the command of scm
>
[
https://issues.apache.org/jira/browse/HDDS-3459?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
runzhiwang updated HDDS-3459:
-
Attachment: (was: screenshot-3.png)
> Datanode use a single thread to process the command of scm
>
[
https://issues.apache.org/jira/browse/HDDS-3459?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
runzhiwang updated HDDS-3459:
-
Attachment: (was: screenshot-2.png)
> Datanode use a single thread to process the command of scm
>
[
https://issues.apache.org/jira/browse/HDDS-3459?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
runzhiwang updated HDDS-3459:
-
Attachment: (was: screenshot-11.png)
> Datanode use a single thread to process the command of scm
>
[
https://issues.apache.org/jira/browse/HDDS-3459?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
runzhiwang updated HDDS-3459:
-
Attachment: (was: screenshot-7.png)
> Datanode use a single thread to process the command of scm
>
[
https://issues.apache.org/jira/browse/HDDS-3459?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
runzhiwang updated HDDS-3459:
-
Attachment: (was: screenshot-5.png)
> Datanode use a single thread to process the command of scm
>
[
https://issues.apache.org/jira/browse/HDDS-3459?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
runzhiwang updated HDDS-3459:
-
Attachment: (was: screenshot-8.png)
> Datanode use a single thread to process the command of scm
>
[
https://issues.apache.org/jira/browse/HDDS-3459?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
runzhiwang updated HDDS-3459:
-
Attachment: (was: screenshot-10.png)
> Datanode use a single thread to process the command of scm
>
[
https://issues.apache.org/jira/browse/HDDS-3459?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
runzhiwang updated HDDS-3459:
-
Attachment: (was: screenshot-13.png)
> Datanode use a single thread to process the command of scm
>
[
https://issues.apache.org/jira/browse/HDDS-3459?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
runzhiwang updated HDDS-3459:
-
Description:
*What's the problem ?*
Datanode use a single [command-processor-thread
[
https://issues.apache.org/jira/browse/HDDS-3459?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17088699#comment-17088699
]
Mukul Kumar Singh commented on HDDS-3459:
-
I think the issue is similar to HDDS-3451.
cc [~nanda]
1 - 100 of 144 matches
Mail list logo
