You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@druid.apache.org by vo...@apache.org on 2023/01/12 23:36:20 UTC
[druid-website-src] branch update_25_docs_with_fixes updated: update 25 docs with fixes
This is an automated email from the ASF dual-hosted git repository.
vogievetsky pushed a commit to branch update_25_docs_with_fixes
in repository https://gitbox.apache.org/repos/asf/druid-website-src.git
The following commit(s) were added to refs/heads/update_25_docs_with_fixes by this push:
new 79e9ab3c update 25 docs with fixes
79e9ab3c is described below
commit 79e9ab3c0a22f7b42181e0ab045c8c5a0b83f686
Author: Vadim Ogievetsky <va...@ogievetsky.com>
AuthorDate: Thu Jan 12 15:36:13 2023 -0800
update 25 docs with fixes
---
docs/25.0.0/operations/single-server.html | 76 ++++++++----------------
docs/25.0.0/querying/sql-metadata-tables.html | 3 +-
docs/25.0.0/tutorials/docker.html | 2 +-
docs/25.0.0/tutorials/index.html | 5 +-
docs/25.0.0/tutorials/tutorial-batch-hadoop.html | 2 +-
docs/25.0.0/tutorials/tutorial-kafka.html | 2 +-
docs/latest/operations/single-server.html | 76 ++++++++----------------
docs/latest/querying/sql-metadata-tables.html | 3 +-
docs/latest/tutorials/docker.html | 2 +-
docs/latest/tutorials/index.html | 5 +-
docs/latest/tutorials/tutorial-batch-hadoop.html | 2 +-
docs/latest/tutorials/tutorial-kafka.html | 2 +-
12 files changed, 62 insertions(+), 118 deletions(-)
diff --git a/docs/25.0.0/operations/single-server.html b/docs/25.0.0/operations/single-server.html
index 40000545..b9d0e40d 100644
--- a/docs/25.0.0/operations/single-server.html
+++ b/docs/25.0.0/operations/single-server.html
@@ -77,63 +77,37 @@
~ specific language governing permissions and limitations
~ under the License.
-->
-<p>Druid includes a set of reference configurations and launch scripts for single-machine deployments.
-These configuration bundles are located in <code>conf/druid/single-server/</code>.</p>
-<p>The <code>auto</code> configuration sizes runtime parameters based on available processors and memory. Other configurations include hard-coded runtime parameters for various server sizes. Most users should stick with <code>auto</code>. Refer below <a href="#druid-auto-start">Druid auto start</a></p>
+<p>Druid includes a launch script, <code>bin/start-druid</code> that automatically sets various memory-related parameters based on available processors and memory.
+It accepts optional arguments such as list of services, total memory, and a config directory to override default JVM arguments and service-specific runtime properties.</p>
+<p>By default, the services started by <code>bin/start-druid</code>:</p>
<ul>
-<li><code>auto</code> (run script: <code>bin/start-druid</code>)</li>
-<li><code>nano-quickstart</code> (run script: <code>bin/start-nano-quickstart</code>)</li>
-<li><code>micro-quickstart</code> (run script: <code>bin/start-micro-quickstart</code>)</li>
-<li><code>small</code> (run script: <code>bin/start-single-server-small</code>)</li>
-<li><code>medium</code> (run script: <code>bin/start-single-server-medium</code>)</li>
-<li><code>large</code> (run script: <code>bin/start-single-server-large</code>)</li>
-<li><code>xlarge</code> (run script: <code>bin/start-single-server-xlarge</code>)</li>
+<li>use all processors</li>
+<li>can use up to 80% memory on the system</li>
+<li>apply the configuration files in <code>conf/druid/auto</code> for all other settings.</li>
</ul>
+<p>For details about possible arguments, run <code>bin/start-druid --help</code>.</p>
+<h2><a class="anchor" aria-hidden="true" id="single-server-reference-configurations-deprecated"></a><a href="#single-server-reference-configurations-deprecated" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 [...]
+<p>Druid includes a set of reference configurations and launch scripts for single-machine deployments.
+These start scripts are deprecated in favor of the <code>bin/start-druid</code> script documented above.
+These configuration bundles are located in <code>conf/druid/single-server/</code>.</p>
+<table>
+<thead>
+<tr><th>Configuration</th><th>Sizing</th><th>Launch command</th><th>Configuration directory</th></tr>
+</thead>
+<tbody>
+<tr><td><code>nano-quickstart</code></td><td>1 CPU, 4GiB RAM</td><td><code>bin/start-nano-quickstart</code></td><td><code>conf/druid/single-server/nano-quickstart</code></td></tr>
+<tr><td><code>micro-quickstart</code></td><td>4 CPU, 16GiB RAM</td><td><code>bin/start-micro-quickstart</code></td><td><code>conf/druid/single-server/micro-quickstart</code></td></tr>
+<tr><td><code>small</code></td><td>8 CPU, 64GiB RAM (~i3.2xlarge)</td><td><code>bin/start-small</code></td><td><code>conf/druid/single-server/small</code></td></tr>
+<tr><td><code>medium</code></td><td>16 CPU, 128GiB RAM (~i3.4xlarge)</td><td><code>bin/start-medium</code></td><td><code>conf/druid/single-server/medium</code></td></tr>
+<tr><td><code>large</code></td><td>32 CPU, 256GiB RAM (~i3.8xlarge)</td><td><code>bin/start-large</code></td><td><code>conf/druid/single-server/large</code></td></tr>
+<tr><td><code>xlarge</code></td><td>64 CPU, 512GiB RAM (~i3.16xlarge)</td><td><code>bin/start-xlarge</code></td><td><code>conf/druid/single-server/xlarge</code></td></tr>
+</tbody>
+</table>
<p>The <code>micro-quickstart</code> is sized for small machines like laptops and is intended for quick evaluation use-cases.</p>
<p>The <code>nano-quickstart</code> is an even smaller configuration, targeting a machine with 1 CPU and 4GiB memory. It is meant for limited evaluations in resource constrained environments, such as small Docker containers.</p>
<p>The other configurations are intended for general use single-machine deployments. They are sized for hardware roughly based on Amazon's i3 series of EC2 instances.</p>
<p>The startup scripts for these example configurations run a single ZK instance along with the Druid services. You can choose to deploy ZK separately as well.</p>
-<p>The example configurations run the Druid Coordinator and Overlord together in a single process using the optional configuration <code>druid.coordinator.asOverlord.enabled=true</code>, described in the <a href="/docs/25.0.0/configuration/index.html#coordinator-operation">Coordinator configuration documentation</a>.</p>
-<p>While example configurations are provided for very large single machines, at higher scales we recommend running Druid in a <a href="/docs/25.0.0/tutorials/cluster.html">clustered deployment</a>, for fault-tolerance and reduced resource contention.</p>
-<h2><a class="anchor" aria-hidden="true" id="druid-auto-start"></a><a href="#druid-auto-start" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2. [...]
-<p>Druid includes a launch script, <code>bin/start-druid</code> that automatically sets various memory-related parameters based on available processors and memory. It accepts optional arguments such as list of services, total memory and a config directory to override default JVM arguments and service-specific runtime properties.</p>
-<p><code>start-druid</code> is a generic launch script capable of starting any set of Druid services on a server.
-It accepts optional arguments such as list of services, total memory and a config directory to override default JVM arguments and service-specific runtime properties.
-Druid services will use all processors and up to 80% memory on the system.
-For details about possible arguments, run <code>bin/start-druid --help</code>.</p>
-<p>The corresponding launch scripts (e.g. <code>start-micro-quickstart</code>) are now deprecated.</p>
-<h2><a class="anchor" aria-hidden="true" id="single-server-reference-configurations"></a><a href="#single-server-reference-configurations" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1. [...]
-<h3><a class="anchor" aria-hidden="true" id="nano-quickstart-1-cpu-4gib-ram"></a><a href="#nano-quickstart-1-cpu-4gib-ram" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 1 [...]
-<ul>
-<li>Launch command: <code>bin/start-nano-quickstart</code></li>
-<li>Configuration directory: <code>conf/druid/single-server/nano-quickstart</code></li>
-</ul>
-<h3><a class="anchor" aria-hidden="true" id="micro-quickstart-4-cpu-16gib-ram"></a><a href="#micro-quickstart-4-cpu-16gib-ram" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13. [...]
-<ul>
-<li>Launch command: <code>bin/start-micro-quickstart</code></li>
-<li>Configuration directory: <code>conf/druid/single-server/micro-quickstart</code></li>
-</ul>
-<h3><a class="anchor" aria-hidden="true" id="small-8-cpu-64gib-ram-i32xlarge"></a><a href="#small-8-cpu-64gib-ram-i32xlarge" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 [...]
-<ul>
-<li>Launch command: <code>bin/start-small</code></li>
-<li>Configuration directory: <code>conf/druid/single-server/small</code></li>
-</ul>
-<h3><a class="anchor" aria-hidden="true" id="medium-16-cpu-128gib-ram-i34xlarge"></a><a href="#medium-16-cpu-128gib-ram-i34xlarge" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5 [...]
-<ul>
-<li>Launch command: <code>bin/start-medium</code></li>
-<li>Configuration directory: <code>conf/druid/single-server/medium</code></li>
-</ul>
-<h3><a class="anchor" aria-hidden="true" id="large-32-cpu-256gib-ram-i38xlarge"></a><a href="#large-32-cpu-256gib-ram-i38xlarge" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S1 [...]
-<ul>
-<li>Launch command: <code>bin/start-large</code></li>
-<li>Configuration directory: <code>conf/druid/single-server/large</code></li>
-</ul>
-<h3><a class="anchor" aria-hidden="true" id="x-large-64-cpu-512gib-ram-i316xlarge"></a><a href="#x-large-64-cpu-512gib-ram-i316xlarge" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 [...]
-<ul>
-<li>Launch command: <code>bin/start-xlarge</code></li>
-<li>Configuration directory: <code>conf/druid/single-server/xlarge</code></li>
-</ul>
-</span></div></article></div><div class="docs-prevnext"><a class="docs-prev button" href="/docs/25.0.0/tutorials/index.html"><span class="arrow-prev">← </span><span>Quickstart (local)</span></a><a class="docs-next button" href="/docs/25.0.0/tutorials/cluster.html"><span>Clustered deployment</span><span class="arrow-next"> →</span></a></div></div></div><nav class="onPageNav"><ul class="toc-headings"><li><a href="#druid-auto-start">Druid auto start</a></li><li><a href="#single-server-refer [...]
+</span></div></article></div><div class="docs-prevnext"><a class="docs-prev button" href="/docs/25.0.0/tutorials/index.html"><span class="arrow-prev">← </span><span>Quickstart (local)</span></a><a class="docs-next button" href="/docs/25.0.0/tutorials/cluster.html"><span>Clustered deployment</span><span class="arrow-next"> →</span></a></div></div></div><nav class="onPageNav"><ul class="toc-headings"><li><a href="#single-server-reference-configurations-deprecated">Single server reference c [...]
document.addEventListener('keyup', function(e) {
if (e.target !== document.body) {
return;
diff --git a/docs/25.0.0/querying/sql-metadata-tables.html b/docs/25.0.0/querying/sql-metadata-tables.html
index 5b8cd7b9..cf8941d9 100644
--- a/docs/25.0.0/querying/sql-metadata-tables.html
+++ b/docs/25.0.0/querying/sql-metadata-tables.html
@@ -187,7 +187,8 @@ datasource "foo", use the query:</p>
<tr><td>is_published</td><td>LONG</td><td>Boolean represented as long type where 1 = true, 0 = false. 1 if this segment has been published to the metadata store and is marked as used. See the <a href="/docs/25.0.0/design/architecture.html#segment-lifecycle">segment lifecycle documentation</a> for more details.</td></tr>
<tr><td>is_available</td><td>LONG</td><td>Boolean represented as long type where 1 = true, 0 = false. 1 if this segment is currently being served by any data serving process, like a Historical or a realtime ingestion task. See the <a href="/docs/25.0.0/design/architecture.html#segment-lifecycle">segment lifecycle documentation</a> for more details.</td></tr>
<tr><td>is_realtime</td><td>LONG</td><td>Boolean represented as long type where 1 = true, 0 = false. 1 if this segment is <em>only</em> served by realtime tasks, and 0 if any Historical process is serving this segment.</td></tr>
-<tr><td>is_overshadowed</td><td>LONG</td><td>Boolean represented as long type where 1 = true, 0 = false. 1 if this segment is published and is <em>fully</em> overshadowed by some other published segments. Currently, <code>is_overshadowed</code> is always 0 for unpublished segments, although this may change in the future. You can filter for segments that "should be published" by filtering for <code>is_published = 1 AND is_overshadowed = 0</code>. Segments can briefly be both pub [...]
+<tr><td>is_overshadowed</td><td>LONG</td><td>Boolean represented as long type where 1 = true, 0 = false. 1 if this segment is published and is <em>fully</em> overshadowed by some other published segments. Currently, <code>is_overshadowed</code> is always 0 for unpublished segments, although this may change in the future. You can filter for segments that "should be published" by filtering for <code>is_published = 1 AND is_overshadowed = 0</code>. Segments can briefly be both pub [...]
+<tr><td>shard_spec</td><td>STRING</td><td>JSON-serialized form of the segment <code>ShardSpec</code></td></tr>
<tr><td>dimensions</td><td>STRING</td><td>JSON-serialized form of the segment dimensions</td></tr>
<tr><td>metrics</td><td>STRING</td><td>JSON-serialized form of the segment metrics</td></tr>
<tr><td>last_compaction_state</td><td>STRING</td><td>JSON-serialized form of the compaction task's config (compaction task which created this segment). May be null if segment was not created by compaction task.</td></tr>
diff --git a/docs/25.0.0/tutorials/docker.html b/docs/25.0.0/tutorials/docker.html
index 49267a1b..d4d70a10 100644
--- a/docs/25.0.0/tutorials/docker.html
+++ b/docs/25.0.0/tutorials/docker.html
@@ -86,7 +86,7 @@ After you finish the initial setup, the cluster will be ready to load data.</p>
<li><a href="https://www.docker.com/get-started">Docker</a></li>
</ul>
<h3><a class="anchor" aria-hidden="true" id="docker-memory-requirements"></a><a href="#docker-memory-requirements" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H [...]
-<p>The default <code>docker-compose.yml</code> launches eight containers: Zookeeper, PostgreSQL, and six Druid containers based upon the <a href="../operations/single-server.html#micro-quickstart-4-cpu-16gib-ram">micro quickstart configuration</a>.
+<p>The default <code>docker-compose.yml</code> launches eight containers: Zookeeper, PostgreSQL, and six Druid containers based upon the <a href="../operations/single-server.html#single-server-reference-configurations-deprecated">micro quickstart configuration</a>.
Each Druid service is configured to use up to 7 GiB of memory (6 GiB direct memory and 1 GiB heap). However, the quickstart will not use all the available memory.</p>
<p>For this setup, Docker needs at least 6 GiB of memory available for the Druid cluster. For Docker Desktop on Mac OS, adjust the memory settings in the <a href="https://docs.docker.com/desktop/mac/">Docker Desktop preferences</a>. If you experience a crash with a 137 error code you likely don't have enough memory allocated to Docker.</p>
<p>You can modify the value of <code>DRUID_SINGLE_NODE_CONF</code> in the Docker <a href="#environment-file"><code>environment</code></a> to use different single-server mode. For example to use the nano quickstart: <code>DRUID_SINGLE_NODE_CONF=nano-quickstart</code>.</p>
diff --git a/docs/25.0.0/tutorials/index.html b/docs/25.0.0/tutorials/index.html
index 26c0d2bc..8aac06a2 100644
--- a/docs/25.0.0/tutorials/index.html
+++ b/docs/25.0.0/tutorials/index.html
@@ -88,9 +88,6 @@
<a href="/docs/25.0.0/ingestion/index.html">Ingestion</a> page to determine which ingestion method is right for you.</p>
<h2><a class="anchor" aria-hidden="true" id="requirements"></a><a href="#requirements" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83. [...]
<p>You can follow these steps on a relatively modest machine, such as a workstation or virtual server with 16 GiB of RAM.</p>
-<p>Druid comes equipped with launch scripts that can be used to start all processes on a single server. Here, we will use <a href="/docs/25.0.0/operations/single-server.html#druid-auto-start"><code>auto</code></a>, which automatically sets various runtime properties based on available processors and memory.</p>
-<p>In addition, Druid includes several <a href="/docs/25.0.0/operations/single-server.html">bundled non-automatic profiles</a> for a range of machine sizes. These range from nano (1 CPU, 4GiB RAM) to x-large (64 CPU, 512GiB RAM).
-We won't use those here, but for more information, see <a href="/docs/25.0.0/operations/single-server.html">Single server deployment</a>. For additional information on deploying Druid services across clustered machines, see <a href="/docs/25.0.0/tutorials/cluster.html">Clustered deployment</a>.</p>
<p>The software requirements for the installation machine are:</p>
<ul>
<li>Linux, Mac OS X, or other Unix-like OS. (Windows is not supported)</li>
@@ -113,7 +110,7 @@ dedicated user account for running Druid.</p>
</code></pre>
<p>The distribution directory contains <code>LICENSE</code> and <code>NOTICE</code> files and subdirectories for executable files, configuration files, sample data and more.</p>
<h2><a class="anchor" aria-hidden="true" id="start-up-druid-services"></a><a href="#start-up-druid-services" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 [...]
-<p>Start up Druid services using the <code>auto</code> single-machine configuration.
+<p>Start up Druid services using the automatic single-machine configuration.
This configuration includes default settings that are appropriate for this tutorial, such as loading the <code>druid-multi-stage-query</code> extension by default so that you can use the MSQ task engine.</p>
<p>You can view that setting and others in the configuration files in the <code>conf/druid/auto</code>.</p>
<p>From the apache-druid-25.0.0 package root, run the following command:</p>
diff --git a/docs/25.0.0/tutorials/tutorial-batch-hadoop.html b/docs/25.0.0/tutorials/tutorial-batch-hadoop.html
index da082171..a39144a2 100644
--- a/docs/25.0.0/tutorials/tutorial-batch-hadoop.html
+++ b/docs/25.0.0/tutorials/tutorial-batch-hadoop.html
@@ -80,7 +80,7 @@
<p>This tutorial shows you how to load data files into Apache Druid using a remote Hadoop cluster.</p>
<p>For this tutorial, we'll assume that you've already completed the previous
<a href="/docs/25.0.0/tutorials/tutorial-batch.html">batch ingestion tutorial</a> using Druid's native batch ingestion system and are using the
-<code>auto</code> single-machine configuration as described in the <a href="/docs/25.0.0/operations/single-server.html#druid-auto-start">quickstart</a>.</p>
+automatic single-machine configuration as described in the <a href="/docs/25.0.0/operations/single-server.html">quickstart</a>.</p>
<h2><a class="anchor" aria-hidden="true" id="install-docker"></a><a href="#install-docker" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0- [...]
<p>This tutorial requires <a href="https://docs.docker.com/install/">Docker</a> to be installed on the tutorial machine.</p>
<p>Once the Docker install is complete, please proceed to the next steps in the tutorial.</p>
diff --git a/docs/25.0.0/tutorials/tutorial-kafka.html b/docs/25.0.0/tutorials/tutorial-kafka.html
index 57cfb6b1..45d314ef 100644
--- a/docs/25.0.0/tutorials/tutorial-kafka.html
+++ b/docs/25.0.0/tutorials/tutorial-kafka.html
@@ -80,7 +80,7 @@
<p>This tutorial shows you how to load data into Apache Druid from a Kafka stream, using Druid's Kafka indexing service.</p>
<p>The tutorial guides you through the steps to load sample nested clickstream data from the <a href="https://www.koalastothemax.com/">Koalas to the Max</a> game into a Kafka topic, then ingest the data into Druid.</p>
<h2><a class="anchor" aria-hidden="true" id="prerequisites"></a><a href="#prerequisites" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.8 [...]
-<p>Before you follow the steps in this tutorial, download Druid as described in the <a href="/docs/25.0.0/tutorials/index.html">quickstart</a> using the <a href="/docs/25.0.0/operations/single-server.html#druid-auto-start">auto</a> single-machine configuration and have it running on your local machine. You don't need to have loaded any data.</p>
+<p>Before you follow the steps in this tutorial, download Druid as described in the <a href="/docs/25.0.0/tutorials/index.html">quickstart</a> using the <a href="/docs/25.0.0/operations/single-server.html">automatic single-machine configuration</a> and have it running on your local machine. You don't need to have loaded any data.</p>
<h2><a class="anchor" aria-hidden="true" id="download-and-start-kafka"></a><a href="#download-and-start-kafka" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-. [...]
<p><a href="http://kafka.apache.org/">Apache Kafka</a> is a high-throughput message bus that works well with Druid. For this tutorial, use Kafka 2.7.0.</p>
<ol>
diff --git a/docs/latest/operations/single-server.html b/docs/latest/operations/single-server.html
index 228a73ce..a16289b9 100644
--- a/docs/latest/operations/single-server.html
+++ b/docs/latest/operations/single-server.html
@@ -77,63 +77,37 @@
~ specific language governing permissions and limitations
~ under the License.
-->
-<p>Druid includes a set of reference configurations and launch scripts for single-machine deployments.
-These configuration bundles are located in <code>conf/druid/single-server/</code>.</p>
-<p>The <code>auto</code> configuration sizes runtime parameters based on available processors and memory. Other configurations include hard-coded runtime parameters for various server sizes. Most users should stick with <code>auto</code>. Refer below <a href="#druid-auto-start">Druid auto start</a></p>
+<p>Druid includes a launch script, <code>bin/start-druid</code> that automatically sets various memory-related parameters based on available processors and memory.
+It accepts optional arguments such as list of services, total memory, and a config directory to override default JVM arguments and service-specific runtime properties.</p>
+<p>By default, the services started by <code>bin/start-druid</code>:</p>
<ul>
-<li><code>auto</code> (run script: <code>bin/start-druid</code>)</li>
-<li><code>nano-quickstart</code> (run script: <code>bin/start-nano-quickstart</code>)</li>
-<li><code>micro-quickstart</code> (run script: <code>bin/start-micro-quickstart</code>)</li>
-<li><code>small</code> (run script: <code>bin/start-single-server-small</code>)</li>
-<li><code>medium</code> (run script: <code>bin/start-single-server-medium</code>)</li>
-<li><code>large</code> (run script: <code>bin/start-single-server-large</code>)</li>
-<li><code>xlarge</code> (run script: <code>bin/start-single-server-xlarge</code>)</li>
+<li>use all processors</li>
+<li>can use up to 80% memory on the system</li>
+<li>apply the configuration files in <code>conf/druid/auto</code> for all other settings.</li>
</ul>
+<p>For details about possible arguments, run <code>bin/start-druid --help</code>.</p>
+<h2><a class="anchor" aria-hidden="true" id="single-server-reference-configurations-deprecated"></a><a href="#single-server-reference-configurations-deprecated" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 [...]
+<p>Druid includes a set of reference configurations and launch scripts for single-machine deployments.
+These start scripts are deprecated in favor of the <code>bin/start-druid</code> script documented above.
+These configuration bundles are located in <code>conf/druid/single-server/</code>.</p>
+<table>
+<thead>
+<tr><th>Configuration</th><th>Sizing</th><th>Launch command</th><th>Configuration directory</th></tr>
+</thead>
+<tbody>
+<tr><td><code>nano-quickstart</code></td><td>1 CPU, 4GiB RAM</td><td><code>bin/start-nano-quickstart</code></td><td><code>conf/druid/single-server/nano-quickstart</code></td></tr>
+<tr><td><code>micro-quickstart</code></td><td>4 CPU, 16GiB RAM</td><td><code>bin/start-micro-quickstart</code></td><td><code>conf/druid/single-server/micro-quickstart</code></td></tr>
+<tr><td><code>small</code></td><td>8 CPU, 64GiB RAM (~i3.2xlarge)</td><td><code>bin/start-small</code></td><td><code>conf/druid/single-server/small</code></td></tr>
+<tr><td><code>medium</code></td><td>16 CPU, 128GiB RAM (~i3.4xlarge)</td><td><code>bin/start-medium</code></td><td><code>conf/druid/single-server/medium</code></td></tr>
+<tr><td><code>large</code></td><td>32 CPU, 256GiB RAM (~i3.8xlarge)</td><td><code>bin/start-large</code></td><td><code>conf/druid/single-server/large</code></td></tr>
+<tr><td><code>xlarge</code></td><td>64 CPU, 512GiB RAM (~i3.16xlarge)</td><td><code>bin/start-xlarge</code></td><td><code>conf/druid/single-server/xlarge</code></td></tr>
+</tbody>
+</table>
<p>The <code>micro-quickstart</code> is sized for small machines like laptops and is intended for quick evaluation use-cases.</p>
<p>The <code>nano-quickstart</code> is an even smaller configuration, targeting a machine with 1 CPU and 4GiB memory. It is meant for limited evaluations in resource constrained environments, such as small Docker containers.</p>
<p>The other configurations are intended for general use single-machine deployments. They are sized for hardware roughly based on Amazon's i3 series of EC2 instances.</p>
<p>The startup scripts for these example configurations run a single ZK instance along with the Druid services. You can choose to deploy ZK separately as well.</p>
-<p>The example configurations run the Druid Coordinator and Overlord together in a single process using the optional configuration <code>druid.coordinator.asOverlord.enabled=true</code>, described in the <a href="/docs/latest/configuration/index.html#coordinator-operation">Coordinator configuration documentation</a>.</p>
-<p>While example configurations are provided for very large single machines, at higher scales we recommend running Druid in a <a href="/docs/latest/tutorials/cluster.html">clustered deployment</a>, for fault-tolerance and reduced resource contention.</p>
-<h2><a class="anchor" aria-hidden="true" id="druid-auto-start"></a><a href="#druid-auto-start" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2. [...]
-<p>Druid includes a launch script, <code>bin/start-druid</code> that automatically sets various memory-related parameters based on available processors and memory. It accepts optional arguments such as list of services, total memory and a config directory to override default JVM arguments and service-specific runtime properties.</p>
-<p><code>start-druid</code> is a generic launch script capable of starting any set of Druid services on a server.
-It accepts optional arguments such as list of services, total memory and a config directory to override default JVM arguments and service-specific runtime properties.
-Druid services will use all processors and up to 80% memory on the system.
-For details about possible arguments, run <code>bin/start-druid --help</code>.</p>
-<p>The corresponding launch scripts (e.g. <code>start-micro-quickstart</code>) are now deprecated.</p>
-<h2><a class="anchor" aria-hidden="true" id="single-server-reference-configurations"></a><a href="#single-server-reference-configurations" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1. [...]
-<h3><a class="anchor" aria-hidden="true" id="nano-quickstart-1-cpu-4gib-ram"></a><a href="#nano-quickstart-1-cpu-4gib-ram" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 1 [...]
-<ul>
-<li>Launch command: <code>bin/start-nano-quickstart</code></li>
-<li>Configuration directory: <code>conf/druid/single-server/nano-quickstart</code></li>
-</ul>
-<h3><a class="anchor" aria-hidden="true" id="micro-quickstart-4-cpu-16gib-ram"></a><a href="#micro-quickstart-4-cpu-16gib-ram" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13. [...]
-<ul>
-<li>Launch command: <code>bin/start-micro-quickstart</code></li>
-<li>Configuration directory: <code>conf/druid/single-server/micro-quickstart</code></li>
-</ul>
-<h3><a class="anchor" aria-hidden="true" id="small-8-cpu-64gib-ram-i32xlarge"></a><a href="#small-8-cpu-64gib-ram-i32xlarge" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 [...]
-<ul>
-<li>Launch command: <code>bin/start-small</code></li>
-<li>Configuration directory: <code>conf/druid/single-server/small</code></li>
-</ul>
-<h3><a class="anchor" aria-hidden="true" id="medium-16-cpu-128gib-ram-i34xlarge"></a><a href="#medium-16-cpu-128gib-ram-i34xlarge" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5 [...]
-<ul>
-<li>Launch command: <code>bin/start-medium</code></li>
-<li>Configuration directory: <code>conf/druid/single-server/medium</code></li>
-</ul>
-<h3><a class="anchor" aria-hidden="true" id="large-32-cpu-256gib-ram-i38xlarge"></a><a href="#large-32-cpu-256gib-ram-i38xlarge" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S1 [...]
-<ul>
-<li>Launch command: <code>bin/start-large</code></li>
-<li>Configuration directory: <code>conf/druid/single-server/large</code></li>
-</ul>
-<h3><a class="anchor" aria-hidden="true" id="x-large-64-cpu-512gib-ram-i316xlarge"></a><a href="#x-large-64-cpu-512gib-ram-i316xlarge" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 [...]
-<ul>
-<li>Launch command: <code>bin/start-xlarge</code></li>
-<li>Configuration directory: <code>conf/druid/single-server/xlarge</code></li>
-</ul>
-</span></div></article></div><div class="docs-prevnext"><a class="docs-prev button" href="/docs/latest/tutorials/index.html"><span class="arrow-prev">← </span><span>Quickstart (local)</span></a><a class="docs-next button" href="/docs/latest/tutorials/cluster.html"><span>Clustered deployment</span><span class="arrow-next"> →</span></a></div></div></div><nav class="onPageNav"><ul class="toc-headings"><li><a href="#druid-auto-start">Druid auto start</a></li><li><a href="#single-server-refer [...]
+</span></div></article></div><div class="docs-prevnext"><a class="docs-prev button" href="/docs/latest/tutorials/index.html"><span class="arrow-prev">← </span><span>Quickstart (local)</span></a><a class="docs-next button" href="/docs/latest/tutorials/cluster.html"><span>Clustered deployment</span><span class="arrow-next"> →</span></a></div></div></div><nav class="onPageNav"><ul class="toc-headings"><li><a href="#single-server-reference-configurations-deprecated">Single server reference c [...]
document.addEventListener('keyup', function(e) {
if (e.target !== document.body) {
return;
diff --git a/docs/latest/querying/sql-metadata-tables.html b/docs/latest/querying/sql-metadata-tables.html
index a06d0471..961d4e3e 100644
--- a/docs/latest/querying/sql-metadata-tables.html
+++ b/docs/latest/querying/sql-metadata-tables.html
@@ -187,7 +187,8 @@ datasource "foo", use the query:</p>
<tr><td>is_published</td><td>LONG</td><td>Boolean represented as long type where 1 = true, 0 = false. 1 if this segment has been published to the metadata store and is marked as used. See the <a href="/docs/latest/design/architecture.html#segment-lifecycle">segment lifecycle documentation</a> for more details.</td></tr>
<tr><td>is_available</td><td>LONG</td><td>Boolean represented as long type where 1 = true, 0 = false. 1 if this segment is currently being served by any data serving process, like a Historical or a realtime ingestion task. See the <a href="/docs/latest/design/architecture.html#segment-lifecycle">segment lifecycle documentation</a> for more details.</td></tr>
<tr><td>is_realtime</td><td>LONG</td><td>Boolean represented as long type where 1 = true, 0 = false. 1 if this segment is <em>only</em> served by realtime tasks, and 0 if any Historical process is serving this segment.</td></tr>
-<tr><td>is_overshadowed</td><td>LONG</td><td>Boolean represented as long type where 1 = true, 0 = false. 1 if this segment is published and is <em>fully</em> overshadowed by some other published segments. Currently, <code>is_overshadowed</code> is always 0 for unpublished segments, although this may change in the future. You can filter for segments that "should be published" by filtering for <code>is_published = 1 AND is_overshadowed = 0</code>. Segments can briefly be both pub [...]
+<tr><td>is_overshadowed</td><td>LONG</td><td>Boolean represented as long type where 1 = true, 0 = false. 1 if this segment is published and is <em>fully</em> overshadowed by some other published segments. Currently, <code>is_overshadowed</code> is always 0 for unpublished segments, although this may change in the future. You can filter for segments that "should be published" by filtering for <code>is_published = 1 AND is_overshadowed = 0</code>. Segments can briefly be both pub [...]
+<tr><td>shard_spec</td><td>STRING</td><td>JSON-serialized form of the segment <code>ShardSpec</code></td></tr>
<tr><td>dimensions</td><td>STRING</td><td>JSON-serialized form of the segment dimensions</td></tr>
<tr><td>metrics</td><td>STRING</td><td>JSON-serialized form of the segment metrics</td></tr>
<tr><td>last_compaction_state</td><td>STRING</td><td>JSON-serialized form of the compaction task's config (compaction task which created this segment). May be null if segment was not created by compaction task.</td></tr>
diff --git a/docs/latest/tutorials/docker.html b/docs/latest/tutorials/docker.html
index c27bf1f3..67d2552d 100644
--- a/docs/latest/tutorials/docker.html
+++ b/docs/latest/tutorials/docker.html
@@ -86,7 +86,7 @@ After you finish the initial setup, the cluster will be ready to load data.</p>
<li><a href="https://www.docker.com/get-started">Docker</a></li>
</ul>
<h3><a class="anchor" aria-hidden="true" id="docker-memory-requirements"></a><a href="#docker-memory-requirements" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H [...]
-<p>The default <code>docker-compose.yml</code> launches eight containers: Zookeeper, PostgreSQL, and six Druid containers based upon the <a href="../operations/single-server.html#micro-quickstart-4-cpu-16gib-ram">micro quickstart configuration</a>.
+<p>The default <code>docker-compose.yml</code> launches eight containers: Zookeeper, PostgreSQL, and six Druid containers based upon the <a href="../operations/single-server.html#single-server-reference-configurations-deprecated">micro quickstart configuration</a>.
Each Druid service is configured to use up to 7 GiB of memory (6 GiB direct memory and 1 GiB heap). However, the quickstart will not use all the available memory.</p>
<p>For this setup, Docker needs at least 6 GiB of memory available for the Druid cluster. For Docker Desktop on Mac OS, adjust the memory settings in the <a href="https://docs.docker.com/desktop/mac/">Docker Desktop preferences</a>. If you experience a crash with a 137 error code you likely don't have enough memory allocated to Docker.</p>
<p>You can modify the value of <code>DRUID_SINGLE_NODE_CONF</code> in the Docker <a href="#environment-file"><code>environment</code></a> to use different single-server mode. For example to use the nano quickstart: <code>DRUID_SINGLE_NODE_CONF=nano-quickstart</code>.</p>
diff --git a/docs/latest/tutorials/index.html b/docs/latest/tutorials/index.html
index 6d58afbc..cfa90137 100644
--- a/docs/latest/tutorials/index.html
+++ b/docs/latest/tutorials/index.html
@@ -88,9 +88,6 @@
<a href="/docs/latest/ingestion/index.html">Ingestion</a> page to determine which ingestion method is right for you.</p>
<h2><a class="anchor" aria-hidden="true" id="requirements"></a><a href="#requirements" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.83. [...]
<p>You can follow these steps on a relatively modest machine, such as a workstation or virtual server with 16 GiB of RAM.</p>
-<p>Druid comes equipped with launch scripts that can be used to start all processes on a single server. Here, we will use <a href="/docs/latest/operations/single-server.html#druid-auto-start"><code>auto</code></a>, which automatically sets various runtime properties based on available processors and memory.</p>
-<p>In addition, Druid includes several <a href="/docs/latest/operations/single-server.html">bundled non-automatic profiles</a> for a range of machine sizes. These range from nano (1 CPU, 4GiB RAM) to x-large (64 CPU, 512GiB RAM).
-We won't use those here, but for more information, see <a href="/docs/latest/operations/single-server.html">Single server deployment</a>. For additional information on deploying Druid services across clustered machines, see <a href="/docs/latest/tutorials/cluster.html">Clustered deployment</a>.</p>
<p>The software requirements for the installation machine are:</p>
<ul>
<li>Linux, Mac OS X, or other Unix-like OS. (Windows is not supported)</li>
@@ -113,7 +110,7 @@ dedicated user account for running Druid.</p>
</code></pre>
<p>The distribution directory contains <code>LICENSE</code> and <code>NOTICE</code> files and subdirectories for executable files, configuration files, sample data and more.</p>
<h2><a class="anchor" aria-hidden="true" id="start-up-druid-services"></a><a href="#start-up-druid-services" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 [...]
-<p>Start up Druid services using the <code>auto</code> single-machine configuration.
+<p>Start up Druid services using the automatic single-machine configuration.
This configuration includes default settings that are appropriate for this tutorial, such as loading the <code>druid-multi-stage-query</code> extension by default so that you can use the MSQ task engine.</p>
<p>You can view that setting and others in the configuration files in the <code>conf/druid/auto</code>.</p>
<p>From the apache-druid-25.0.0 package root, run the following command:</p>
diff --git a/docs/latest/tutorials/tutorial-batch-hadoop.html b/docs/latest/tutorials/tutorial-batch-hadoop.html
index 58a8ddba..19efb910 100644
--- a/docs/latest/tutorials/tutorial-batch-hadoop.html
+++ b/docs/latest/tutorials/tutorial-batch-hadoop.html
@@ -80,7 +80,7 @@
<p>This tutorial shows you how to load data files into Apache Druid using a remote Hadoop cluster.</p>
<p>For this tutorial, we'll assume that you've already completed the previous
<a href="/docs/latest/tutorials/tutorial-batch.html">batch ingestion tutorial</a> using Druid's native batch ingestion system and are using the
-<code>auto</code> single-machine configuration as described in the <a href="/docs/latest/operations/single-server.html#druid-auto-start">quickstart</a>.</p>
+automatic single-machine configuration as described in the <a href="/docs/latest/operations/single-server.html">quickstart</a>.</p>
<h2><a class="anchor" aria-hidden="true" id="install-docker"></a><a href="#install-docker" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0- [...]
<p>This tutorial requires <a href="https://docs.docker.com/install/">Docker</a> to be installed on the tutorial machine.</p>
<p>Once the Docker install is complete, please proceed to the next steps in the tutorial.</p>
diff --git a/docs/latest/tutorials/tutorial-kafka.html b/docs/latest/tutorials/tutorial-kafka.html
index 5f925cb8..a562407f 100644
--- a/docs/latest/tutorials/tutorial-kafka.html
+++ b/docs/latest/tutorials/tutorial-kafka.html
@@ -80,7 +80,7 @@
<p>This tutorial shows you how to load data into Apache Druid from a Kafka stream, using Druid's Kafka indexing service.</p>
<p>The tutorial guides you through the steps to load sample nested clickstream data from the <a href="https://www.koalastothemax.com/">Koalas to the Max</a> game into a Kafka topic, then ingest the data into Druid.</p>
<h2><a class="anchor" aria-hidden="true" id="prerequisites"></a><a href="#prerequisites" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-.98 0-2-1.22-2-2.5 0-.8 [...]
-<p>Before you follow the steps in this tutorial, download Druid as described in the <a href="/docs/latest/tutorials/index.html">quickstart</a> using the <a href="/docs/latest/operations/single-server.html#druid-auto-start">auto</a> single-machine configuration and have it running on your local machine. You don't need to have loaded any data.</p>
+<p>Before you follow the steps in this tutorial, download Druid as described in the <a href="/docs/latest/tutorials/index.html">quickstart</a> using the <a href="/docs/latest/operations/single-server.html">automatic single-machine configuration</a> and have it running on your local machine. You don't need to have loaded any data.</p>
<h2><a class="anchor" aria-hidden="true" id="download-and-start-kafka"></a><a href="#download-and-start-kafka" aria-hidden="true" class="hash-link"><svg class="hash-link-icon" aria-hidden="true" height="16" version="1.1" viewBox="0 0 16 16" width="16"><path fill-rule="evenodd" d="M4 9h1v1H4c-1.5 0-3-1.69-3-3.5S2.55 3 4 3h4c1.45 0 3 1.69 3 3.5 0 1.41-.91 2.72-2 3.25V8.59c.58-.45 1-1.27 1-2.09C10 5.22 8.98 4 8 4H4c-.98 0-2 1.22-2 2.5S3 9 4 9zm9-3h-1v1h1c1 0 2 1.22 2 2.5S13.98 12 13 12H9c-. [...]
<p><a href="http://kafka.apache.org/">Apache Kafka</a> is a high-throughput message bus that works well with Druid. For this tutorial, use Kafka 2.7.0.</p>
<ol>
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@druid.apache.org
For additional commands, e-mail: commits-help@druid.apache.org