diff --git a/docs/content/Historical-Config.md b/docs/content/Historical-Config.md
index e551382c7c6..dbc610d00d1 100644
--- a/docs/content/Historical-Config.md
+++ b/docs/content/Historical-Config.md
@@ -22,6 +22,7 @@ The historical node uses several of the global configs in [Configuration](Config
 
 |Property|Description|Default|
 |--------|-----------|-------|
+|`druid.server.maxSize`|The maximum number of bytes-worth of segments that the node wants assigned to it. This is not a limit that Historical nodes actually enforces, just a value published to the Coordinator node so it can plan accordingly.|0|
 |`druid.server.tier`| A string to name the distribution tier that the storage node belongs to. Many of the [rules Coordinator nodes use](Rule-Configuration.html) to manage segments can be keyed on tiers. |  `_default_tier` |
 |`druid.server.priority`|In a tiered architecture, the priority of the tier, thus allowing control over which nodes are queried. Higher numbers mean higher priority. The default (no priority) works for architecture with no cross replication (tiers that have no data-storage overlap). Data centers typically have equal priority. | 0 |