[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

[jira] [Comment Edited] (HDDS-3167) Support different replication factor for CLOSED Container

[ https://issues.apache.org/jira/browse/HDDS-3167?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17058372#comment-17058372 ] Siddharth Wagle edited comment on HDDS-3167 at 3/13/20, 2:50 AM: - Wouldn't

[jira] [Commented] (HDDS-3167) Support different replication factor for CLOSED Container

[ https://issues.apache.org/jira/browse/HDDS-3167?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17058372#comment-17058372 ] Siddharth Wagle commented on HDDS-3167: --- Wouldn't such a setting make sense at a directory level if

[jira] [Updated] (HDDS-3167) Support different replication factor for CLOSED Container

[ https://issues.apache.org/jira/browse/HDDS-3167?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sammi Chen updated HDDS-3167: - Description: For open container, it's replication is decided by Ratis pipeline number size. For closed

[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

[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

[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=17058369#comment-17058369 ] runzhiwang commented on HDDS-3171: -- I'm working on it. > Couldn't create RpcClient protocol exception on

[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=17058305#comment-17058305 ] runzhiwang commented on HDDS-1933: -- [~swagle] Okay, I see. I will check the code and find out how to make

[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=17058304#comment-17058304 ] Siddharth Wagle edited comment on HDDS-1933 at 3/13/20, 12:03 AM: --

[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=17058304#comment-17058304 ] Siddharth Wagle edited comment on HDDS-1933 at 3/13/20, 12:03 AM: --

[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=17058304#comment-17058304 ] Siddharth Wagle commented on HDDS-1933: --- DatanodeDetails are identified by unique UUID already, the

[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=17058302#comment-17058302 ] runzhiwang commented on HDDS-1933: -- [~swagle] Hi, I'm sorry, but what do you mean "making a change so

[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=17058301#comment-17058301 ] Siddharth Wagle commented on HDDS-1933: --- [~yjxxtd] are you making a change so that this config is

[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=17058297#comment-17058297 ] runzhiwang commented on HDDS-1933: -- [~swagle] set dfs.datanode.use.datanode.hostname cannot work. The

[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=17058274#comment-17058274 ] Siddharth Wagle commented on HDDS-1933: --- [~adoroszlai] But what if you set

[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=17058268#comment-17058268 ] Attila Doroszlai commented on HDDS-1933: Setting {{dfs.datanode.use.datanode.hostname=true}} is

[jira] [Resolved] (HDDS-1874) Describe how ozoneManagerDoubleBuffer works in ascii art in code

[ https://issues.apache.org/jira/browse/HDDS-1874?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arpit Agarwal resolved HDDS-1874. - Resolution: Won't Fix Let's work on getting some HA docs up as part of the included

[jira] [Updated] (HDDS-1746) Allocating Blocks is not happening for Multipart upload part key in createMultipartKey call

[ https://issues.apache.org/jira/browse/HDDS-1746?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arpit Agarwal updated HDDS-1746: Priority: Minor (was: Blocker) > Allocating Blocks is not happening for Multipart upload part key

[jira] [Updated] (HDDS-2698) Document OM HA Configuration

[ https://issues.apache.org/jira/browse/HDDS-2698?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arpit Agarwal updated HDDS-2698: Priority: Blocker (was: Major) > Document OM HA Configuration > > >

[jira] [Updated] (HDDS-1995) Generate renewTime on OMLeader for GetDelegationToken

[ https://issues.apache.org/jira/browse/HDDS-1995?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arpit Agarwal updated HDDS-1995: Priority: Blocker (was: Major) > Generate renewTime on OMLeader for GetDelegationToken >

[jira] [Updated] (HDDS-505) OzoneManager HA

[ https://issues.apache.org/jira/browse/HDDS-505?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arpit Agarwal updated HDDS-505: --- Component/s: Ozone Manager HA > OzoneManager HA > --- > >

[jira] [Updated] (HDDS-3137) OM RpcClient fail with java.lang.IllegalArgumentException

[ https://issues.apache.org/jira/browse/HDDS-3137?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arpit Agarwal updated HDDS-3137: Component/s: HA > OM RpcClient fail with java.lang.IllegalArgumentException >

[jira] [Updated] (HDDS-2980) Delete replayed entry from OpenKeyTable during commit

[ https://issues.apache.org/jira/browse/HDDS-2980?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arpit Agarwal updated HDDS-2980: Component/s: HA > Delete replayed entry from OpenKeyTable during commit >

[jira] [Created] (HDDS-3170) File count by size task does not handle OM Key DELETE operation correctly.

Aravindan Vijayan created HDDS-3170: --- Summary: File count by size task does not handle OM Key DELETE operation correctly. Key: HDDS-3170 URL: https://issues.apache.org/jira/browse/HDDS-3170

[jira] [Assigned] (HDDS-3164) Add Recon endpoint to serve missing containers along with keys that were present in them.

[ https://issues.apache.org/jira/browse/HDDS-3164?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vivek Ratnavel Subramanian reassigned HDDS-3164: Assignee: Vivek Ratnavel Subramanian > Add Recon endpoint to serve

[jira] [Resolved] (HDDS-3169) Revert Recon config key change for HTTP Server keytab.

[ https://issues.apache.org/jira/browse/HDDS-3169?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Aravindan Vijayan resolved HDDS-3169. - Resolution: Fixed PR merged. > Revert Recon config key change for HTTP Server keytab. >

[GitHub] [hadoop-ozone] avijayanhwx commented on issue #670: HDDS-3169. Revert Recon config key change for HTTP Server keytab.

avijayanhwx commented on issue #670: HDDS-3169. Revert Recon config key change for HTTP Server keytab. URL: https://github.com/apache/hadoop-ozone/pull/670#issuecomment-598338057 Thank you for the reviews @arp7 & @mukul1987.

[GitHub] [hadoop-ozone] avijayanhwx merged pull request #670: HDDS-3169. Revert Recon config key change for HTTP Server keytab.

avijayanhwx merged pull request #670: HDDS-3169. Revert Recon config key change for HTTP Server keytab. URL: https://github.com/apache/hadoop-ozone/pull/670 This is an automated message from the Apache Git Service. To

[jira] [Assigned] (HDDS-3086) Failure running integration test it-freon

[ https://issues.apache.org/jira/browse/HDDS-3086?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shashikant Banerjee reassigned HDDS-3086: - Assignee: Shashikant Banerjee (was: Siddharth Wagle) > Failure running

[GitHub] [hadoop-ozone] avijayanhwx commented on issue #670: HDDS-3169. Revert Recon config key change for HTTP Server keytab.

avijayanhwx commented on issue #670: HDDS-3169. Revert Recon config key change for HTTP Server keytab. URL: https://github.com/apache/hadoop-ozone/pull/670#issuecomment-598296519 cc @vivekratnavel This is an automated

[jira] [Updated] (HDDS-3169) Revert Recon config key change for HTTP Server keytab.

[ https://issues.apache.org/jira/browse/HDDS-3169?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated HDDS-3169: - Labels: pull-request-available (was: ) > Revert Recon config key change for HTTP Server keytab.

[GitHub] [hadoop-ozone] avijayanhwx opened a new pull request #670: HDDS-3169. Revert Recon config key change for HTTP Server keytab.

avijayanhwx opened a new pull request #670: HDDS-3169. Revert Recon config key change for HTTP Server keytab. URL: https://github.com/apache/hadoop-ozone/pull/670 ## What changes were proposed in this pull request? There was a recent change to the config key used by Recon's HTTP server

[jira] [Created] (HDDS-3169) Revert Recon config key change for HTTP Server keytab.

Aravindan Vijayan created HDDS-3169: --- Summary: Revert Recon config key change for HTTP Server keytab. Key: HDDS-3169 URL: https://issues.apache.org/jira/browse/HDDS-3169 Project: Hadoop Distributed

[GitHub] [hadoop-ozone] cku328 opened a new pull request #669: HDDS-3144. Fixed failed test case.

cku328 opened a new pull request #669: HDDS-3144. Fixed failed test case. URL: https://github.com/apache/hadoop-ozone/pull/669 ## What changes were proposed in this pull request? I use the debugger to get a log string that calls the

[jira] [Updated] (HDDS-3144) LogSubcommandTest fails

[ https://issues.apache.org/jira/browse/HDDS-3144?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated HDDS-3144: - Labels: pull-request-available (was: ) > LogSubcommandTest fails > --- > >

[jira] [Assigned] (HDDS-3023) Create Freon test to test isolated Ratis LEADER

[ https://issues.apache.org/jira/browse/HDDS-3023?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Attila Doroszlai reassigned HDDS-3023: -- Assignee: Marton Elek > Create Freon test to test isolated Ratis LEADER >

[jira] [Assigned] (HDDS-3042) Support running full Ratis pipeline from IDE (IntelliJ)

[ https://issues.apache.org/jira/browse/HDDS-3042?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Attila Doroszlai reassigned HDDS-3042: -- Assignee: Marton Elek > Support running full Ratis pipeline from IDE (IntelliJ) >

[jira] [Resolved] (HDDS-3114) Implement background block-file closing thread

[ https://issues.apache.org/jira/browse/HDDS-3114?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Attila Doroszlai resolved HDDS-3114. Resolution: Won't Do Changed the map to a Guava cache with expiry. > Implement background

[jira] [Commented] (HDDS-3086) Failure running integration test it-freon

[ https://issues.apache.org/jira/browse/HDDS-3086?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17057887#comment-17057887 ] Attila Doroszlai commented on HDDS-3086: [~shashikant], I think for cid=142, it tried different

[jira] [Comment Edited] (HDDS-3086) Failure running integration test it-freon

[ https://issues.apache.org/jira/browse/HDDS-3086?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17057833#comment-17057833 ] Shashikant Banerjee edited comment on HDDS-3086 at 3/12/20, 12:16 PM: --

[jira] [Comment Edited] (HDDS-3086) Failure running integration test it-freon

[ https://issues.apache.org/jira/browse/HDDS-3086?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17057833#comment-17057833 ] Shashikant Banerjee edited comment on HDDS-3086 at 3/12/20, 12:15 PM: --

[jira] [Comment Edited] (HDDS-3086) Failure running integration test it-freon

[ https://issues.apache.org/jira/browse/HDDS-3086?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17057833#comment-17057833 ] Shashikant Banerjee edited comment on HDDS-3086 at 3/12/20, 12:00 PM: --

[jira] [Assigned] (HDDS-3086) Failure running integration test it-freon

[ https://issues.apache.org/jira/browse/HDDS-3086?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shashikant Banerjee reassigned HDDS-3086: - Assignee: Siddharth Wagle (was: Shashikant Banerjee) > Failure running

[jira] [Comment Edited] (HDDS-3086) Failure running integration test it-freon

[ https://issues.apache.org/jira/browse/HDDS-3086?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17057833#comment-17057833 ] Shashikant Banerjee edited comment on HDDS-3086 at 3/12/20, 12:00 PM: --

[jira] [Comment Edited] (HDDS-3086) Failure running integration test it-freon

[ https://issues.apache.org/jira/browse/HDDS-3086?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17057833#comment-17057833 ] Shashikant Banerjee edited comment on HDDS-3086 at 3/12/20, 11:59 AM: --

[jira] [Comment Edited] (HDDS-3086) Failure running integration test it-freon

[ https://issues.apache.org/jira/browse/HDDS-3086?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17057833#comment-17057833 ] Shashikant Banerjee edited comment on HDDS-3086 at 3/12/20, 11:35 AM: --

[jira] [Commented] (HDDS-3086) Failure running integration test it-freon

[ https://issues.apache.org/jira/browse/HDDS-3086?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17057833#comment-17057833 ] Shashikant Banerjee commented on HDDS-3086: --- 2020-02-27 14:50:15,865 [Thread-1361] INFO

[GitHub] [hadoop-ozone] bshashikant commented on issue #366: HDDS-2753. Test OM Volume and Bucket operations are idempotent.

bshashikant commented on issue #366: HDDS-2753. Test OM Volume and Bucket operations are idempotent. URL: https://github.com/apache/hadoop-ozone/pull/366#issuecomment-598132996 Thanks @hanishakoneru for working on this. Instead of exposing a public API to force set last AppliedTermIndex

[jira] [Comment Edited] (HDDS-3167) Support different replication factor for CLOSED Container

[ https://issues.apache.org/jira/browse/HDDS-3167?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17057818#comment-17057818 ] Marton Elek edited comment on HDDS-3167 at 3/12/20, 11:09 AM: -- Thanks to open

[jira] [Commented] (HDDS-3167) Support different replication factor for CLOSED Container

[ https://issues.apache.org/jira/browse/HDDS-3167?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17057818#comment-17057818 ] Marton Elek commented on HDDS-3167: --- How would you like to decide the replication factor for a specific

[jira] [Comment Edited] (HDDS-3155) Improved ozone client flush implementation to make it faster.

[ https://issues.apache.org/jira/browse/HDDS-3155?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17057814#comment-17057814 ] mingchao zhao edited comment on HDDS-3155 at 3/12/20, 11:06 AM: Hi [~elek]

[jira] [Commented] (HDDS-3155) Improved ozone client flush implementation to make it faster.

[ https://issues.apache.org/jira/browse/HDDS-3155?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17057814#comment-17057814 ] mingchao zhao commented on HDDS-3155: - Hi [~elek] [~shashikant] [~msingh] very thanks for your

[jira] [Updated] (HDDS-3086) Failure running integration test it-freon

[ https://issues.apache.org/jira/browse/HDDS-3086?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Attila Doroszlai updated HDDS-3086: --- Attachment: org.apache.hadoop.fs.ozone.contract.ITestOzoneContractDistCp-output.txt >

[jira] [Updated] (HDDS-3155) Improved ozone client flush implementation to make it faster.

[ https://issues.apache.org/jira/browse/HDDS-3155?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] mingchao zhao updated HDDS-3155: Attachment: image-2020-03-12-17-47-57-770.png > Improved ozone client flush implementation to make

[jira] [Updated] (HDDS-3155) Improved ozone client flush implementation to make it faster.

[ https://issues.apache.org/jira/browse/HDDS-3155?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] mingchao zhao updated HDDS-3155: Attachment: image-2020-03-12-16-48-08-391.png > Improved ozone client flush implementation to make

[GitHub] [hadoop-ozone] timmylicheng commented on a change in pull request #663: HDDS-3156 update allocateContainer to remove additional createPipeline step.

timmylicheng commented on a change in pull request #663: HDDS-3156 update allocateContainer to remove additional createPipeline step. URL: https://github.com/apache/hadoop-ozone/pull/663#discussion_r391472796 ## File path:

[jira] [Commented] (HDDS-3116) Datanode sometimes fails to start with NPE when starting Ratis xceiver server

[ https://issues.apache.org/jira/browse/HDDS-3116?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17057707#comment-17057707 ] Attila Doroszlai commented on HDDS-3116: Committed to master. [~dineshchitlangia] please resolve

[jira] [Updated] (HDDS-3116) Datanode sometimes fails to start with NPE when starting Ratis xceiver server

[ https://issues.apache.org/jira/browse/HDDS-3116?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Attila Doroszlai updated HDDS-3116: --- Fix Version/s: 0.6.0 > Datanode sometimes fails to start with NPE when starting Ratis xceiver

[jira] [Updated] (HDDS-3116) Datanode sometimes fails to start with NPE when starting Ratis xceiver server

[ https://issues.apache.org/jira/browse/HDDS-3116?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Attila Doroszlai updated HDDS-3116: --- Labels: (was: pull-request-available) > Datanode sometimes fails to start with NPE when

[GitHub] [hadoop-ozone] adoroszlai merged pull request #630: HDDS-3116. Datanode sometimes fails to start with NPE when starting Ratis xceiver server

adoroszlai merged pull request #630: HDDS-3116. Datanode sometimes fails to start with NPE when starting Ratis xceiver server URL: https://github.com/apache/hadoop-ozone/pull/630 This is an automated message from the Apache

[GitHub] [hadoop-ozone] bshashikant commented on issue #556: HDDS-3018. Fix TestContainerStateMachineFailures.java

bshashikant commented on issue #556: HDDS-3018. Fix TestContainerStateMachineFailures.java URL: https://github.com/apache/hadoop-ozone/pull/556#issuecomment-598058629 Thanks @timmylicheng . I think the problem seems to be arising out a race condition of sort. By the time, allocateBlock

[GitHub] [hadoop-ozone] timmylicheng commented on issue #556: HDDS-3018. Fix TestContainerStateMachineFailures.java

timmylicheng commented on issue #556: HDDS-3018. Fix TestContainerStateMachineFailures.java URL: https://github.com/apache/hadoop-ozone/pull/556#issuecomment-598048976 @bshashikant After multi-raft change, Ratis pipline (ONE or THREE) are created by BackgroundPipelineCreator and when auto

[jira] [Updated] (HDDS-3139) Pipeline placement should select lowest load datanode as anchor

[ https://issues.apache.org/jira/browse/HDDS-3139?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] ASF GitHub Bot updated HDDS-3139: - Labels: pull-request-available (was: ) > Pipeline placement should select lowest load datanode

[GitHub] [hadoop-ozone] timmylicheng opened a new pull request #668: HDDS-3139 Pipeline placement should max out pipeline usage

timmylicheng opened a new pull request #668: HDDS-3139 Pipeline placement should max out pipeline usage URL: https://github.com/apache/hadoop-ozone/pull/668 ## What changes were proposed in this pull request? Pipeline placement should select lowest load datanode as anchor.