HDDS-9807. Consider volume committed space when checking if datanode can host new container #5721

vtutrinov · 2023-12-04T10:39:10Z

What changes were proposed in this pull request?

The algorithm of detection of the datanode availability for a new container was different between the SCM and datanodes in case of EC buckets. The SCM doesn't take into account the committed bytes count and serves the client with an invalid pipeline and then the datanodes from the provided pipeline will fail to create new containers

The PR proposes a common way of computing the datanode availability for a new container allocation

What is the link to the Apache JIRA

https://issues.apache.org/jira/browse/HDDS-9807

How was this patch tested?

manually in a way described in the jira ticket,
new unit test that checks the datanode is not available to allocate a new container in case of increasing committed bytes count

adoroszlai · 2023-12-04T12:39:21Z

@xichen01 please take a look

xichen01 · 2023-12-05T12:13:52Z

...in/java/org/apache/hadoop/ozone/container/common/interfaces/StorageLocationReportMXBean.java


  long getScmUsed();

  long getRemaining();


@vtutrinov @adoroszlai
What is the definition of remaining, I noticed that remaining is actually Volume available. available=capacity - reserved - used.

So does committed have to be reported to the SCM separately.

Or is it added to remaining, which is defined as the amount of space on the Volume that is guaranteed to be available for data storage? available=capacity - reserved - used - commited.
We use available in a lot of places, and it seems like we should take commited into available.

ozone/hadoop-hdds/container-service/src/main/java/org/apache/hadoop/ozone/container/common/volume/MutableVolumeSet.java

Line 473 in 9b3d045

remaining = volumeInfo.get().getAvailable();

seems it makes sense, I will try to check the approach

@xichen01
I've pushed a new commit with the proposed approach and the build is green, as such as the manual test from the jira ticket. But I'm concerned about the datanode storage metrics (output of the ozone admin datanode usageinfo command) and recon's reports - from the user's perspective it will seen contr ordinal:

I've written a 200KiB key to the EC-bucket with rs-6-3-1024k replication (the cluster has 10 datanodes with 2Gb storages mounted to /data)

datanodes report before the key was written:

Usage Information (1 Datanodes) UUID : 8ac06e73-a434-4fd3-9be5-bc271b8f6bf7 IP Address : 172.23.0.15 Hostname : ozone-datanode10-1.ozone_default Capacity : 2147483648 B (2 GB) Total Used : 31571968 B (30.11 MB) Total Used % : 1.47% Ozone Used : 0 B (0 B) Ozone Used % : 0.00% Remaining : 2115911680 B (1.97 GB) Remaining % : 98.53% Container(s) : 0 Usage Information (1 Datanodes) UUID : 9e3bf76a-8c98-4fa3-b034-c68973d7560b IP Address : 172.23.0.10 Hostname : ozone-datanode3-1.ozone_default Capacity : 2147483648 B (2 GB) Total Used : 31571968 B (30.11 MB) Total Used % : 1.47% Ozone Used : 0 B (0 B) Ozone Used % : 0.00% Remaining : 2115911680 B (1.97 GB) Remaining % : 98.53% Container(s) : 0 Usage Information (1 Datanodes) UUID : a5df4b7d-92b3-407a-b56d-aaeb924f0cd6 IP Address : 172.23.0.7 Hostname : ozone-datanode2-1.ozone_default Capacity : 2147483648 B (2 GB) Total Used : 27365376 B (26.10 MB) Total Used % : 1.27% Ozone Used : 0 B (0 B) Ozone Used % : 0.00% Remaining : 2120118272 B (1.97 GB) Remaining % : 98.73% Container(s) : 0 Usage Information (1 Datanodes) UUID : e5a630fc-ce77-4211-89dc-15ab0ca67fde IP Address : 172.23.0.6 Hostname : ozone-datanode8-1.ozone_default Capacity : 2147483648 B (2 GB) Total Used : 31571968 B (30.11 MB) Total Used % : 1.47% Ozone Used : 0 B (0 B) Ozone Used % : 0.00% Remaining : 2115911680 B (1.97 GB) Remaining % : 98.53% Container(s) : 0 Usage Information (1 Datanodes) UUID : 2d00f163-7f22-4395-b82b-e8353c74698b IP Address : 172.23.0.5 Hostname : ozone-datanode7-1.ozone_default Capacity : 2147483648 B (2 GB) Total Used : 31571968 B (30.11 MB) Total Used % : 1.47% Ozone Used : 0 B (0 B) Ozone Used % : 0.00% Remaining : 2115911680 B (1.97 GB) Remaining % : 98.53% Container(s) : 0 Usage Information (1 Datanodes) UUID : 3a22dc09-acc5-4270-8007-135056031ed9 IP Address : 172.23.0.12 Hostname : ozone-datanode9-1.ozone_default Capacity : 2147483648 B (2 GB) Total Used : 31571968 B (30.11 MB) Total Used % : 1.47% Ozone Used : 0 B (0 B) Ozone Used % : 0.00% Remaining : 2115911680 B (1.97 GB) Remaining % : 98.53% Container(s) : 0 Usage Information (1 Datanodes) UUID : 4478a423-0416-429e-b41c-5e58b8ec7ed5 IP Address : 172.23.0.16 Hostname : ozone-datanode5-1.ozone_default Capacity : 2147483648 B (2 GB) Total Used : 31571968 B (30.11 MB) Total Used % : 1.47% Ozone Used : 0 B (0 B) Ozone Used % : 0.00% Remaining : 2115911680 B (1.97 GB) Remaining % : 98.53% Container(s) : 0 Usage Information (1 Datanodes) UUID : 5ffda4af-e5dd-4b11-a945-7fef0b53356b IP Address : 172.23.0.17 Hostname : ozone-datanode1-1.ozone_default Capacity : 2147483648 B (2 GB) Total Used : 31571968 B (30.11 MB) Total Used % : 1.47% Ozone Used : 0 B (0 B) Ozone Used % : 0.00% Remaining : 2115911680 B (1.97 GB) Remaining % : 98.53% Container(s) : 0 Usage Information (1 Datanodes) UUID : 6fe5b830-5031-4a4c-a8fa-ae909c55d187 IP Address : 172.23.0.3 Hostname : ozone-datanode6-1.ozone_default Capacity : 2147483648 B (2 GB) Total Used : 31571968 B (30.11 MB) Total Used % : 1.47% Ozone Used : 0 B (0 B) Ozone Used % : 0.00% Remaining : 2115911680 B (1.97 GB) Remaining % : 98.53% Container(s) : 0 Usage Information (1 Datanodes) UUID : 7ce23e7c-41bf-4c5e-aea7-63af06049ad0 IP Address : 172.23.0.19 Hostname : ozone-datanode4-1.ozone_default Capacity : 2147483648 B (2 GB) Total Used : 31571968 B (30.11 MB) Total Used % : 1.47% Ozone Used : 0 B (0 B) Ozone Used % : 0.00% Remaining : 2115911680 B (1.97 GB) Remaining % : 98.53% Container(s) : 0

datanode report after the key was written:

Usage Information (1 Datanodes) UUID : 8ac06e73-a434-4fd3-9be5-bc271b8f6bf7 IP Address : 172.23.0.15 Hostname : ozone-datanode10-1.ozone_default Capacity : 2147483648 B (2 GB) Total Used : 1252982784 B (1.17 GB) Total Used % : 58.35% Ozone Used : 0 B (0 B) Ozone Used % : 0.00% Remaining : 894500864 B (853.06 MB) Remaining % : 41.65% Container(s) : 1 Usage Information (1 Datanodes) UUID : 9e3bf76a-8c98-4fa3-b034-c68973d7560b IP Address : 172.23.0.10 Hostname : ozone-datanode3-1.ozone_default Capacity : 2147483648 B (2 GB) Total Used : 1252982784 B (1.17 GB) Total Used % : 58.35% Ozone Used : 0 B (0 B) Ozone Used % : 0.00% Remaining : 894500864 B (853.06 MB) Remaining % : 41.65% Container(s) : 1 Usage Information (1 Datanodes) UUID : a5df4b7d-92b3-407a-b56d-aaeb924f0cd6 IP Address : 172.23.0.7 Hostname : ozone-datanode2-1.ozone_default Capacity : 2147483648 B (2 GB) Total Used : 1248776192 B (1.16 GB) Total Used % : 58.15% Ozone Used : 204800 B (200 KB) Ozone Used % : 0.01% Remaining : 898707456 B (857.07 MB) Remaining % : 41.85% Container(s) : 1 Usage Information (1 Datanodes) UUID : e5a630fc-ce77-4211-89dc-15ab0ca67fde IP Address : 172.23.0.6 Hostname : ozone-datanode8-1.ozone_default Capacity : 2147483648 B (2 GB) Total Used : 31596544 B (30.13 MB) Total Used % : 1.47% Ozone Used : 0 B (0 B) Ozone Used % : 0.00% Remaining : 2115887104 B (1.97 GB) Remaining % : 98.53% Container(s) : 0 Usage Information (1 Datanodes) UUID : 2d00f163-7f22-4395-b82b-e8353c74698b IP Address : 172.23.0.5 Hostname : ozone-datanode7-1.ozone_default Capacity : 2147483648 B (2 GB) Total Used : 1252982784 B (1.17 GB) Total Used % : 58.35% Ozone Used : 204800 B (200 KB) Ozone Used % : 0.01% Remaining : 894500864 B (853.06 MB) Remaining % : 41.65% Container(s) : 1 Usage Information (1 Datanodes) UUID : 3a22dc09-acc5-4270-8007-135056031ed9 IP Address : 172.23.0.12 Hostname : ozone-datanode9-1.ozone_default Capacity : 2147483648 B (2 GB) Total Used : 1252982784 B (1.17 GB) Total Used % : 58.35% Ozone Used : 0 B (0 B) Ozone Used % : 0.00% Remaining : 894500864 B (853.06 MB) Remaining % : 41.65% Container(s) : 1 Usage Information (1 Datanodes) UUID : 4478a423-0416-429e-b41c-5e58b8ec7ed5 IP Address : 172.23.0.16 Hostname : ozone-datanode5-1.ozone_default Capacity : 2147483648 B (2 GB) Total Used : 1252982784 B (1.17 GB) Total Used % : 58.35% Ozone Used : 0 B (0 B) Ozone Used % : 0.00% Remaining : 894500864 B (853.06 MB) Remaining % : 41.65% Container(s) : 1 Usage Information (1 Datanodes) UUID : 5ffda4af-e5dd-4b11-a945-7fef0b53356b IP Address : 172.23.0.17 Hostname : ozone-datanode1-1.ozone_default Capacity : 2147483648 B (2 GB) Total Used : 1252982784 B (1.17 GB) Total Used % : 58.35% Ozone Used : 204800 B (200 KB) Ozone Used % : 0.01% Remaining : 894500864 B (853.06 MB) Remaining % : 41.65% Container(s) : 1 Usage Information (1 Datanodes) UUID : 6fe5b830-5031-4a4c-a8fa-ae909c55d187 IP Address : 172.23.0.3 Hostname : ozone-datanode6-1.ozone_default Capacity : 2147483648 B (2 GB) Total Used : 1252982784 B (1.17 GB) Total Used % : 58.35% Ozone Used : 204800 B (200 KB) Ozone Used % : 0.01% Remaining : 894500864 B (853.06 MB) Remaining % : 41.65% Container(s) : 1 Usage Information (1 Datanodes) UUID : 7ce23e7c-41bf-4c5e-aea7-63af06049ad0 IP Address : 172.23.0.19 Hostname : ozone-datanode4-1.ozone_default Capacity : 2147483648 B (2 GB) Total Used : 1252982784 B (1.17 GB) Total Used % : 58.35% Ozone Used : 0 B (0 B) Ozone Used % : 0.00% Remaining : 894500864 B (853.06 MB) Remaining % : 41.65% Container(s) : 1

WHAT ??? 200KiB written key has changed the remaining storage size of 9 datanodes from 1.97GiB to 853MB, looks too strange, doesn't it?
I would report the committed bytes as a separate report data field as the remaining storage size will be more obvious for the user and the cluster admins

I think this is because we include commited in the remaining, so when a Container is created, the space that the Container might use will be deducted from the remaining.

If we don't include commited in the remaining, the problem is that the datanode list command shows that there is enough space remaining to create a Container, but in reality it is not possible to create a new Container, because inside the Datanode, the creation of a Container has to take into account commited.

Exactly, and that's why I would provide the committed bytes count in reports (e.g. in datanode heartbeat requests, datanode usageifo or in datanode list cli commands) as a separate field and don't mix it with the remaining bytes count (Devide et impera policy :) )

Yes, it looks like your initial solution is the more appropriate choice.

…ailability as on datanode to allocate a new container

… providing the committed bytes metric separately

…stead of providing the committed bytes metric separately" This reverts commit cfcc024.

…port and datanode usageinfo

xichen01

@vtutrinov. The patch looks good, there are only a few Comments you can refer to.

xichen01 · 2023-12-08T15:59:18Z

...p-hdds/server-scm/src/test/java/org/apache/hadoop/hdds/scm/TestSCMCommonPlacementPolicy.java

+    when(confing.getStorageSize(eq(HDDS_DATANODE_VOLUME_MIN_FREE_SPACE),
+            eq(HDDS_DATANODE_VOLUME_MIN_FREE_SPACE_DEFAULT),
+            eq(StorageUnit.BYTES))).thenReturn(100000.0);
+    UUID datanodeUuid = spy(UUID.randomUUID());


spy Is it necessary for UUID?

no, it isn't, fixed

xichen01 · 2023-12-08T15:59:20Z

...p-hdds/server-scm/src/test/java/org/apache/hadoop/hdds/scm/TestSCMCommonPlacementPolicy.java

+    when(datanodeInfo.getNodeStatus()).thenReturn(nodeStatus);
+    when(nodeMngr.getNodeByUuid(eq(datanodeUuid))).thenReturn(datanodeInfo);
+
+    StorageContainerDatanodeProtocolProtos.StorageReportProto storageReport1 =


nit: can consider using the org.apache.hadoop.hdds.scm.HddsTestUtils#createStorageReport

xichen01 · 2023-12-08T15:59:26Z

...p-hdds/server-scm/src/test/java/org/apache/hadoop/hdds/scm/TestSCMCommonPlacementPolicy.java

+        .thenReturn(Collections.singletonList(metaReport));
+
+
+    // 500 committed bytes


nit: It would be good to comment on the process of calculating.

xichen01 · 2023-12-08T15:59:29Z

...p-hdds/server-scm/src/test/java/org/apache/hadoop/hdds/scm/TestSCMCommonPlacementPolicy.java

+
+
+    // 500 committed bytes
+    assertTrue(placementPolicy.isValidNode(datanodeDetails, 100, 4000));


nit: can directly use hasEnoughSpace to assert

I don't agree that it would be correct. We check the placement policy's behavior here and its implementations (e.g. org.apache.hadoop.hdds.scm.container.placement.algorithms.SCMContainerPlacementRackScatter) use isValid method to check the datanode availability

xichen01 · 2023-12-08T15:59:38Z

...vice/src/main/java/org/apache/hadoop/ozone/container/common/volume/AvailableSpaceFilter.java

        ", volumes: " + fullVolumes;
  }

+  public static boolean hasVolumeEnoughSpace(long volumeCapacity,


Can put it into VolumeUsage, just like getMinVolumeFreeSpace

xichen01 · 2023-12-08T16:18:17Z

hadoop-hdds/server-scm/src/main/java/org/apache/hadoop/hdds/scm/SCMCommonPlacementPolicy.java

-        if (reportProto.getRemaining() > dataSizeRequired) {
+        if (hasVolumeEnoughSpace(reportProto.getCapacity(),
+            reportProto.getRemaining(), reportProto.getCommitted(),
+            dataSizeRequired, conf)) {


The configuration used in getMinVolumeFreeSpace is the Datanode configuration, what if the configuration is different for different Datanodes or not available in SCM?
Maybe volumeFreeSpaceToSpare should also report

xichen01 · 2023-12-08T16:18:42Z

...op-hdds/tools/src/main/java/org/apache/hadoop/hdds/scm/cli/datanode/UsageInfoSubcommand.java

        + " B", StringUtils.byteDesc(info.getRemaining()));
    System.out.printf("%-13s: %s %n", "Remaining %",
        PERCENT_FORMAT.format(info.getRemainingRatio()));
+    System.out.printf("%-13s: %s (%s) %n", "Committed", info.getCommitted()


Committed doesn't seem to be easy to understand outside of the code context, suggesting: Container Preallocated.
And add a Remaining Allocatable (remaining - commited)

…t, tiny changes in test to check datanode availability depending on committed bytes count

adoroszlai · 2023-12-10T08:06:02Z

Thanks @vtutrinov for updating the patch. There is a test failure in TestSCMCommonPlacementPolicy.testDatanodeIsInvalidInCaseOfIncreasingCommittedBytes: https://github.com/vtutrinov/ozone/actions/runs/7156214054/job/19485712139#step:5:1750

…not relevant anymore)

vtutrinov · 2023-12-10T08:44:04Z

Thanks @vtutrinov for updating the patch. There is a test failure in TestSCMCommonPlacementPolicy.testDatanodeIsInvalidInCaseOfIncreasingCommittedBytes: https://github.com/vtutrinov/ozone/actions/runs/7156214054/job/19485712139#step:5:1750

Fixed

xichen01 · 2023-12-10T16:48:08Z

@vtutrinov The patch looks good.
The only thing we might want to consider at this point is FreeSpaceToSpare. Requires the "remaining allocatable space" greater than FreeSpaceToSpare when create a new Container, so maybe we should add that to the output of the UsageInfo command as well, what do you think?

vtutrinov · 2023-12-11T06:29:17Z

@vtutrinov The patch looks good. The only thing we might want to consider at this point is FreeSpaceToSpare. Requires the "remaining allocatable space" greater than FreeSpaceToSpare when create a new Container, so maybe we should add that to the output of the UsageInfo command as well, what do you think?

Yep, it makes sense, I will do
UPD: done

sumitagrawl

@vtutrinov Thanks for working over this, overall LGTM

sumitagrawl · 2023-12-11T09:00:20Z

...vice/src/main/java/org/apache/hadoop/ozone/container/common/volume/AvailableSpaceFilter.java

    long committed = vol.getCommittedBytes();
    long available = free - committed;
-    long volumeFreeSpace =
+    long volumeFreeSpaceTpSpare =


nit: spelling incorrect, volumeFreeSpaceToSpare

…e usageinfo command output

xichen01 · 2023-12-11T10:30:22Z

...op-hdds/tools/src/main/java/org/apache/hadoop/hdds/scm/cli/datanode/UsageInfoSubcommand.java

+    System.out.printf("%-13s: %s (%s) %n", "Remaining Allocatable",
+        (info.getRemaining() - info.getCommitted()) + " B",
+        StringUtils.byteDesc((info.getRemaining() - info.getCommitted())));
+    System.out.printf("%-13s: %s (%s) %n", "Free Space To Spare",


We should make this newly added lines aligned
Such as:

//.. Remaining : 4751560704 B (4.43 GB) Remaining % : 45.02% Container Pre-allocated : 0 B (0 B) Remaining Allocatable : 4751560704 B (4.43 GB) Free Space To Spare : 0 B (0 B)

xichen01 · 2023-12-11T14:27:06Z

@vtutrinov Thank for updating the patch. LGTM + 1 .

…ct-algo-to-detect-datanode-availability

adoroszlai · 2023-12-11T14:31:24Z

@aswinshakil @sadanand48 please review

myskov · 2023-12-19T09:17:50Z

@aswinshakil @sadanand48 please review

adoroszlai · 2023-12-20T17:22:28Z

Thanks @vtutrinov for the patch, @sumitagrawl, @xichen01 for the review.

(Since release branch for 1.4 has been cut, we can fix any post-commit comments later, without holding back the upcoming release.)

symious · 2023-12-21T13:58:33Z

@adoroszlai Could you help to confirm if this PR needs to be cherry-picked to ozone-1.4?

adoroszlai · 2023-12-21T14:33:03Z

@symious @myskov I suggest not including it in 1.4.0, as this had little time to be tested. We can work on a patch release 1.4.1 soon afterwards.

symious · 2023-12-21T14:34:31Z

@adoroszlai Thank you for the confirmation.

szetszwo · 2023-12-29T09:06:17Z

This may cause NPE; see HDDS-10027.

…can host new container (apache#5721) (cherry picked from commit 0e07225)

…can host new container (apache#5721) (cherry picked from commit a74b09e0cdcc7234b883a31e4daea6039788f36d)

…if datanode can host new container (apache#5721) (cherry picked from commit 0e07225) Conflicts: hadoop-hdds/docs/themes/ozonedoc/static/swagger-resources/recon-api.yaml hadoop-ozone/recon/src/test/java/org/apache/hadoop/ozone/recon/api/TestNSSummaryEndpointWithFSO.java hadoop-ozone/recon/src/test/java/org/apache/hadoop/ozone/recon/api/TestNSSummaryEndpointWithLegacy.java

adoroszlai requested review from aswinshakil and sadanand48 December 4, 2023 12:37

adoroszlai changed the title ~~HDDS-9807. Take into account the hdds volume committed bytes on detecting the datanode availability to allocate a new container on SCM side~~ HDDS-9807. Consider volume committed space when checking if datanode can host new container Dec 4, 2023

xichen01 reviewed Dec 5, 2023

View reviewed changes

Slava Tutrinov added 2 commits December 6, 2023 09:39

HDDS-9807. use the same algorithm for SCM to detect an hdds volume av…

72d0d69

…ailability as on datanode to allocate a new container

HDDS-9807. update remaining volume size (- committedBytes) instead of…

cfcc024

… providing the committed bytes metric separately

vtutrinov force-pushed the HDDS-9807-scm-correct-algo-to-detect-datanode-availability branch from b1e2f73 to cfcc024 Compare December 6, 2023 08:53

Slava Tutrinov added 3 commits December 7, 2023 21:34

Revert "HDDS-9807. update remaining volume size (- committedBytes) in…

db1305c

…stead of providing the committed bytes metric separately" This reverts commit cfcc024.

HDDS-9807. add committed storage bytes count to the recon datanode re…

9d8c56d

…port and datanode usageinfo

HDDS-9807. add committed bytes count to volume info metrics

5fe6ceb

xichen01 reviewed Dec 8, 2023

View reviewed changes

HDDS-9807. provide datanode freeSpaceToSpare through heartbeat reques…

59ece8d

…t, tiny changes in test to check datanode availability depending on committed bytes count

HDDS-9807. fix test to check datanode availability (configuration is …

58b6aba

…not relevant anymore)

sumitagrawl reviewed Dec 11, 2023

View reviewed changes

HDDS-9807. add FreeSpaceToSpare datanode volume metric to the datanod…

873aeaf

…e usageinfo command output

xichen01 reviewed Dec 11, 2023

View reviewed changes

HDDS-9807. align datanode usageinfo sub-command output

a6ff69a

vtutrinov force-pushed the HDDS-9807-scm-correct-algo-to-detect-datanode-availability branch from 3b13629 to a6ff69a Compare December 11, 2023 13:00

Merge remote-tracking branch 'origin/master' into HDDS-9807-scm-corre…

529c0cb

…ct-algo-to-detect-datanode-availability

adoroszlai merged commit 0e07225 into apache:master Dec 20, 2023

ivandika3 mentioned this pull request Mar 12, 2024

HDDS-10494. Recon datanode page to support sort by other storage metrics #6350

Closed

xichen01 pushed a commit to xichen01/ozone that referenced this pull request Jul 17, 2024

HDDS-9807. Consider volume committed space when checking if datanode …

62c72bd

…can host new container (apache#5721) (cherry picked from commit 0e07225)

xichen01 pushed a commit to xichen01/ozone that referenced this pull request Jul 17, 2024

HDDS-9807. Consider volume committed space when checking if datanode …

6323ab3

…can host new container (apache#5721) (cherry picked from commit 0e07225)

xichen01 pushed a commit to xichen01/ozone that referenced this pull request Jul 17, 2024

HDDS-9807. Consider volume committed space when checking if datanode …

1999ba7

…can host new container (apache#5721) (cherry picked from commit 0e07225)

xichen01 mentioned this pull request Jul 18, 2024

[DO NOT MERGE] Backport some fixes, performance optimizations from master to ozone-1.4 #6929 #6964

Merged

vtutrinov pushed a commit to vtutrinov/ozone that referenced this pull request Jul 15, 2025

HDDS-9807. Consider volume committed space when checking if datanode …

12b94cd

…can host new container (apache#5721) (cherry picked from commit a74b09e0cdcc7234b883a31e4daea6039788f36d)

		.thenReturn(Collections.singletonList(metaReport));


		// 500 committed bytes



		// 500 committed bytes
		assertTrue(placementPolicy.isValidNode(datanodeDetails, 100, 4000));

HDDS-9807. Consider volume committed space when checking if datanode can host new container #5721

HDDS-9807. Consider volume committed space when checking if datanode can host new container #5721

Uh oh!

Conversation

vtutrinov commented Dec 4, 2023

What changes were proposed in this pull request?

What is the link to the Apache JIRA

How was this patch tested?

Uh oh!

adoroszlai commented Dec 4, 2023

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

vtutrinov Dec 6, 2023 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

xichen01 left a comment

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

adoroszlai commented Dec 10, 2023

Uh oh!

vtutrinov commented Dec 10, 2023

Uh oh!

xichen01 commented Dec 10, 2023

Uh oh!

vtutrinov commented Dec 11, 2023 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

sumitagrawl left a comment

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

Choose a reason for hiding this comment

Uh oh!

xichen01 commented Dec 11, 2023

Uh oh!

adoroszlai commented Dec 11, 2023

Uh oh!

vtutrinov Dec 6, 2023 •

edited

Loading

vtutrinov commented Dec 11, 2023 •

edited

Loading

adoroszlai commented Dec 21, 2023 •

edited

Loading