[jira] [Updated] (HDDS-3735) Improve the performance of SCM with 0.78 by decrease the times of lock and unlock

[ https://issues.apache.org/jira/browse/HDDS-3735?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] runzhiwang updated HDDS-3735: - Parent: HDDS-3733 Issue Type: Sub-task (was: Improvement) > Improve the performance of SCM with

[jira] [Updated] (HDDS-3732) Improve the performance of SCM with 7.23% by avoid UUID.toString

[ https://issues.apache.org/jira/browse/HDDS-3732?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] runzhiwang updated HDDS-3732: - Description: I start a ozone cluster with 1000 datanodes, and run two weeks with heavy workload, and

[jira] [Updated] (HDDS-3732) Improve the performance of SCM with 7.23% by avoid UUID.toString

[ https://issues.apache.org/jira/browse/HDDS-3732?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] runzhiwang updated HDDS-3732: - Attachment: screenshot-2.png > Improve the performance of SCM with 7.23% by avoid UUID.toString >

[jira] [Updated] (HDDS-3732) Improve the performance of SCM with 7.23% by avoid UUID.toString

[ https://issues.apache.org/jira/browse/HDDS-3732?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] runzhiwang updated HDDS-3732: - Description: I start a ozone cluster with 1000 datanodes, and run two weeks with heavy workload, and

[jira] [Updated] (HDDS-3732) Improve the performance of SCM with 7.23% by avoid UUID.toString

[ https://issues.apache.org/jira/browse/HDDS-3732?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] runzhiwang updated HDDS-3732: - Summary: Improve the performance of SCM with 7.23% by avoid UUID.toString (was: Improve the performance

[jira] [Updated] (HDDS-3734) Improve the performance of SCM with 3.86% by avoid TreeSet.addAll

[ https://issues.apache.org/jira/browse/HDDS-3734?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] runzhiwang updated HDDS-3734: - Description: TreeSet.addAll cost 7.25% cpu. we need not TreeSet.addAll which cost 3.86% cpu, because the

[jira] [Updated] (HDDS-3734) Improve the performance of SCM with 3.86% by avoid TreeSet.addAll

[ https://issues.apache.org/jira/browse/HDDS-3734?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] runzhiwang updated HDDS-3734: - Description: TreeSet.addAll cost 3.86% cpu. we need not TreeSet.addAll which cost 3.86% cpu, because the

[jira] [Updated] (HDDS-3732) Improve the performance of SCM with 7.32% by avoid UUID.toString

[ https://issues.apache.org/jira/browse/HDDS-3732?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] runzhiwang updated HDDS-3732: - Summary: Improve the performance of SCM with 7.32% by avoid UUID.toString (was: Improve the performance

[jira] [Updated] (HDDS-3734) Improve the performance of SCM by improving queryNodeState

[ https://issues.apache.org/jira/browse/HDDS-3734?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] runzhiwang updated HDDS-3734: - Description: queryNodeState cost 7.25% cpu. 1. we need not TreeSet.addAll which cost 3.86% cpu, because

[jira] [Updated] (HDDS-3734) Improve the performance of SCM by improving queryNodeState

[ https://issues.apache.org/jira/browse/HDDS-3734?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] runzhiwang updated HDDS-3734: - Attachment: screenshot-1.png > Improve the performance of SCM by improving queryNodeState >

[jira] [Updated] (HDDS-3733) Improve the performance of SCM

[ https://issues.apache.org/jira/browse/HDDS-3733?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] runzhiwang updated HDDS-3733: - Description: I start a ozone cluster with 1000 nodes, and run two weeks with heavy workload, and perf

[jira] [Updated] (HDDS-3733) Improve the performance of SCM

[ https://issues.apache.org/jira/browse/HDDS-3733?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] runzhiwang updated HDDS-3733: - Description: I start a ozone cluster with 1000 datanodes, and run two weeks with heavy workload, and perf

[jira] [Created] (HDDS-3734) Improve the performance of SCM by improving queryNodeState

runzhiwang created HDDS-3734: Summary: Improve the performance of SCM by improving queryNodeState Key: HDDS-3734 URL: https://issues.apache.org/jira/browse/HDDS-3734 Project: Hadoop Distributed Data Store

[jira] [Updated] (HDDS-3734) Improve the performance of SCM by improving queryNodeState

[ https://issues.apache.org/jira/browse/HDDS-3734?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] runzhiwang updated HDDS-3734: - Parent: HDDS-3733 Issue Type: Sub-task (was: Improvement) > Improve the performance of SCM by

[jira] [Updated] (HDDS-3732) Improve the performance of SCM by avoid UUID.toString

[ https://issues.apache.org/jira/browse/HDDS-3732?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] runzhiwang updated HDDS-3732: - Parent: HDDS-3733 Issue Type: Sub-task (was: Improvement) > Improve the performance of SCM by

[jira] [Created] (HDDS-3733) Improve the performance of SCM

runzhiwang created HDDS-3733: Summary: Improve the performance of SCM Key: HDDS-3733 URL: https://issues.apache.org/jira/browse/HDDS-3733 Project: Hadoop Distributed Data Store Issue Type:

[jira] [Updated] (HDDS-3732) Improve the performance of SCM by avoid UUID.toString

[ https://issues.apache.org/jira/browse/HDDS-3732?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] runzhiwang updated HDDS-3732: - Description: UUID.toString cost 7.23% CPU. We can store the string of UUID when init DatanodeDetails,

[jira] [Updated] (HDDS-3732) Improve the performance of SCM by avoid UUID.toString

[ https://issues.apache.org/jira/browse/HDDS-3732?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] runzhiwang updated HDDS-3732: - Attachment: screenshot-1.png > Improve the performance of SCM by avoid UUID.toString >

[jira] [Updated] (HDDS-3732) Improve the performance of SCM by avoid UUID.toString

[ https://issues.apache.org/jira/browse/HDDS-3732?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] runzhiwang updated HDDS-3732: - Attachment: output.svg > Improve the performance of SCM by avoid UUID.toString >

[jira] [Created] (HDDS-3732) Improve the performance of SCM by avoid UUID.toString

runzhiwang created HDDS-3732: Summary: Improve the performance of SCM by avoid UUID.toString Key: HDDS-3732 URL: https://issues.apache.org/jira/browse/HDDS-3732 Project: Hadoop Distributed Data Store

[jira] [Comment Edited] (HDDS-3481) SCM ask 31 datanodes to replicate the same container

[ https://issues.apache.org/jira/browse/HDDS-3481?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17126297#comment-17126297 ] runzhiwang edited comment on HDDS-3481 at 6/5/20, 1:26 AM: --- [~nanda] [~arp]

[jira] [Comment Edited] (HDDS-3481) SCM ask 31 datanodes to replicate the same container

[ https://issues.apache.org/jira/browse/HDDS-3481?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17126297#comment-17126297 ] runzhiwang edited comment on HDDS-3481 at 6/5/20, 1:25 AM: --- [~nanda] [~arp]

[jira] [Comment Edited] (HDDS-3481) SCM ask 31 datanodes to replicate the same container

[ https://issues.apache.org/jira/browse/HDDS-3481?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17126297#comment-17126297 ] runzhiwang edited comment on HDDS-3481 at 6/5/20, 1:24 AM: --- [~nanda] [~arp]

[jira] [Comment Edited] (HDDS-3481) SCM ask 31 datanodes to replicate the same container

[ https://issues.apache.org/jira/browse/HDDS-3481?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17126297#comment-17126297 ] runzhiwang edited comment on HDDS-3481 at 6/5/20, 12:51 AM: [~nanda] [~arp]

[jira] [Commented] (HDDS-3481) SCM ask 31 datanodes to replicate the same container

[ https://issues.apache.org/jira/browse/HDDS-3481?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17126297#comment-17126297 ] runzhiwang commented on HDDS-3481: -- [~nanda] [~arp] [~elek] Thanks for review. I thinks your suggestions

[jira] [Updated] (HDDS-3630) Merge rocksdb in datanode

[ https://issues.apache.org/jira/browse/HDDS-3630?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] runzhiwang updated HDDS-3630: - Attachment: (was: Merge RocksDB in Datanode.pdf) > Merge rocksdb in datanode >

[jira] [Updated] (HDDS-3630) Merge rocksdb in datanode

[ https://issues.apache.org/jira/browse/HDDS-3630?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] runzhiwang updated HDDS-3630: - Attachment: Merge RocksDB in Datanode-v1.pdf > Merge rocksdb in datanode > - > >

[jira] [Updated] (HDDS-3630) Merge rocksdb in datanode

[ https://issues.apache.org/jira/browse/HDDS-3630?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] runzhiwang updated HDDS-3630: - Description: Currently, one rocksdb for one container. one container has 5GB capacity. 10TB data need

[jira] [Updated] (HDDS-3630) Merge rocksdb in datanode

[ https://issues.apache.org/jira/browse/HDDS-3630?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] runzhiwang updated HDDS-3630: - Description: Currently, one rocksdb for one container. one container has 5GB capacity. 10TB data need

[jira] [Updated] (HDDS-3630) Merge rocksdb in datanode

[ https://issues.apache.org/jira/browse/HDDS-3630?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] runzhiwang updated HDDS-3630: - Description: Currently, one rocksdb for one container. one container has 5GB capacity. 10TB data need

[jira] [Updated] (HDDS-3630) Merge rocksdb in datanode

[ https://issues.apache.org/jira/browse/HDDS-3630?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] runzhiwang updated HDDS-3630: - Description: Currently, one rocksdb for one container. one container has 5GB capacity. 10TB data need

[jira] [Updated] (HDDS-3630) Merge rocksdb in datanode

[ https://issues.apache.org/jira/browse/HDDS-3630?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] runzhiwang updated HDDS-3630: - Attachment: Merge RocksDB in Datanode.pdf > Merge rocksdb in datanode > - > >

[jira] [Updated] (HDDS-3630) Merge rocksdb in datanode

[ https://issues.apache.org/jira/browse/HDDS-3630?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] runzhiwang updated HDDS-3630: - Description: Currently, one rocksdb for one container. one container has 5GB capacity. 10TB data need

[jira] [Updated] (HDDS-3630) Merge rocksdb in datanode

[ https://issues.apache.org/jira/browse/HDDS-3630?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] runzhiwang updated HDDS-3630: - Description: Currently, one rocksdb for one container. one container has 5GB capacity. 10TB data need

[jira] [Updated] (HDDS-3630) Merge rocksdb in datanode

[ https://issues.apache.org/jira/browse/HDDS-3630?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] runzhiwang updated HDDS-3630: - Summary: Merge rocksdb in datanode (was: Merge rocksdb into one in datanode) > Merge rocksdb in

[jira] [Updated] (HDDS-3630) Merge rocksdb into one in datanode

[ https://issues.apache.org/jira/browse/HDDS-3630?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] runzhiwang updated HDDS-3630: - Description: Currently, one rocksdb for one container. one container has 5GB capacity. 10TB data need

[jira] [Commented] (HDDS-3630) Merge rocksdb into one in datanode

[ https://issues.apache.org/jira/browse/HDDS-3630?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17113815#comment-17113815 ] runzhiwang commented on HDDS-3630: -- [~msingh] Thanks for reminding, I will create a google doc to share

[jira] [Updated] (HDDS-3630) Merge rocksdb into one in datanode

[ https://issues.apache.org/jira/browse/HDDS-3630?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] runzhiwang updated HDDS-3630: - Description: Currently, one rocksdb for one container. one container has 5GB capacity. 10TB data need

[jira] [Created] (HDDS-3630) Merge rocksdb into one in datanode

runzhiwang created HDDS-3630: Summary: Merge rocksdb into one in datanode Key: HDDS-3630 URL: https://issues.apache.org/jira/browse/HDDS-3630 Project: Hadoop Distributed Data Store Issue Type:

[jira] [Updated] (HDDS-3254) Control Datanode memory

[ https://issues.apache.org/jira/browse/HDDS-3254?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] runzhiwang updated HDDS-3254: - Summary: Control Datanode memory (was: Datanode memory leak) > Control Datanode memory >

[jira] [Updated] (HDDS-3626) Limit the off-heap memory of RocksDB in datanode

[ https://issues.apache.org/jira/browse/HDDS-3626?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] runzhiwang updated HDDS-3626: - Description: Datanode occupy 5.2GB physical memory, Xmx is 2200m, MaxDirectMemorySize is 800m, so there

[jira] [Updated] (HDDS-3626) Limit the off-heap memory of RocksDB in datanode

[ https://issues.apache.org/jira/browse/HDDS-3626?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] runzhiwang updated HDDS-3626: - Description: Datanode occupy 5.2GB physical memory, Xmx is 2200m, MaxDirectMemorySize is 800m, so there

[jira] [Created] (HDDS-3626) Limit the off-heap memory of RocksDB in datanode

runzhiwang created HDDS-3626: Summary: Limit the off-heap memory of RocksDB in datanode Key: HDDS-3626 URL: https://issues.apache.org/jira/browse/HDDS-3626 Project: Hadoop Distributed Data Store

[jira] [Resolved] (HDDS-3555) Failed to create bucket by s3g

[ https://issues.apache.org/jira/browse/HDDS-3555?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] runzhiwang resolved HDDS-3555. -- Resolution: Resolved > Failed to create bucket by s3g > -- > >

[jira] [Updated] (HDDS-3223) Improve s3g read 1GB object efficiency by 10 times

[ https://issues.apache.org/jira/browse/HDDS-3223?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] runzhiwang updated HDDS-3223: - Summary: Improve s3g read 1GB object efficiency by 10 times (was: Improve s3g read 1GB object

[jira] [Updated] (HDDS-3514) Fix Memory leak of RaftServerImpl

[ https://issues.apache.org/jira/browse/HDDS-3514?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] runzhiwang updated HDDS-3514: - Summary: Fix Memory leak of RaftServerImpl (was: Memory leak of RaftServerImpl) > Fix Memory leak of

[jira] [Commented] (HDDS-3555) Failed to create bucket by s3g

[ https://issues.apache.org/jira/browse/HDDS-3555?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17101481#comment-17101481 ] runzhiwang commented on HDDS-3555: -- [~adoroszlai] Could you have a look ? > Failed to create bucket by

[jira] [Updated] (HDDS-3555) Failed to create bucket by s3g

[ https://issues.apache.org/jira/browse/HDDS-3555?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] runzhiwang updated HDDS-3555: - Description: command is: aws s3api --endpoint http://ip:9878 create-bucket --bucket idex-bucket code is:

[jira] [Updated] (HDDS-3555) Failed to create bucket by s3g

[ https://issues.apache.org/jira/browse/HDDS-3555?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] runzhiwang updated HDDS-3555: - Description: !screenshot-1.png! > Failed to create bucket by s3g > -- > >

[jira] [Updated] (HDDS-3555) Failed to create bucket by s3g

[ https://issues.apache.org/jira/browse/HDDS-3555?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] runzhiwang updated HDDS-3555: - Attachment: screenshot-1.png > Failed to create bucket by s3g > -- > >

[jira] [Created] (HDDS-3555) Failed to create bucket by s3g

runzhiwang created HDDS-3555: Summary: Failed to create bucket by s3g Key: HDDS-3555 URL: https://issues.apache.org/jira/browse/HDDS-3555 Project: Hadoop Distributed Data Store Issue Type: Bug

[jira] [Updated] (HDDS-3554) Multipart Upload Failed because partName mismatch

[ https://issues.apache.org/jira/browse/HDDS-3554?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] runzhiwang updated HDDS-3554: - Attachment: screenshot-1.png > Multipart Upload Failed because partName mismatch >

[jira] [Updated] (HDDS-3554) Multipart Upload Failed because partName mismatch

[ https://issues.apache.org/jira/browse/HDDS-3554?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] runzhiwang updated HDDS-3554: - Description: !screenshot-1.png! > Multipart Upload Failed because partName mismatch >

[jira] [Assigned] (HDDS-3554) Multipart Upload Failed because partName mismatch

[ https://issues.apache.org/jira/browse/HDDS-3554?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] runzhiwang reassigned HDDS-3554: Assignee: runzhiwang > Multipart Upload Failed because partName mismatch >

[jira] [Created] (HDDS-3554) Multipart Upload Failed because partName mismatch

runzhiwang created HDDS-3554: Summary: Multipart Upload Failed because partName mismatch Key: HDDS-3554 URL: https://issues.apache.org/jira/browse/HDDS-3554 Project: Hadoop Distributed Data Store

[jira] [Resolved] (HDDS-3548) Datanode memory leak because too many PipelineReportsProto

[ https://issues.apache.org/jira/browse/HDDS-3548?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] runzhiwang resolved HDDS-3548. -- Resolution: Not A Problem > Datanode memory leak because too many PipelineReportsProto >

[jira] [Updated] (HDDS-3548) Datanode memory leak because too many PipelineReportsProto

[ https://issues.apache.org/jira/browse/HDDS-3548?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] runzhiwang updated HDDS-3548: - Description: Multi-Raft: 3 pipelines each datanode, the latest commit is

[jira] [Updated] (HDDS-3548) Datanode memory leak because too many PipelineReportsProto

[ https://issues.apache.org/jira/browse/HDDS-3548?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] runzhiwang updated HDDS-3548: - Description: Multi-Raft: 3 pipelines each datanode, the latest commit is

[jira] [Updated] (HDDS-3548) Datanode memory leak because too many PipelineReportsProto

[ https://issues.apache.org/jira/browse/HDDS-3548?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] runzhiwang updated HDDS-3548: - Description: Multi-Raft: 3 pipelines each datanode, the latest commit is

[jira] [Updated] (HDDS-3548) Datanode memory leak because too many PipelineReportsProto

[ https://issues.apache.org/jira/browse/HDDS-3548?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] runzhiwang updated HDDS-3548: - Description: Multi-Raft 3 pipeline each datanode, the latest commit is

[jira] [Updated] (HDDS-3548) Datanode memory leak because too many PipelineReportsProto

[ https://issues.apache.org/jira/browse/HDDS-3548?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] runzhiwang updated HDDS-3548: - Description: Environment: Multi-Raft, the latest commit is

[jira] [Updated] (HDDS-3548) Datanode memory leak because too many PipelineReportsProto

[ https://issues.apache.org/jira/browse/HDDS-3548?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] runzhiwang updated HDDS-3548: - Description: Environment: Multi-Raft, the latest commit is

[jira] [Updated] (HDDS-3548) Datanode memory leak because too many PipelineReportsProto

[ https://issues.apache.org/jira/browse/HDDS-3548?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] runzhiwang updated HDDS-3548: - Description: 1.  LinkedList @ 0x77053df98 occupy 1.8GB memory !image-2020-05-06-17-11-43-422.png!  2.

[jira] [Updated] (HDDS-3548) Datanode memory leak because too many PipelineReportsProto

[ https://issues.apache.org/jira/browse/HDDS-3548?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] runzhiwang updated HDDS-3548: - Description: 1.  LinkedList @ 0x77053df98 occupy 1.8G !image-2020-05-06-17-11-43-422.png!  2. The item

[jira] [Updated] (HDDS-3548) Datanode memory leak because too many PipelineReportsProto

[ https://issues.apache.org/jira/browse/HDDS-3548?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] runzhiwang updated HDDS-3548: - Attachment: image-2020-05-06-17-16-02-519.png > Datanode memory leak because too many

[jira] [Updated] (HDDS-3548) Datanode memory leak because too many PipelineReportsProto

[ https://issues.apache.org/jira/browse/HDDS-3548?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] runzhiwang updated HDDS-3548: - Description: 1. 3107 instances of PielineReportsProto occupy 1.8GB memory

[jira] [Updated] (HDDS-3548) Datanode memory leak because too many PipelineReportsProto

[ https://issues.apache.org/jira/browse/HDDS-3548?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] runzhiwang updated HDDS-3548: - Attachment: image-2020-05-06-17-11-43-422.png > Datanode memory leak because too many

[jira] [Updated] (HDDS-3548) Datanode memory leak because too many PipelineReportsProto

[ https://issues.apache.org/jira/browse/HDDS-3548?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] runzhiwang updated HDDS-3548: - Description: 1. 3107 instances of PielineReportsProto occupy 1.8GB memory

[jira] [Updated] (HDDS-3548) Datanode memory leak because too many PipelineReportsProto

[ https://issues.apache.org/jira/browse/HDDS-3548?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] runzhiwang updated HDDS-3548: - Description: !image-2020-05-06-17-06-21-189.png! > Datanode memory leak because too many

[jira] [Updated] (HDDS-3548) Datanode memory leak because too many PipelineReportsProto

[ https://issues.apache.org/jira/browse/HDDS-3548?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] runzhiwang updated HDDS-3548: - Attachment: image-2020-05-06-17-06-21-189.png > Datanode memory leak because too many

[jira] [Updated] (HDDS-3548) Datanode memory leak because too many PipelineReportsProto

[ https://issues.apache.org/jira/browse/HDDS-3548?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] runzhiwang updated HDDS-3548: - Parent: HDDS-3254 Issue Type: Sub-task (was: Bug) > Datanode memory leak because too many

[jira] [Created] (HDDS-3548) Datanode memory leak because too many PipelineReportsProto

runzhiwang created HDDS-3548: Summary: Datanode memory leak because too many PipelineReportsProto Key: HDDS-3548 URL: https://issues.apache.org/jira/browse/HDDS-3548 Project: Hadoop Distributed Data Store

[jira] [Updated] (HDDS-3254) Datanode memory leak

[ https://issues.apache.org/jira/browse/HDDS-3254?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] runzhiwang updated HDDS-3254: - Summary: Datanode memory leak (was: Datanode memory increase so much) > Datanode memory leak >

[jira] [Updated] (HDDS-3514) Memory leak of RaftServerImpl

[ https://issues.apache.org/jira/browse/HDDS-3514?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] runzhiwang updated HDDS-3514: - Description: This depends on [RATIS-845|https://issues.apache.org/jira/browse/RATIS-845], find the

[jira] [Created] (HDDS-3514) Memory leak of RaftServerImpl

runzhiwang created HDDS-3514: Summary: Memory leak of RaftServerImpl Key: HDDS-3514 URL: https://issues.apache.org/jira/browse/HDDS-3514 Project: Hadoop Distributed Data Store Issue Type: Bug

[jira] [Updated] (HDDS-3481) SCM ask 31 datanodes to replicate the same container

[ https://issues.apache.org/jira/browse/HDDS-3481?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] runzhiwang updated HDDS-3481: - Attachment: screenshot-4.png > SCM ask 31 datanodes to replicate the same container >

[jira] [Updated] (HDDS-3481) SCM ask 31 datanodes to replicate the same container

[ https://issues.apache.org/jira/browse/HDDS-3481?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] runzhiwang updated HDDS-3481: - Description: *What's the problem ?* As the image shows, scm ask 31 datanodes to replicate container 2037

[jira] [Updated] (HDDS-3481) SCM ask 31 datanodes to replicate the same container

[ https://issues.apache.org/jira/browse/HDDS-3481?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] runzhiwang updated HDDS-3481: - Description: *What's the problem ?* As the image shows, scm ask 31 datanodes to replicate container 2037

[jira] [Updated] (HDDS-3481) SCM ask 31 datanodes to replicate the same container

[ https://issues.apache.org/jira/browse/HDDS-3481?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] runzhiwang updated HDDS-3481: - Description: *What's the problem ?* As the image shows, scm ask 31 datanodes to replicate container 2037

[jira] [Updated] (HDDS-3481) SCM ask 31 datanodes to replicate the same container

[ https://issues.apache.org/jira/browse/HDDS-3481?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] runzhiwang updated HDDS-3481: - Attachment: screenshot-3.png > SCM ask 31 datanodes to replicate the same container >

[jira] [Updated] (HDDS-3481) SCM ask 31 datanodes to replicate the same container

[ https://issues.apache.org/jira/browse/HDDS-3481?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] runzhiwang updated HDDS-3481: - Description: *What's the problem ?* As the image shows, scm ask 31 datanodes to replicate container 2037

[jira] [Updated] (HDDS-3481) SCM ask 31 datanodes to replicate the same container

[ https://issues.apache.org/jira/browse/HDDS-3481?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] runzhiwang updated HDDS-3481: - Description: *What's the problem ?* As the image shows, scm ask 31 datanodes to replicate container 2037

[jira] [Updated] (HDDS-3481) SCM ask 31 datanodes to replicate the same container

[ https://issues.apache.org/jira/browse/HDDS-3481?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] runzhiwang updated HDDS-3481: - Description: *What's the problem ?* As the image shows, scm ask 31 datanodes to replicate container 2037

[jira] [Updated] (HDDS-3481) SCM ask 31 datanodes to replicate the same container

[ https://issues.apache.org/jira/browse/HDDS-3481?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] runzhiwang updated HDDS-3481: - Description: *What's the problem ?* As the image shows, scm ask 31 datanodes to replicate container 2037

[jira] [Updated] (HDDS-3481) SCM ask 31 datanodes to replicate the same container

[ https://issues.apache.org/jira/browse/HDDS-3481?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] runzhiwang updated HDDS-3481: - Description: As the image shows, scm ask 31 datanodes to replicate container 2037 every 10 minutes.

[jira] [Assigned] (HDDS-3481) SCM ask 31 datanodes to replicate the same container

[ https://issues.apache.org/jira/browse/HDDS-3481?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] runzhiwang reassigned HDDS-3481: Assignee: runzhiwang > SCM ask 31 datanodes to replicate the same container >

[jira] [Updated] (HDDS-3481) SCM ask 31 datanodes to replicate the same container

[ https://issues.apache.org/jira/browse/HDDS-3481?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] runzhiwang updated HDDS-3481: - Description: As !screenshot-1.png! was: !screenshot-1.png! > SCM ask 31 datanodes to replicate

[jira] [Updated] (HDDS-3481) SCM ask 31 datanodes to replicate the same container

[ https://issues.apache.org/jira/browse/HDDS-3481?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] runzhiwang updated HDDS-3481: - Description: !screenshot-1.png! > SCM ask 31 datanodes to replicate the same container >

[jira] [Updated] (HDDS-3481) SCM ask 31 datanodes to replicate the same container

[ https://issues.apache.org/jira/browse/HDDS-3481?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] runzhiwang updated HDDS-3481: - Attachment: screenshot-1.png > SCM ask 31 datanodes to replicate the same container >

[jira] [Created] (HDDS-3481) SCM ask 31 datanodes to replicate the same container

runzhiwang created HDDS-3481: Summary: SCM ask 31 datanodes to replicate the same container Key: HDDS-3481 URL: https://issues.apache.org/jira/browse/HDDS-3481 Project: Hadoop Distributed Data Store

[jira] [Comment Edited] (HDDS-3459) 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:comment-tabpanel=17088754#comment-17088754 ] runzhiwang edited comment on HDDS-3459 at 4/23/20, 12:49 AM: - I will share the

[jira] [Comment Edited] (HDDS-3459) 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:comment-tabpanel=17088754#comment-17088754 ] runzhiwang edited comment on HDDS-3459 at 4/21/20, 11:28 PM: - [~nanda] Hi,

[jira] [Comment Edited] (HDDS-3459) 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:comment-tabpanel=17088754#comment-17088754 ] runzhiwang edited comment on HDDS-3459 at 4/21/20, 4:13 PM: [~nanda] Hi,

[jira] [Comment Edited] (HDDS-3459) 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:comment-tabpanel=17088754#comment-17088754 ] runzhiwang edited comment on HDDS-3459 at 4/21/20, 4:06 PM: [~nanda] Hi,

[jira] [Comment Edited] (HDDS-3459) 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:comment-tabpanel=17088754#comment-17088754 ] runzhiwang edited comment on HDDS-3459 at 4/21/20, 4:06 PM: [~nanda] Hi,

[jira] [Comment Edited] (HDDS-3459) 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:comment-tabpanel=17088754#comment-17088754 ] runzhiwang edited comment on HDDS-3459 at 4/21/20, 4:05 PM: [~nanda] Hi,

[jira] [Comment Edited] (HDDS-3459) 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:comment-tabpanel=17088754#comment-17088754 ] runzhiwang edited comment on HDDS-3459 at 4/21/20, 3:02 PM: [~nanda] Hi,

[jira] [Commented] (HDDS-3459) 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:comment-tabpanel=17088754#comment-17088754 ] runzhiwang commented on HDDS-3459: -- [~nanda] Hi, thanks for your explanation. My basic opinion is: 1.

[jira] [Updated] (HDDS-3459) 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

[jira] [Comment Edited] (HDDS-3459) 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:comment-tabpanel=17088721#comment-17088721 ] runzhiwang edited comment on HDDS-3459 at 4/21/20, 2:05 PM: [~msingh] I think

<    1   2   3   4   5   6   7   >