Skip to content

Commit 78d11ba

Browse files
updating feature layout name.
1 parent ed954a3 commit 78d11ba

1 file changed

Lines changed: 3 additions & 3 deletions

File tree

hadoop-hdds/docs/content/design/storage-distribution.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -270,7 +270,7 @@ The pending deletion bytes are calculated and updated within the BlockDeletionSe
270270

271271
### New HDDS Layout and Upgrade
272272

273-
A new HDDS layout feature, DATA_DISTRIBUTION, has been introduced to handle upgrade and downgrade scenarios correctly and ensure accurate persistence of pending deletion metrics.
273+
A new HDDS layout feature, STORAGE_SPACE_DISTRIBUTION, has been introduced to handle upgrade and downgrade scenarios correctly and ensure accurate persistence of pending deletion metrics.
274274

275275
#### Why a New Layout Feature Is Needed
276276

@@ -279,13 +279,13 @@ If these metrics are written before the cluster is finalized, and later the clus
279279

280280
To prevent such inaccuracies, SCM and DNs must only start persisting the aggregated pending deletion data once the layout feature is finalized.
281281

282-
#### Behavior Before DATA_DISTRIBUTION Finalization
282+
#### Behavior Before STORAGE_SPACE_DISTRIBUTION Finalization
283283

284284
- SCM does not collect or expose DeletedBlocksTransactionSummary.
285285
- DNs do not report TotalPendingBytes.
286286
- Recon must handle the case where SCM and DN do not expose storage distribution data.
287287

288-
#### Behavior After DATA_DISTRIBUTION Finalization
288+
#### Behavior After STORAGE_SPACE_DISTRIBUTION Finalization
289289

290290
- SCM aggregates block sizes for new transactions, updates DeletedBlocksTransactionSummary, and exposes these metrics.
291291
- DNs handle both legacy and new transactions, calculate pending deletion bytes for new ones, and report them.

0 commit comments

Comments
 (0)