[jira] [Updated] (HDDS-3223) Read a big object cost 2 times more 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: By s3gateway, write a 187MB file cost 5 seconds, but read it cost 17 seconds. I use {code:ja

[jira] [Updated] (HDDS-3223) Read a big object cost 2 times more 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: By s3gateway, write a 187MB file cost 5 seconds, but read it cost 17 seconds. I use tcpdump

[jira] [Updated] (HDDS-3223) Read a big object cost 2 times more 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: By s3gateway, write a 187MB file cost 5 seconds, but read it cost 17 seconds. I use tcpdump

[jira] [Updated] (HDDS-3223) Read a big object cost 2 times more 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: By s3gateway, write a 187MB file cost 5 seconds, but read it cost 17 seconds. I use tcpdump

[jira] [Updated] (HDDS-3223) Read a big object cost 2 times more 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-3.png > Read a big object cost 2 times more than write it by s3g >

[jira] [Updated] (HDDS-3223) Read a big object cost 2 times more 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: By s3gateway, write a 187MB file cost 5 seconds, but read it cost 17 seconds. I use tcpdump

[jira] [Updated] (HDDS-3223) Read a big object cost 2 times more 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: By s3gateway, write a 187MB file cost 5 seconds, but read it cost 17 seconds. I use tcpdump

[jira] [Updated] (HDDS-3223) Read a big object cost 2 times more 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: By s3gateway, write a 187MB file cost 5 seconds, but read it cost 17 seconds. I use tcpdump

[jira] [Updated] (HDDS-3223) Read a big object cost 2 times more 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: By s3gateway, write a 187MB file cost 5 seconds, but read it cost 17 seconds. I use tcpdump

[jira] [Updated] (HDDS-3223) Read a big object cost 2 times more 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: By s3gateway, write a 187MB file cost 5 seconds, but read it cost 17 seconds. !screenshot-1

[jira] [Updated] (HDDS-3223) Read a big object cost 2 times more 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 cost 2 times more than write it by s3g >

[jira] [Updated] (HDDS-3223) Read a big object cost 2 times more 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-2.png > Read a big object cost 2 times more than write it by s3g >

[jira] [Updated] (HDDS-3223) Read a big object cost 2 times more 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: By s3gateway, write a 187MB file cost 5 seconds, but read it cost 17 seconds. The write and r

[jira] [Assigned] (HDDS-3223) Read a big object cost 2 times more than write it by s3g

[ https://issues.apache.org/jira/browse/HDDS-3223?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] runzhiwang reassigned HDDS-3223: Assignee: runzhiwang > Read a big object cost 2 times more than write it by s3g > -

[jira] [Commented] (HDDS-3223) Read a big object cost 2 times more than write it by s3g

[ https://issues.apache.org/jira/browse/HDDS-3223?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17060612#comment-17060612 ] runzhiwang commented on HDDS-3223: -- I'm working on it. > Read a big object cost 2 times

[jira] [Updated] (HDDS-3223) Read a big object cost 2 times more 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: By s3gateway, write a 187MB file cost 5 seconds, but read it cost 17 seconds. The write and r

[jira] [Updated] (HDDS-3223) Read a big object cost 2 times more 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: - Summary: Read a big object cost 2 times more than write it by s3g (was: Improve the read efficiency of bi

[jira] [Updated] (HDDS-3223) Improve the read efficiency of big object in s3g

[ https://issues.apache.org/jira/browse/HDDS-3223?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] runzhiwang updated HDDS-3223: - Description: By s3gateway, write a 187MB file cost 5 seconds, but read it cost 17 seconds. The write and r

[jira] [Updated] (HDDS-3223) Improve the read efficiency of big object in s3g

[ https://issues.apache.org/jira/browse/HDDS-3223?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] runzhiwang updated HDDS-3223: - Description: By s3gateway, write a 200MB file cost 5 seconds, but read it cost 17 seconds. And > Improve

[jira] [Updated] (HDDS-3223) Improve the read efficiency of big object in s3g

[ https://issues.apache.org/jira/browse/HDDS-3223?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] runzhiwang updated HDDS-3223: - Issue Type: Improvement (was: Bug) > Improve the read efficiency of big object in s3g > -

[jira] [Created] (HDDS-3223) Improve the read efficiency of big object in s3g

runzhiwang created HDDS-3223: Summary: Improve the read efficiency of big object in s3g Key: HDDS-3223 URL: https://issues.apache.org/jira/browse/HDDS-3223 Project: Hadoop Distributed Data Store

[jira] [Updated] (HDDS-3168) Merge a lot of RPC call getContainerWithPipeline into one

[ https://issues.apache.org/jira/browse/HDDS-3168?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] runzhiwang updated HDDS-3168: - Summary: Merge a lot of RPC call getContainerWithPipeline into one (was: Merge a lot of RPC call getConta

[jira] [Updated] (HDDS-3168) Merge a lot of RPC call getContainerWithPipeline into one

[ https://issues.apache.org/jira/browse/HDDS-3168?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] runzhiwang updated HDDS-3168: - Description: !screenshot-3.png! (was: Read a 100MB object which has 25 chunks, the jaeger trace informa

[jira] [Updated] (HDDS-3168) Merge a lot of RPC call getContainerWithPipeline

[ https://issues.apache.org/jira/browse/HDDS-3168?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] runzhiwang updated HDDS-3168: - Summary: Merge a lot of RPC call getContainerWithPipeline (was: Merge a lot of RPC call getContainerWithP

[jira] [Updated] (HDDS-3168) Merge a lot of RPC call getContainerWithPipeline into one

[ https://issues.apache.org/jira/browse/HDDS-3168?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] runzhiwang updated HDDS-3168: - Summary: Merge a lot of RPC call getContainerWithPipeline into one (was: Merge a lot of RPC call ) > Mer

[jira] [Updated] (HDDS-3168) Merge a lot of RPC call

[ https://issues.apache.org/jira/browse/HDDS-3168?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] runzhiwang updated HDDS-3168: - Summary: Merge a lot of RPC call (was: Improve the efficiency of reading object) > Merge a lot of RPC c

[jira] [Comment Edited] (HDDS-1933) Datanode should use hostname in place of ip addresses to allow DN's to work when ipaddress change

[ https://issues.apache.org/jira/browse/HDDS-1933?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17058543#comment-17058543 ] runzhiwang edited comment on HDDS-1933 at 3/13/20, 9:23 AM: I

[jira] [Comment Edited] (HDDS-1933) Datanode should use hostname in place of ip addresses to allow DN's to work when ipaddress change

[ https://issues.apache.org/jira/browse/HDDS-1933?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17058543#comment-17058543 ] runzhiwang edited comment on HDDS-1933 at 3/13/20, 9:23 AM: I

[jira] [Comment Edited] (HDDS-1933) Datanode should use hostname in place of ip addresses to allow DN's to work when ipaddress change

[ https://issues.apache.org/jira/browse/HDDS-1933?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17058543#comment-17058543 ] runzhiwang edited comment on HDDS-1933 at 3/13/20, 9:18 AM: I

[jira] [Commented] (HDDS-1933) Datanode should use hostname in place of ip addresses to allow DN's to work when ipaddress change

[ https://issues.apache.org/jira/browse/HDDS-1933?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17058543#comment-17058543 ] runzhiwang commented on HDDS-1933: -- I change getIpAddress at the following links to getHo

[jira] [Commented] (HDDS-1933) Datanode should use hostname in place of ip addresses to allow DN's to work when ipaddress change

[ https://issues.apache.org/jira/browse/HDDS-1933?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17058476#comment-17058476 ] runzhiwang commented on HDDS-1933: -- [~swagle] Hi, I think the following code use the ipad

[jira] [Updated] (HDDS-3168) Improve the efficiency of reading object

[ https://issues.apache.org/jira/browse/HDDS-3168?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] runzhiwang updated HDDS-3168: - Description: Read a 100MB object which has 25 chunks, the jaeger trace information as the image shows. Now

[jira] [Updated] (HDDS-3168) Improve the efficiency of reading object

[ https://issues.apache.org/jira/browse/HDDS-3168?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] runzhiwang updated HDDS-3168: - Description: Read a 100MB object which 25 chunks, the jaeger trace information as the image shows. Now ozo

[jira] [Updated] (HDDS-3171) Couldn't create RpcClient protocol exception on k8s.

[ https://issues.apache.org/jira/browse/HDDS-3171?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] runzhiwang updated HDDS-3171: - Summary: Couldn't create RpcClient protocol exception on k8s. (was: Couldn't create RpcClient protocol ex

[jira] [Commented] (HDDS-3171) Couldn't create RpcClient protocol exception on k8s.

[ https://issues.apache.org/jira/browse/HDDS-3171?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17058369#comment-17058369 ] runzhiwang commented on HDDS-3171: -- I'm working on it. > Couldn't create RpcClient proto

[jira] [Updated] (HDDS-3171) Couldn't create RpcClient protocol exception in k8s.

[ https://issues.apache.org/jira/browse/HDDS-3171?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] runzhiwang updated HDDS-3171: - Description: Start ozone on k8s, sometimes it report Couldn't create RpcClient protocol exception on k8s,

[jira] [Updated] (HDDS-3171) Couldn't create RpcClient protocol exception in k8s.

[ https://issues.apache.org/jira/browse/HDDS-3171?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] runzhiwang updated HDDS-3171: - Attachment: screenshot-1.png > Couldn't create RpcClient protocol exception in k8s. >

[jira] [Assigned] (HDDS-3171) Couldn't create RpcClient protocol exception in k8s.

[ https://issues.apache.org/jira/browse/HDDS-3171?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] runzhiwang reassigned HDDS-3171: Assignee: runzhiwang > Couldn't create RpcClient protocol exception in k8s. > -

[jira] [Updated] (HDDS-3171) Couldn't create RpcClient protocol exception in k8s.

[ https://issues.apache.org/jira/browse/HDDS-3171?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] runzhiwang updated HDDS-3171: - Description: Start ozone on k8s, sometimes it report !screenshot-1.png! was: !screenshot-1.png! >

[jira] [Updated] (HDDS-3171) Couldn't create RpcClient protocol exception in k8s.

[ https://issues.apache.org/jira/browse/HDDS-3171?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] runzhiwang updated HDDS-3171: - Description: !screenshot-1.png! > Couldn't create RpcClient protocol exception in k8s. > ---

[jira] [Created] (HDDS-3171) Couldn't create RpcClient protocol exception in k8s.

runzhiwang created HDDS-3171: Summary: Couldn't create RpcClient protocol exception in k8s. Key: HDDS-3171 URL: https://issues.apache.org/jira/browse/HDDS-3171 Project: Hadoop Distributed Data Store

[jira] [Commented] (HDDS-1933) Datanode should use hostname in place of ip addresses to allow DN's to work when ipaddress change

[ https://issues.apache.org/jira/browse/HDDS-1933?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17058305#comment-17058305 ] runzhiwang commented on HDDS-1933: -- [~swagle] Okay, I see. I will check the code and find

[jira] [Commented] (HDDS-1933) Datanode should use hostname in place of ip addresses to allow DN's to work when ipaddress change

[ https://issues.apache.org/jira/browse/HDDS-1933?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17058302#comment-17058302 ] runzhiwang commented on HDDS-1933: -- [~swagle] Hi, I'm sorry, but what do you mean "making

[jira] [Commented] (HDDS-1933) Datanode should use hostname in place of ip addresses to allow DN's to work when ipaddress change

[ https://issues.apache.org/jira/browse/HDDS-1933?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17058297#comment-17058297 ] runzhiwang commented on HDDS-1933: -- [~swagle] set dfs.datanode.use.datanode.hostname cann

[jira] [Commented] (HDDS-3168) Improve the efficiency of reading object

[ https://issues.apache.org/jira/browse/HDDS-3168?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17057622#comment-17057622 ] runzhiwang commented on HDDS-3168: -- I'm working on it. > Improve the efficiency of readi

[jira] [Updated] (HDDS-3168) Improve the efficiency of reading object

[ https://issues.apache.org/jira/browse/HDDS-3168?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] runzhiwang updated HDDS-3168: - Description: Read a 100MB object which 25 chunks, the jaeger trace information as the image shows. Now ozo

[jira] [Updated] (HDDS-3168) Improve the efficiency of reading object

[ https://issues.apache.org/jira/browse/HDDS-3168?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] runzhiwang updated HDDS-3168: - Description: Read a 100MB object, the jaeger trace information as the image shows. Now ozone read each chu

[jira] [Updated] (HDDS-3168) Improve the efficiency of reading object

[ https://issues.apache.org/jira/browse/HDDS-3168?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] runzhiwang updated HDDS-3168: - Description: !screenshot-3.png! (was: !screenshot-2.png! ) > Improve the efficiency of reading object

[jira] [Updated] (HDDS-3168) Improve the efficiency of reading object

[ https://issues.apache.org/jira/browse/HDDS-3168?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] runzhiwang updated HDDS-3168: - Attachment: screenshot-3.png > Improve the efficiency of reading object >

[jira] [Updated] (HDDS-3168) Improve the efficiency of reading object

[ https://issues.apache.org/jira/browse/HDDS-3168?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] runzhiwang updated HDDS-3168: - Description: !screenshot-2.png! (was: !screenshot-1.png! ) > Improve the efficiency of reading object

[jira] [Updated] (HDDS-3168) Improve the efficiency of reading object

[ https://issues.apache.org/jira/browse/HDDS-3168?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] runzhiwang updated HDDS-3168: - Attachment: screenshot-2.png > Improve the efficiency of reading object >

[jira] [Updated] (HDDS-3168) Improve the efficiency of reading object

[ https://issues.apache.org/jira/browse/HDDS-3168?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] runzhiwang updated HDDS-3168: - Description: !screenshot-1.png! > Improve the efficiency of reading object > ---

[jira] [Updated] (HDDS-3168) Improve the efficiency of reading object

[ https://issues.apache.org/jira/browse/HDDS-3168?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] runzhiwang updated HDDS-3168: - Attachment: screenshot-1.png > Improve the efficiency of reading object >

[jira] [Created] (HDDS-3168) Improve the efficiency of reading object

runzhiwang created HDDS-3168: Summary: Improve the efficiency of reading object Key: HDDS-3168 URL: https://issues.apache.org/jira/browse/HDDS-3168 Project: Hadoop Distributed Data Store Issue Ty

[jira] [Updated] (HDDS-3158) Create client for each request in s3g cost too much time.

[ https://issues.apache.org/jira/browse/HDDS-3158?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] runzhiwang updated HDDS-3158: - Description: S3gateway create client for each request, but create a client cost about 5 ms, which is too

[jira] [Updated] (HDDS-3158) Create client for each request in s3g cost too much time.

[ https://issues.apache.org/jira/browse/HDDS-3158?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] runzhiwang updated HDDS-3158: - Affects Version/s: 0.5.0 > Create client for each request in s3g cost too much time. > ---

[jira] [Updated] (HDDS-3158) Create client for each request in s3g cost too much time.

[ https://issues.apache.org/jira/browse/HDDS-3158?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] runzhiwang updated HDDS-3158: - Description: S3gateway create client for each request, but create a client cost about > Create client fo

[jira] [Created] (HDDS-3158) Create client for each request in s3g cost too much time.

runzhiwang created HDDS-3158: Summary: Create client for each request in s3g cost too much time. Key: HDDS-3158 URL: https://issues.apache.org/jira/browse/HDDS-3158 Project: Hadoop Distributed Data Store

[jira] [Updated] (HDDS-3130) Add trace span in s3gateway

[ https://issues.apache.org/jira/browse/HDDS-3130?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] runzhiwang updated HDDS-3130: - Attachment: (was: image-2020-03-05-13-59-29-552.png) > Add trace span in s3gateway > -

[jira] [Updated] (HDDS-3130) Add trace span in s3gateway

[ https://issues.apache.org/jira/browse/HDDS-3130?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] runzhiwang updated HDDS-3130: - Summary: Add trace span in s3gateway (was: jaeger can not work normal) > Add trace span in s3gateway > --

[jira] [Updated] (HDDS-3130) Add trace span in s3gateway

[ https://issues.apache.org/jira/browse/HDDS-3130?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] runzhiwang updated HDDS-3130: - Description: (was: Just as the image shows, the trace information of CreateKey is not enough. !image-

[jira] [Updated] (HDDS-3130) Add jaeger trace span in s3gateway

[ https://issues.apache.org/jira/browse/HDDS-3130?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] runzhiwang updated HDDS-3130: - Summary: Add jaeger trace span in s3gateway (was: Add trace span in s3gateway) > Add jaeger trace span i

[jira] [Updated] (HDDS-3130) jaeger can not work normal

[ https://issues.apache.org/jira/browse/HDDS-3130?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] runzhiwang updated HDDS-3130: - Issue Type: Improvement (was: Bug) > jaeger can not work normal > -- > >

[jira] [Resolved] (HDDS-3124) Time interval calculate error

[ https://issues.apache.org/jira/browse/HDDS-3124?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] runzhiwang resolved HDDS-3124. -- Resolution: Fixed > Time interval calculate error > -- > >

[jira] [Resolved] (HDDS-3041) Memory leak of s3g

[ https://issues.apache.org/jira/browse/HDDS-3041?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] runzhiwang resolved HDDS-3041. -- Resolution: Fixed > Memory leak of s3g > -- > > Key: HDDS-3041 >

[jira] [Commented] (HDDS-3127) docker compose should create headless principals for test users

[ https://issues.apache.org/jira/browse/HDDS-3127?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17051829#comment-17051829 ] runzhiwang commented on HDDS-3127: -- I'm working on it > docker compose should create hea

[jira] [Assigned] (HDDS-3127) docker compose should create headless principals for test users

[ https://issues.apache.org/jira/browse/HDDS-3127?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] runzhiwang reassigned HDDS-3127: Assignee: runzhiwang > docker compose should create headless principals for test users > --

[jira] [Assigned] (HDDS-3122) Fail to destroy pipeline in k8s when redeploy DataNode

[ https://issues.apache.org/jira/browse/HDDS-3122?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] runzhiwang reassigned HDDS-3122: Assignee: runzhiwang > Fail to destroy pipeline in k8s when redeploy DataNode > ---

[jira] [Commented] (HDDS-3130) jaeger can not work normal

[ https://issues.apache.org/jira/browse/HDDS-3130?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17051828#comment-17051828 ] runzhiwang commented on HDDS-3130: -- I'm working on it > jaeger can not work normal > ---

[jira] [Created] (HDDS-3130) jaeger can not work normal

runzhiwang created HDDS-3130: Summary: jaeger can not work normal Key: HDDS-3130 URL: https://issues.apache.org/jira/browse/HDDS-3130 Project: Hadoop Distributed Data Store Issue Type: Bug

[jira] [Updated] (HDDS-3124) Time interval calculate error

[ https://issues.apache.org/jira/browse/HDDS-3124?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] runzhiwang updated HDDS-3124: - Description: Just as the image shows, the time interval in log "Unable to communicate to SCM server at sc

[jira] [Updated] (HDDS-3124) Time interval calculate error

[ https://issues.apache.org/jira/browse/HDDS-3124?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] runzhiwang updated HDDS-3124: - Attachment: (was: screenshot-2.png) > Time interval calculate error > --

[jira] [Updated] (HDDS-3124) Time interval calculate error

[ https://issues.apache.org/jira/browse/HDDS-3124?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] runzhiwang updated HDDS-3124: - Attachment: (was: screenshot-3.png) > Time interval calculate error > --

[jira] [Updated] (HDDS-3124) Time interval calculate error

[ https://issues.apache.org/jira/browse/HDDS-3124?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] runzhiwang updated HDDS-3124: - Attachment: (was: screenshot-1.png) > Time interval calculate error > --

[jira] [Updated] (HDDS-3124) Time interval calculate error

[ https://issues.apache.org/jira/browse/HDDS-3124?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] runzhiwang updated HDDS-3124: - Attachment: (was: screenshot-4.png) > Time interval calculate error > --

[jira] [Updated] (HDDS-3124) Time interval calculate error

[ https://issues.apache.org/jira/browse/HDDS-3124?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] runzhiwang updated HDDS-3124: - Attachment: screenshot-1.png > Time interval calculate error > -- > >

[jira] [Updated] (HDDS-3124) Time interval calculate error

[ https://issues.apache.org/jira/browse/HDDS-3124?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] runzhiwang updated HDDS-3124: - Description: Just as the image shows, the time interval in log "Unable to communicate to SCM server at sc

[jira] [Commented] (HDDS-3125) Can not make full use of all datanodes.

[ https://issues.apache.org/jira/browse/HDDS-3125?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17050718#comment-17050718 ] runzhiwang commented on HDDS-3125: -- I'm working on it. > Can not make full use of all da

[jira] [Assigned] (HDDS-3125) Can not make full use of all datanodes.

[ https://issues.apache.org/jira/browse/HDDS-3125?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] runzhiwang reassigned HDDS-3125: Assignee: runzhiwang > Can not make full use of all datanodes. > --

[jira] [Updated] (HDDS-3125) Can not make full use of all datanodes.

[ https://issues.apache.org/jira/browse/HDDS-3125?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] runzhiwang updated HDDS-3125: - Description: I deploy ozone on k8s with multi-raft open, deploy datanode on 18 machines, each machine sta

[jira] [Updated] (HDDS-3125) Can not make full use of all datanodes.

[ https://issues.apache.org/jira/browse/HDDS-3125?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] runzhiwang updated HDDS-3125: - Attachment: screenshot-1.png > Can not make full use of all datanodes. > -

[jira] [Created] (HDDS-3125) Can not make full use of all datanodes.

runzhiwang created HDDS-3125: Summary: Can not make full use of all datanodes. Key: HDDS-3125 URL: https://issues.apache.org/jira/browse/HDDS-3125 Project: Hadoop Distributed Data Store Issue Typ

[jira] [Assigned] (HDDS-3124) Time interval calculate error

[ https://issues.apache.org/jira/browse/HDDS-3124?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] runzhiwang reassigned HDDS-3124: Assignee: runzhiwang > Time interval calculate error > -- > >

[jira] [Commented] (HDDS-3124) Time interval calculate error

[ https://issues.apache.org/jira/browse/HDDS-3124?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17050689#comment-17050689 ] runzhiwang commented on HDDS-3124: -- I'm working on it. > Time interval calculate error

[jira] [Updated] (HDDS-3124) Time interval calculate error

[ https://issues.apache.org/jira/browse/HDDS-3124?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] runzhiwang updated HDDS-3124: - Description: Just as the image shows, the time interval in log "Unable to communicate to SCM server at sc

[jira] [Updated] (HDDS-3124) Time interval calculate error

[ https://issues.apache.org/jira/browse/HDDS-3124?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] runzhiwang updated HDDS-3124: - Description: Just as the image shows, the time interval in log "Unable to communicate to SCM server at sc

[jira] [Updated] (HDDS-3124) Time interval calculate error

[ https://issues.apache.org/jira/browse/HDDS-3124?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] runzhiwang updated HDDS-3124: - Attachment: screenshot-4.png > Time interval calculate error > -- > >

[jira] [Updated] (HDDS-3124) Time interval calculate error

[ https://issues.apache.org/jira/browse/HDDS-3124?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] runzhiwang updated HDDS-3124: - Description: !screenshot-2.png! !screenshot-3.png! !screenshot-4.png! was: !screenshot-2.png!

[jira] [Updated] (HDDS-3124) Time interval calculate error

[ https://issues.apache.org/jira/browse/HDDS-3124?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] runzhiwang updated HDDS-3124: - Attachment: screenshot-3.png > Time interval calculate error > -- > >

[jira] [Updated] (HDDS-3124) Time interval calculate error

[ https://issues.apache.org/jira/browse/HDDS-3124?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] runzhiwang updated HDDS-3124: - Description: !screenshot-2.png! (was: !screenshot-1.png! ) > Time interval calculate error >

[jira] [Updated] (HDDS-3124) Time interval calculate error

[ https://issues.apache.org/jira/browse/HDDS-3124?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] runzhiwang updated HDDS-3124: - Attachment: screenshot-2.png > Time interval calculate error > -- > >

[jira] [Updated] (HDDS-3124) Time interval calculate error

[ https://issues.apache.org/jira/browse/HDDS-3124?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] runzhiwang updated HDDS-3124: - Attachment: screenshot-1.png > Time interval calculate error > -- > >

[jira] [Updated] (HDDS-3124) Time interval calculate error

[ https://issues.apache.org/jira/browse/HDDS-3124?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] runzhiwang updated HDDS-3124: - Description: !screenshot-1.png! (was: !image-2020-03-04-09-45-36-083.png! !image-2020-03-04-09-45-59

[jira] [Created] (HDDS-3124) Time interval calculate error

runzhiwang created HDDS-3124: Summary: Time interval calculate error Key: HDDS-3124 URL: https://issues.apache.org/jira/browse/HDDS-3124 Project: Hadoop Distributed Data Store Issue Type: Bug

[jira] [Created] (HDDS-3122) Fail to destroy pipeline in k8s when redeploy DataNode

runzhiwang created HDDS-3122: Summary: Fail to destroy pipeline in k8s when redeploy DataNode Key: HDDS-3122 URL: https://issues.apache.org/jira/browse/HDDS-3122 Project: Hadoop Distributed Data Store

[jira] [Commented] (HDDS-3122) Fail to destroy pipeline in k8s when redeploy DataNode

[ https://issues.apache.org/jira/browse/HDDS-3122?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17049841#comment-17049841 ] runzhiwang commented on HDDS-3122: -- I'm working on it. > Fail to destroy pipeline in k8s

[jira] [Commented] (HDDS-1933) Datanode should use hostname in place of ip addresses to allow DN's to work when ipaddress change

[ https://issues.apache.org/jira/browse/HDDS-1933?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17049773#comment-17049773 ] runzhiwang commented on HDDS-1933: -- I'm working on it > Datanode should use hostname in

[jira] [Commented] (HDDS-1933) Datanode should use hostname in place of ip addresses to allow DN's to work when ipaddress change

[ https://issues.apache.org/jira/browse/HDDS-1933?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17049139#comment-17049139 ] runzhiwang commented on HDDS-1933: -- [~msingh] Hi, I have set "dfs.datanode.use.datanode.h

[jira] [Commented] (HDDS-2821) Use datanode IP or host in log to improve readability

[ https://issues.apache.org/jira/browse/HDDS-2821?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17012479#comment-17012479 ] runzhiwang commented on HDDS-2821: -- I'm working on it. > Use datanode IP or host in log

[jira] [Updated] (HDDS-2819) Timeout threshold is too small to exit Saftmode when security enabled

[ https://issues.apache.org/jira/browse/HDDS-2819?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] runzhiwang updated HDDS-2819: - Description: When I run ozone-0.5.0-SNAPSHOT/compose/ozonesecure/test.sh on computer with 8 core 1999.971

<    1   2   3   4   5   6   7   >