[
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
>
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
[
https://issues.apache.org/jira/browse/HDDS-3459?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17088754#comment-17088754
]
runzhiwang edited comment on HDDS-3459 at 4/23/20, 12:49 AM:
-
[
https://issues.apache.org/jira/browse/HDDS-3459?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17088754#comment-17088754
]
runzhiwang edited comment on HDDS-3459 at 4/21/20, 11:28 PM:
-
[
https://issues.apache.org/jira/browse/HDDS-3459?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17088754#comment-17088754
]
runzhiwang edited comment on HDDS-3459 at 4/21/20, 4:13 PM:
[~
[
https://issues.apache.org/jira/browse/HDDS-3459?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17088754#comment-17088754
]
runzhiwang edited comment on HDDS-3459 at 4/21/20, 4:06 PM:
[~
[
https://issues.apache.org/jira/browse/HDDS-3459?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17088754#comment-17088754
]
runzhiwang edited comment on HDDS-3459 at 4/21/20, 4:06 PM:
[~
[
https://issues.apache.org/jira/browse/HDDS-3459?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17088754#comment-17088754
]
runzhiwang edited comment on HDDS-3459 at 4/21/20, 4:05 PM:
[~
[
https://issues.apache.org/jira/browse/HDDS-3459?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17088754#comment-17088754
]
runzhiwang edited comment on HDDS-3459 at 4/21/20, 3:02 PM:
[~
[
https://issues.apache.org/jira/browse/HDDS-3459?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17088754#comment-17088754
]
runzhiwang commented on HDDS-3459:
--
[~nanda] Hi, thanks for your explanation. My basic op
[
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://github.com/a
[
https://issues.apache.org/jira/browse/HDDS-3459?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17088721#comment-17088721
]
runzhiwang edited comment on HDDS-3459 at 4/21/20, 2:05 PM:
[~
[
https://issues.apache.org/jira/browse/HDDS-3459?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17088721#comment-17088721
]
runzhiwang commented on HDDS-3459:
--
[~msingh] I think it's not similar to HDDS-3451.
[
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://github.com/a
[
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://github.com/a
[
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://github.com/a
[
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-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-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-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:
-
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-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:
-
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:
-
Description:
*What's the problem ?*
Datanode use a single [command-processor-thread
|https://github.com/a
[
https://issues.apache.org/jira/browse/HDDS-3459?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
runzhiwang updated HDDS-3459:
-
Summary: Datanode use a single thread to process the command of scm (was:
Infinite leader election)
> Da
[
https://issues.apache.org/jira/browse/HDDS-3470?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
runzhiwang updated HDDS-3470:
-
Description:
As the image shows, the SEND_HEARTBEAT response of scm to datanode has a lot of
duplicated c
[
https://issues.apache.org/jira/browse/HDDS-3470?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
runzhiwang updated HDDS-3470:
-
Attachment: (was: screenshot-1.png)
> Duplicated command of scm to datanode
>
[
https://issues.apache.org/jira/browse/HDDS-3470?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
runzhiwang updated HDDS-3470:
-
Attachment: screenshot-2.png
> Duplicated command of scm to datanode
> ---
[
https://issues.apache.org/jira/browse/HDDS-3470?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
runzhiwang updated HDDS-3470:
-
Description:
As the image shows, the SEND_HEARTBEAT response of scm to datanode has a lot of
duplicated c
[
https://issues.apache.org/jira/browse/HDDS-3470?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17088476#comment-17088476
]
runzhiwang commented on HDDS-3470:
--
I'm working on it.
> Duplicated command of scm to da
[
https://issues.apache.org/jira/browse/HDDS-3470?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
runzhiwang updated HDDS-3470:
-
Description:
As the image shows, the SEND_HEARTBEAT response of scm to datanode has a lot of
duplicated c
runzhiwang created HDDS-3470:
Summary: Duplicated command of scm to datanode
Key: HDDS-3470
URL: https://issues.apache.org/jira/browse/HDDS-3470
Project: Hadoop Distributed Data Store
Issue Type:
[
https://issues.apache.org/jira/browse/HDDS-3470?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
runzhiwang updated HDDS-3470:
-
Attachment: screenshot-1.png
> Duplicated command of scm to datanode
> ---
[
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 ?*
There are 3 datanodes in a group: leader, follower1, follower2. Steps
[
https://issues.apache.org/jira/browse/HDDS-3459?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
runzhiwang updated HDDS-3459:
-
Summary: Infinite leader election (was: Infinite leader election in ozone)
> Infinite leader election
> -
[
https://issues.apache.org/jira/browse/HDDS-3459?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
runzhiwang updated HDDS-3459:
-
Summary: Infinite leader election in ozone (was: Infinite group not found)
> Infinite leader election in
[
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 ?*
There are 3 datanodes in a group: leader, follower1, follower2. Steps
[
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 ?*
There are 3 datanodes in a group: leader, follower1, follower2.
1. fol
[
https://issues.apache.org/jira/browse/HDDS-3459?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
runzhiwang updated HDDS-3459:
-
Attachment: screenshot-14.png
> Infinite group not found
>
>
> Ke
[
https://issues.apache.org/jira/browse/HDDS-3459?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
runzhiwang updated HDDS-3459:
-
Attachment: screenshot-12.png
> Infinite group not found
>
>
> Ke
[
https://issues.apache.org/jira/browse/HDDS-3459?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
runzhiwang updated HDDS-3459:
-
Attachment: screenshot-11.png
> Infinite group not found
>
>
> Ke
[
https://issues.apache.org/jira/browse/HDDS-3459?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
runzhiwang updated HDDS-3459:
-
Attachment: screenshot-13.png
> Infinite group not found
>
>
> Ke
[
https://issues.apache.org/jira/browse/HDDS-3459?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
runzhiwang updated HDDS-3459:
-
Attachment: screenshot-10.png
> Infinite group not found
>
>
> Ke
[
https://issues.apache.org/jira/browse/HDDS-3459?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
runzhiwang updated HDDS-3459:
-
Attachment: screenshot-9.png
> Infinite group not found
>
>
> Key
[
https://issues.apache.org/jira/browse/HDDS-3459?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
runzhiwang updated HDDS-3459:
-
Attachment: screenshot-8.png
> Infinite group not found
>
>
> Key
[
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
> Infinite group not found
>
>
> Key
[
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 ?*
There are 3 datanodes in a group: leader, follower1, follower2, then I
[
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
> Infinite group not found
>
>
> Key
[
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
> Infinite group not found
>
>
> Key
[
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 ?*
There are 3 datanodes in a group: leader, follower1, follower2, then I
[
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 ?*
There are 3 datanodes in a group: leader, follower1, follower2, then I
[
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
> Infinite group not found
>
>
> Key
[
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 ?*
There are 3 datanodes in a group: leader, follower1, follower2, then I
[
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
> Infinite group not found
>
>
> Key
[
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 ?*
There are 3 datanodes in a group: leader, follower1, follower2, then I
[
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
> Infinite group not found
>
>
> Key
[
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
> Infinite group not found
>
>
> Key
[
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 ?*
There are 3 datanodes in a group: leader, follower1, follower2, then I
[
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 ?*
There are 3 datanodes in a group: leader, follower1, follower2, then I
[
https://issues.apache.org/jira/browse/HDDS-3459?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17087502#comment-17087502
]
runzhiwang commented on HDDS-3459:
--
I'm working on it.
> Infinite group not found
>
runzhiwang created HDDS-3459:
Summary: Infinite group not found
Key: HDDS-3459
URL: https://issues.apache.org/jira/browse/HDDS-3459
Project: Hadoop Distributed Data Store
Issue Type: Bug
[
https://issues.apache.org/jira/browse/HDDS-3223?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
runzhiwang updated HDDS-3223:
-
Description:
*What's the problem ?*
Read 1000M object, it cost about 470 seconds, i.e. 2.2M/s, which is to
[
https://issues.apache.org/jira/browse/HDDS-3223?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
runzhiwang updated HDDS-3223:
-
Description:
*What's the problem ?*
Read 1000M object, it cost about 470 seconds, i.e. 2.2M/s, which is to
[
https://issues.apache.org/jira/browse/HDDS-3223?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
runzhiwang updated HDDS-3223:
-
Description:
*What's the problem ?*
Read 1000M object, it cost about 470 seconds, i.e. 2.2M/s, which is to
[
https://issues.apache.org/jira/browse/HDDS-3223?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
runzhiwang updated HDDS-3223:
-
Description:
*What's the problem ?*
Read 1000M object, it cost about 470 seconds, i.e. 2.2M/s, which is to
[
https://issues.apache.org/jira/browse/HDDS-3223?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
runzhiwang updated HDDS-3223:
-
Description:
*What's the problem ?*
Read a 1GB file, it cost about 470 seconds, i.e. 2.2M/s, which is too
[
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 100 times (was: S3g
become slower when read bigger ob
[
https://issues.apache.org/jira/browse/HDDS-3223?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
runzhiwang updated HDDS-3223:
-
Description:
*What's the problem ?*
Read a 300M file, it cost about 25 seconds, i.e. 12M/s, which is too s
[
https://issues.apache.org/jira/browse/HDDS-3223?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
runzhiwang updated HDDS-3223:
-
Summary: S3g become slower when read bigger object for error use of skip
(was: S3g become slower when rea
[
https://issues.apache.org/jira/browse/HDDS-3223?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
runzhiwang updated HDDS-3223:
-
Summary: S3g become slower when read bigger object (was: Read a big object
is too slow by s3g)
> S3g bec
[
https://issues.apache.org/jira/browse/HDDS-3223?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
runzhiwang updated HDDS-3223:
-
Priority: Critical (was: Major)
> Read a big object is too slow by s3g
>
[
https://issues.apache.org/jira/browse/HDDS-3223?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
runzhiwang updated HDDS-3223:
-
Description:
*What's the problem ?*
Read a 300M file, it cost about 25 seconds, i.e. 12M/s, which is too s
[
https://issues.apache.org/jira/browse/HDDS-3223?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
runzhiwang updated HDDS-3223:
-
Description:
*What's the problem ?*
Read a 300M file, it cost about 25 seconds, i.e. 12M/s, which is too s
[
https://issues.apache.org/jira/browse/HDDS-3223?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
runzhiwang updated HDDS-3223:
-
Description:
*What's the problem ?*
Read a 300M file, it cost about 25 seconds, i.e. 12M/s, which is too s
[
https://issues.apache.org/jira/browse/HDDS-3223?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17085414#comment-17085414
]
runzhiwang commented on HDDS-3223:
--
I‘m working on it
> Read a big object is slower than
[
https://issues.apache.org/jira/browse/HDDS-3223?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
runzhiwang updated HDDS-3223:
-
Summary: Read a big object is too slow by s3g (was: Read a big object is
slower than write it by s3g)
>
[
https://issues.apache.org/jira/browse/HDDS-3223?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
runzhiwang updated HDDS-3223:
-
Description:
*What's the problem ?*
Read a 300M file, it cost about 25 seconds, i.e. 12.8M/s, which is too
[
https://issues.apache.org/jira/browse/HDDS-3223?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
runzhiwang updated HDDS-3223:
-
Description:
*What's the problem ?*
Read a 320M file, it cost about 25 seconds, i.e. 12.8M/s, which is too
[
https://issues.apache.org/jira/browse/HDDS-3223?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
runzhiwang updated HDDS-3223:
-
Description: !screenshot-1.png!
> Read a big object is slower than write it by s3g
> ---
[
https://issues.apache.org/jira/browse/HDDS-3223?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
runzhiwang updated HDDS-3223:
-
Attachment: screenshot-1.png
> Read a big object is slower than write it by s3g
>
[
https://issues.apache.org/jira/browse/HDDS-3223?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
runzhiwang reopened HDDS-3223:
--
> Read a big object is slower than write it by s3g
>
>
>
[
https://issues.apache.org/jira/browse/HDDS-3223?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
runzhiwang updated HDDS-3223:
-
Description: (was: By s3gateway, write a 187MB file cost 5 seconds, but
read it cost 17 seconds. Both
[
https://issues.apache.org/jira/browse/HDDS-3223?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
runzhiwang updated HDDS-3223:
-
Attachment: (was: screenshot-5.png)
> Read a big object is slower than write it by s3g
> -
[
https://issues.apache.org/jira/browse/HDDS-3223?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
runzhiwang updated HDDS-3223:
-
Comment: was deleted
(was: I think it's related to our own operating system.)
> Read a big object cost 2
[
https://issues.apache.org/jira/browse/HDDS-3223?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
runzhiwang updated HDDS-3223:
-
Summary: Read a big object is slower than write it by s3g (was: Read a big
object cost 2 times more than
[
https://issues.apache.org/jira/browse/HDDS-3223?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
runzhiwang updated HDDS-3223:
-
Attachment: (was: screenshot-3.png)
> Read a big object is slower than write it by s3g
> -
301 - 400 of 648 matches
Mail list logo
