From ba04741058ab209c7b9959414e12a30815aff5a5 Mon Sep 17 00:00:00 2001 From: ostreichman-ms Date: Sun, 15 Feb 2026 13:12:51 +0200 Subject: [PATCH] Update extents-overview.md --- data-explorer/kusto/management/extents-overview.md | 3 +++ 1 file changed, 3 insertions(+) diff --git a/data-explorer/kusto/management/extents-overview.md b/data-explorer/kusto/management/extents-overview.md index fc8c1f2a88..24f3ca95d4 100644 --- a/data-explorer/kusto/management/extents-overview.md +++ b/data-explorer/kusto/management/extents-overview.md @@ -22,6 +22,9 @@ The common extent lifecycle is as follows: 1. The extent is merged with other extents. 1. The merged extent (possibly one that tracks its lineage to other extents) is eventually dropped because of a [retention policy](retention-policy.md). +> [!NOTE] +> The recommended maximum number of extents per cluster is 10,000,000 + ## Extent creation time Two [datetime](../query/scalar-data-types/datetime.md) values are tracked per extent: `MinCreatedOn` and `MaxCreatedOn`. These values are initially the same but may change when the extent is merged with other extents. When the extent is merged with other extents, the new values are according to the original minimum and maximum values of the merged extents.