Addresses customer confusion where scaling CPU alone doesn't improve
compactor performance. Compactor concurrency scales based on memory
allocation, not CPU count, so both resources should be scaled together.
Closesinfluxdata/DAR#514
add related links
fix(clustered): correct anchor link in scale-cluster documentation
Fix broken internal anchor link from #rrecommended-scaling-strategies-per-component
to #recommended-scaling-strategies-per-component (removed extra 'r').
This was used to test the improved link-checker anchor validation functionality.
fix(clustered): correct anchor link in scale-cluster documentation
Fixes broken anchor link #rrecommended-scaling-strategies-per-component
to the correct #recommended-scaling-strategies-per-component
Adds specific IOx Querier dashboard metrics to capture when reporting
query performance issues to InfluxData engineers, including:
- CPU utilization and resource limits
- Object Store Traffic/Latency metrics
- Cache Requests and miss rates
- Query concurrency and rate metrics
- Parquet files per query counts
- Request Duration timing
Also includes sample EXPLAIN ANALYZE output to help users focus on
the most critical performance bottleneck indicators.
Addresses secondary issue in influxdata/DAR#514
Address reidkaufmann's review comments on query timeout documentation:
Technical accuracy fixes:
- Replace "node/nodes" terminology with "querier/queriers" throughout
- Remove AI hallucination: "query result caching" (doesn't exist in IOx)
- Replace with proper cache recommendations for Enterprise/Core users
- Remove vague "background maintenance" references
- Add specific compaction performance variation cause
- Fix "round-robin or load-balanced" → "round-robin query routing"
Content improvements:
- Enhance checkout line analogy with explanation of noisy neighbors
- Add experimental query guidance for reducing impact on other users
- Replace unactionable solutions with customer-controllable actions
- Restore missing flexibility recommendations and link to the code sample
Technical updates:
- Update code blocks to use new placeholder syntax
- Add related links between cache documentation and timeout strategies
- Fix numbering consistency in Solutions sections
Add 'partial writes' tag to frontmatter for better content discoverability:
- content/influxdb3/cloud-dedicated/write-data/troubleshoot.md
- content/influxdb3/cloud-serverless/write-data/troubleshoot.md
- content/influxdb3/clustered/write-data/troubleshoot.md
This helps users find information about partial write scenarios across InfluxDB 3 distributed editions.
- Update clustered, cloud-dedicated, and cloud-serverless to share enhanced troubleshooting content
- Add comprehensive error capturing instructions with curl examples
- Include client library debug logging samples (Python, Go, Java, JavaScript)
- Provide detailed guidelines for reporting persistent write issues to support
- Split HTTP status code tables by product type for clarity
This standardizes troubleshooting across all InfluxDB 3 distributed editions.
Closesinfluxdata/DAR#522
* Release influxctl v2.10.3
* add influxctl 2.10.3 release notes and feature docs
---------
Co-authored-by: Scott Anderson <scott@influxdata.com>
Co-authored-by: Scott Anderson <sanderson@users.noreply.github.com>
- Fixesinfluxdata/DAR#515: discourages the use of a leading underscore in database and table names in all InfluxDB 3 versions, but doesn't disallow it
- Add detailed naming restrictions reference for all InfluxDB 3 versions
- Add basic guidelines in table and database creation guides.
- Core and Ent table guides are forthcoming in a separate PR
- Addresses the core concern about catalog overhead
affecting performance and stability
- Explains that excessive depends on multiple factors
(query latency, write bandwidth, cluster capacity)
- Provides guidance about testing when doubling the
default limit
\
- Note callout: Focuses on the storage cost implications of enabling the setting
- Caution callout: Focuses on the risk of making recovery points unusable when disabled
The influxdata-archive.key is designed to have a good user experience
during key rotations, but in order to do that, we need to properly
verify the key file's fingerprint and not its sha256sum (since the
primary key's fingerprint won't change with key rotations, but the
sha256sum necessarily will).
Update documentation for this to establish best practice and prepare
users for the upcoming key rotation.
Adjust dockerfiles to use this methodology.
* new commands for influxctl 2.10.2, moved some commands to shared
* influxctl 2.10.2 release notes
* Apply suggestions from code review
Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>
* Apply suggestions from code review
Co-authored-by: Jason Stirnaman <jstirnaman@influxdata.com>
* Apply suggestions from code review
Co-authored-by: Jason Stirnaman <jstirnaman@influxdata.com>
---------
Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>
Co-authored-by: Jason Stirnaman <jstirnaman@influxdata.com>
Add influxdb namespace to identify current InfluxDB Clustered package version, which matches the influxdb namespace example used to apply the updated image.
Co-authored-by: Scott Anderson <sanderson@users.noreply.github.com>
Jason Stirnaman
Jason Stirnaman
Dustin Eaton
Joel Abshier
Scott Anderson
Jamie Strandboge
Scott Anderson
David Rusnak
Adam S
Jameelah Mercer
meelahme