a30345170c
* feat(influxdb3): Core and Ent performance tuning guide:Add an admin/performance-tuning/ page with specific workload and capacity configurations.Part of #6403. * fix(influxdb3): product-specific link fragments for flags * fix(influxdb3): enterprise-specific link fragments * Apply suggestion from @jstirnaman * fix(influxdb3): duplicate licensing and resource limits sections- Rem… (#6470) * fix(influxdb3): duplicate licensing and resource limits sections- Remove duplicate licensing section- Resolve resource limits duplicates, merging details into the Resource limits section. * fix(influxdb3): fix broken links and enterprise-only flags in config options - Comment out TOC links to undocumented datafusion-runtime-* dev flags - Wrap enterprise-only section references (#licensing, #resource-limits) in conditionals - Fix num-datafusion-threads incorrectly marked as enterprise-only - Move Resource Limits section heading outside enterprise wrapper Resolves broken fragment links for both Core and Enterprise builds. * feat(enterprise): add cluster management documentation (#6431) Add comprehensive guide for managing InfluxDB 3 Enterprise clusters including: - Node configuration and deployment - Cluster initialization and scaling - Node removal and replacement procedures - Best practices for production deployments * Fixes multiple influxdb3 config option issues: - Fixed option placement (global vs serve options) in performance-tuning.md - Fixed --datafusion-num-threads option name (was --num-datafusion-threads) - Fixed --parquet-mem-cache-size option name and defaults for Core - Commented out unreleased --compaction-row-limit option - Added v3.0.0 breaking changes to release notes - Updated config-options.md with correct defaults and value formats All changes verified against InfluxDB v3.5.0 release binaries and git history. * fix(influxdb3): config options in clustering.md - Correctly place server options - Comment out unreleased options |
||
|---|---|---|
| .. | ||
| influxctl | ||
| influxdb-client-libraries-reference | ||
| influxdb-v2 | ||
| influxdb3 | ||
| influxdb3-admin | ||
| influxdb3-api-reference | ||
| influxdb3-cli | ||
| influxdb3-get-started | ||
| influxdb3-internals | ||
| influxdb3-internals-reference | ||
| influxdb3-plugins | ||
| influxdb3-query-guides | ||
| influxdb3-reference | ||
| influxdb3-sample-data | ||
| influxdb3-visualize | ||
| influxdb3-write-guides | ||
| influxql-v3-reference | ||
| sql-reference | ||
| v3-core-enterprise-release-notes | ||
| v3-distributed-admin-custom-partitions | ||
| v3-distributed-internals-reference | ||
| v3-process-data/visualize | ||
| README.md | ||
| _index.md | ||
| v3-line-protocol.md | ||
README.md
Shared content
This section is for content shared across multiple products and versions.
The /shared/_index.md frontmatter, marks the /shared directory and its
children as draft so they
don't get rendered when the site is built, but the contents of each shared
documented is included in pages that use the file as a source in their
frontmatter.
Use shared content
-
Create a new folder for the content in the
content/shared/directory. -
Copy the markdown files into the new folder.
-
Remove the frontmatter from the markdown files in the shared directory. If the first line starts with a shortcode, add an HTML comment before the first line, otherwise hugo will err.
-
In each of the files that use the shared content, add a source to the frontmatter that points to the shared markdown file—for example:
source: /shared/influxql-v3-reference/regular-expressions.md -
In the doc body, remove the shared Markdown text and add a comment that points to the shared file, in case someone happens upon the page in the repo--for example, in
/content/3/core/reference/influxql/regular-expressions.md, add the following: