<p dir="auto">Currently, "historical node" accepts such configuration:</p>
<div class="snippet-clipboard-content notranslate position-relative overflow-auto" data-snippet-clipboard-copy-content="druid.segmentCache.locations=[{&quot;path&quot;: &quot;/disk2/druidUser/indexCache&quot;, &quot;maxSize&quot;\: 10000000000}]
druid.server.maxSize=30000000000"><pre class="notranslate"><code class="notranslate">druid.segmentCache.locations=[{"path": "/disk2/druidUser/indexCache", "maxSize"\: 10000000000}]
druid.server.maxSize=30000000000
</code></pre></div>
<p dir="auto">When space need exceeds 10GB, we cannot see error in "coordinator Web UI".<br>
And the usage of space is 33% in coordinator Web UI, which is misleading.</p>
<p dir="auto">I found the space problem only when I looked into "historical" node's log, and use debugger to trace the code nearby.</p>
<p dir="auto">I suggest: refuse to start historical node when sum of "indexCache" in all locations &lt; durid.server.maxSize.</p>
<p dir="auto">The rules for determining available space on a historical node for a segment seem to include both druid.server.maxSize and druid.segmentCache.locations:maxSize.</p>
<p dir="auto">However, the Coordinator Console shows the Max Size and Percent Used based only on druid.server.maxSize.</p>
<p dir="auto">It would be useful if the console showed both values to help diagnose "segment too large" errors thrown by the OmniSegmentLoader (when people accidentally set them to different values).</p>
<p dir="auto">See <a href="https://groups.google.com/forum/#!searchin/druid-development/segment$20too$20large/druid-development/w8Q65ZRusi4/kN0JybUtUfAJ" rel="nofollow">https://groups.google.com/forum/#!searchin/druid-development/segment$20too$20large/druid-development/w8Q65ZRusi4/kN0JybUtUfAJ</a></p>