content/enterprise_influxdb/v1/about-the-project/release-notes.md
<span id="v1.12.x"></span>
[!Important]
Upgrade meta nodes first
When upgrading to InfluxDB Enterprise 1.12.1+, upgrade meta nodes before upgrading data nodes.
influx_inspect buildtsi to
rebuild the TSI index.influx_inspect export with
-tsmfile option to
export a single TSM file.-m flag to the influxd-ctl show-shards command
to output inconsistent shards.fluxQueryRespBytes metric to the /debug/vars metrics endpoint.query-log-path configuration option
to data nodes.aggressive-points-per-block configuration option
to prevent TSM files from not getting fully compacted.FUTURE LIMIT
and PAST LIMIT.xxhash and avoid stringtoslicebyte in the cache.Compactor.write./shard-status API to return the correct result and use a
consistent "idleness" definition for shards.[!Note]
InfluxDB Enterprise and FIPS-compliance
InfluxDB Enterprise 1.11+ introduces builds that are compliant with Federal Information Processing Standards (FIPS) and adhere to a strict set of security standards. Both standard and FIPS-compliant InfluxDB Enterprise builds are available. For more information, see FIPS-compliant InfluxDB Enterprise builds.
/api/v2/delete compatibility
API before
string comparisons (e.g. to allow special characters in measurement names).MetaExecutor operations like
SHOW TAG VALUES and SHOW TAG KEYS.GROUP BY queries with an offset that crossed a DST boundary from failing.range() filters correctly for all years.FIPS POST if available and log the result.SHOW TAG VALUES when using FGA by optimizing queries
to be limited to only tag values the user has permission to access.jwt-go.dvsekhvalnov/jose2go to v1.6.0.influx_inspect error when deleting last measurement.protobuf library.[!Note]
Upgrading from InfluxDB Enterprise v1.11.3
If upgrading from InfluxDB Enterprise v1.11.3+ to {{< latest-patch >}}, you can now configure whether or not InfluxDB compacts series files on startup using the
compact-series-fileconfiguration option in your InfluxDB Enterprise data node configuration file.
[!Note]
Series file compaction
With InfluxDB Enterprise v1.11.4+, InfluxDB can be configured to optionally compact series files before data nodes are started. Series files are stored in
_seriesdirectories inside the InfluxDB data directory. Default:/var/lib/data/<db-name>/_series.To compact series files on startup, set the
compact-series-fileconfiguration option totruein your InfluxDB Enterprise data node configuration file.
- If any series files are corrupt, the
influx_inspectorinfluxdprocesses on the data node may fail to start. In both cases, delete the series file directories before restarting the database. InfluxDB automatically regenerates the necessary series directories and files when restarting.- To check if series files are corrupt before starting the database, run the
influx_inspect verify-seriesfilecommand while the database is off-line.- If series files are large (20+ gigabytes), it may be faster to delete the series file directories before starting the database.
compact-series-file configuration setting to optionally execute
series compaction during startup.[!Important]
Series file compaction on startup
With InfluxDB Enterprise v1.11.3, on startup, InfluxDB runs the
influxd_inspect -compact-series-filecommand to compact series files before data nodes are started. Series files are stored in_seriesdirectories inside the InfluxDB data directory. Default:/var/lib/data/<db-name>/_series
- InfluxDB Enterprise v1.11.4+ introduces a configuration setting to optionally compact series on startup.
- If any series files are corrupt, the
influx_inspectorinfluxdprocesses on the data node may fail to start. In both cases, delete the series file directories and rebuild the indexes before restarting the database. InfluxDB automatically regenerates the deleted series files when the database restarts.- To check if series files are corrupt before starting the database, run the
influx_inspect verify-seriesfilecommand while the database is off-line.- If series files are large (20+ gigabytes), it may be faster to delete the series file directories before starting the database.
DIGESTS.tag for each release.golang.org/x/crypto version to match go.mod./debug/vars.iox.sqlInterval().onNonmonotonic parameter to histogramQuantile()
to define behavior when bin counts are not monotonically increasing.geo.totalDistance()
to aggregate total distance of consecutive points.iox.sqlInterval() to
convert Flux durations to SQL interval strings.contrib/qxip/hash package which
includes hashing functions.contrib/qxip/logql package
which provides functions for working with
Grafana Loki and LogQL.contrib/qxip/clickhouse
package which provides functions for querying data from Clickhouse.types.isNumeric() to test for numeric values.dynamic.isType() function.dynamic.asArray() function.iox.sql() function.array package.array.from().experimental.unpivot()
for non-field and non-group-key columns.experimental/polyline package for
downsampling data.apiKey parameter in zenoss.event()
and zenoss.endpoint().join package
such as join.full().initialZero parameter
to the derivative function.time(), to the date
package to convert any timeable into datetime.compact-series-file at startup.CIRCLE_TAG to package builder.boringcrypto builds on fresh containers.golang.org/x/crypto/ssh usage.SIGHUP, restart the anti-entropy service and reload configuration.PBKDF2 implementation for FIPS builds.ensure-fips for crypto and TLS implementations on startupSHOW FIELD KEY CARDINALITY metaquery.pkg-config dependency.error or warn where appropriate.golang.org/x/crypto/ssh dependency.pkg/boringutil/xcrypto instead of golang.org/x/crypto for FIPS builds.golang.org/x/crypto/bcrypt dependency from FIPS build.golang.org/x/crypto dependencies.changelogger.go.mod version.changelog_* workflows.digest and influx_tools.index out of range panic in merge cursor process.SHOW MEASUREMENTS.--start and --end backup options to specify the time to include in backup.inflxud-ctl show.preview() to experimental package for limiting return rows and tables (as opposed to just rows with limit()).trace option to Flux CLI.addDuration() to add and subDuration() to sub,
and moved both of these functions from the experimental package to the date package.map().movingAverage() and cumulativeSum() optimizations by default.-shard flag when using the influxd-ctl backup command.verify subcommand no longer appends /data to the -dir flag path parameterInfluxQL queries./debug/vars.influxd config panic.hh_node measurement to the /debug/vars monitoring telemetry. This tracks more accurately with the max-size configuration setting for hinted handoff in data nodes.influxd-ctl restore command to fail.queue is full errors.max series per database exceedederror.error creating subscription message.DROP SHARD now successfully ignores "shard not found" errors.{{% warn %}} An edge case regression was introduced into this version that may cause a constant build-up of hinted handoff if writes are rejected due to malformed requests. If you experience write errors and hinted hand-off growth, we recommend upgrading to 1.9.8 or the latest release. {{% /warn %}}
influxd-ctl restore command to fail.max series per database exceedederror.error creating subscription message.DROP SHARD now successfully ignores "shard not found" errors.[!Note] InfluxDB Enterprise offerings are no longer available on AWS, Azure, and GCP marketplaces. Please contact Sales to request an license key to install InfluxDB Enterprise in your own environment.
Revert damaged meta nodes to a previous state: Add the -meta-only-overwrite-force option to influxd-ctl restore to revert damaged meta nodes in an existing cluster to a previous state when restoring an InfluxDB Enterprise database.
Estimate the size of a backup (full or incremental) and provide progress messages. Add -estimate option to influxd-ctl backup to estimate the size of a backup (full or incremental) and provide progress messages. Prints the number of files to back up, the percentage of bytes transferred for each file (organized by shard), and the estimated time remaining to complete the backup.
Log active queries when a process is terminated: Add the termination-query-log configuration option. When set to true all running queries are printed to the log when a data node process receives a SIGTERM (for example, a Kubernetes process exceeds the container memory limit or the process is terminated).
Log details of HTTP calls to meta nodes. When cluster-tracing is enabled, all API calls to meta nodes are now logged with details providing an audit trail including IP address of caller, specific API being invoked, action being invoked, and more.
protobuf library.influxd config.influxd-ctl entropy commands use the correct TLS settings.influxd-ctl join robustness and provide better error messages on failure.[!Note] InfluxDB Enterprise 1.9.4 was not released. Changes below are included in InfluxDB Enterprise 1.9.5.
SHOW TAG VALUES by retention policy.memUsage metrics to /debug/vars endpoint
to measure memory usage in bytes across all subscriptions.compact-full-write-cold-duration apply to both TSM files and the TSI index.influx_tools import.retry-rate-limit is exceeded.influxd-ctl entropy commands.bcrypt and pbkdf2 support.total-buffer-bytes configuration parameter to subscriptions.
This option is intended to help alleviate out-of-memory errors.DigestWithOptions.yum-compatible names.SHOW SHARDS showing expiration time for shard groups with no expiration.total-max-memory-bytes and other flux controller configuration work correctly.The release of InfluxDB Enterprise 1.9 is different from previous InfluxDB Enterprise releases in that there is no corresponding InfluxDB OSS release. (InfluxDB 1.8.x will continue to receive maintenance updates.)
SHOW SERIES CARDINALITY and SHOW SERIES CARDINALITY from <measurement> InfluxQL queries.
These queries now return a cardinality estimation column header where before they returned count.debug/vars metrics.to function.WITH KEY to SHOW TAG KEYS.show databases now checks read and write permissions.tsm1.BlockCount() call to match signature.entropy show expiration times consistent with show-shards.User-Agent to allowed CORS headers./debug/vars.snapshotter.influx_inspect.PATCH in CORS.GROUP BY returning multiple results per group in some circumstances.[start, stop] instead of [start, stop)).context.Context value in client.fields.idx unnecessarily.influx_stress tool (deprecated since version 1.2).
Instead, use inch
or influx-stress (not to be confused with influx_stress).[!Note] InfluxDB Enterprise 1.9.0 and 1.9.1 were not released. Bug fixes intended for 1.9.0 and 1.9.1 were rolled into InfluxDB Enterprise 1.9.2.
{{% warn %}} Fine-grained authorization security update. If using InfluxDB Enterprise 1.8.5, we strongly recommend upgrading to InfluxDB Enterprise 1.8.6 immediately. 1.8.5 does not correctly enforce grants with specified permissions for users. Versions prior to InfluxDB Enterprise 1.8.5 are not affected. 1.8.6 ensures that only users with sufficient permissions can read and write to a measurement. {{% /warn %}}
level="debug") in the data node configuration, the Anti-Entropy service reports reasons a shard is not idle, including:
copy-shard logging. Add information to log messages in copy-shard functions and additional error tests.copy-shard copy-shard-status kill-copy-shard remove-shardDiffIterator.Next(). Update to check before possible function exit and ensure handles are closed on error in digest diffs.The InfluxDB Enterprise v1.8.5 release builds on the InfluxDB OSS v1.8.5 release. For details on changes incorporated from the InfluxDB OSS release, see InfluxDB OSS release notes.
influxd_ctl entropy show now shows shard expiry times consistent with influxd_ctl show-shardsThe InfluxDB Enterprise 1.8.4 release builds on the InfluxDB OSS 1.8.4 release. For details on changes incorporated from the InfluxDB OSS release, see InfluxDB OSS release notes.
Note: InfluxDB Enterprise 1.8.3 was not released. Bug fixes intended for 1.8.3 were rolled into InfluxDB Enterprise 1.8.4.
Add the ability to renew or update your license key or file without restarting data nodes.
influxd-ctl show shards.control.Shard.Err.The InfluxDB Enterprise 1.8.2 release builds on the InfluxDB OSS 1.8.2 and 1.8.1 releases. Due to a defect in InfluxDB OSS 1.8.1, InfluxDB Enterprise 1.8.1 was not released. This release resolves the defect and includes the features and bug fixes listed below. For details on changes incorporated from the InfluxDB OSS release, see InfluxDB OSS release notes.
allow-out-of-order-writes to the [cluster] section of the data node configuration file. This setting defaults to false to match the existing behavior. There are some important operational considerations to review before turning this on. But, the result is enabling this option reduces the time required to drain the hinted handoff queue and increase throughput during recovery. See allow-out-of-order-writes for more detail.[hinted-handoff] section called max-pending-writes, which defaults to 1024. See max-pending-writes for more detail.influxd-ctl CLI improvementsinfluxd-ctl show-shards. This option provides more information about each shard owner, including the state (hot/cold), last modified date and time, and size on disk.GroupSearchBaseDNs, SearchFilter, GroupMembershipSearchFilter, and GroupSearchFilter values in the LDAP section of the configuration file are now all escaped.processCreateShardSnapshotRequest() and provide useful log information regarding the reason a temporary directory is created.The InfluxDB Enterprise 1.8 release builds on the InfluxDB OSS 1.8 release. For details on changes incorporated from the InfluxDB OSS release, see InfluxDB OSS release notes.
Add option to back up meta data only (users, roles, databases, continuous
queries, and retention policies) using the new -strategy flag and only meta
option: influx ctl backup -strategy only meta </your-backup-directory>.
[!Note] To restore a meta data backup, use the
restore -fullcommand and specify your backup manifest:influxd-ctl restore -full </backup-directory/backup.manifest>.
For more information, see Perform a metastore only backup.
incremental and full backup options to the new -strategy flag in influx ctl backup:
influx ctl backup -strategy incrementalinflux ctl backup -strategy fullFor more information, see the influxd-ctl backup syntax.
The InfluxDB Enterprise 1.7.10 release builds on the InfluxDB OSS 1.7.10 release. For details on changes incorporated from the InfluxDB OSS release, see InfluxDB OSS release notes.
MaxShardGroupID on meta update.The InfluxDB Enterprise 1.7.9 release builds on the InfluxDB OSS 1.7.9 release. For details on changes incorporated from the InfluxDB OSS release, see InfluxDB OSS release notes.
tsdb store open to beginning of server initialization.{{% warn %}} InfluxDB now rejects all non-UTF-8 characters. To successfully write data to InfluxDB, use only UTF-8 characters in database names, measurement names, tag sets, and field sets. InfluxDB Enterprise customers can contact InfluxData support for more information. {{% /warn %}}
The InfluxDB Enterprise 1.7.8 release builds on the InfluxDB OSS 1.7.8 release. For details on changes incorporated from the InfluxDB OSS release, see InfluxDB OSS release notes.
influxd-ctl error message when the Anti-Entropy (AE) service is disabled.INFLUXDB_LOGGING_LEVEL if misconfigured.The InfluxDB Enterprise 1.7.7 release builds on the InfluxDB OSS 1.7.7 release. For details on changes incorporated from the InfluxDB OSS release, see InfluxDB OSS release notes.
Println statement introduced in this release. For a possible workaround, see https://github.com/influxdata/influxdb/issues/14265#issuecomment-508875853. Next month's maintenance release will address this issue.This InfluxDB Enterprise release builds on the InfluxDB OSS 1.7.6 release. For details on changes incorporated from the InfluxDB OSS release, see InfluxDB OSS release notes.
{{% warn %}}
If you are currently on this release, roll back to v1.7.4 until a fix is available.
After upgrading to this release, some customers have experienced regressions, including parentheses being removed resulting in operator precedence causing changing results in complex queries and regular expressions.
Examples:
WHERE d > 100 AND (c = 'foo' OR v = 'bar').(a AND b) OR c instead of a AND (b OR c){{% /warn %}}
This InfluxDB Enterprise release builds on the InfluxDB OSS 1.7.5 release. For details on changes incorporated from the InfluxDB OSS release, see InfluxDB OSS release notes.
influx_tools utility (for internal support use) to be part of the packaging.contains no .tsm files error.fix(cluster): account for nil result set when writing read response.This InfluxDB Enterprise release builds on the InfluxDB OSS 1.7.4 release. For details on changes incorporated from the InfluxDB OSS release, see InfluxDB OSS release notes.
systemd for Amazon Linux 2.This InfluxDB Enterprise release builds on the InfluxDB OSS 1.7.3 release. For details on changes incorporated from the InfluxDB OSS release, see the InfluxDB OSS release notes.
If you have not installed this release, then install the 1.7.4 release.
If you are currently running this release, then upgrade to the 1.7.4 release as soon as possible.
A critical defect in the InfluxDB 1.7.3 release was discovered and our engineering team fixed the issue in the 1.7.4 release. Out of high concern for your data and projects, upgrade to the 1.7.4 release as soon as possible.
A small percentage of customers experienced data node crashes with segmentation violation errors. We fixed this issue in 1.7.4.
Prior to v.1.7.3, the anti-entropy (AE) service was enabled by default. When shards create large digests with lots of time ranges (10s of thousands), some customers experienced significant performance issues, including CPU usage spikes. If your shards include a small number of time ranges (most have 1 to 10, some have up to several hundreds) and you can benefit from the AE service, then you can enable AE and watch to see if performance is significantly impacted.
DistinctCount, min, & max time.This release only includes the InfluxDB OSS 1.6.6 changes (no Enterprise-specific changes).
This release builds off of the InfluxDB OSS 1.6.0 through 1.6.5 releases. For details about changes incorporated from InfluxDB OSS releases, see InfluxDB OSS release notes.
This release builds off of the InfluxDB OSS 1.6.0 through 1.6.4 releases. For details about changes incorporated from InfluxDB OSS releases, see the InfluxDB OSS release notes.
internal-shared-secret if meta auth enabledIf [meta] auth-enabled is set to true, the [meta] internal-shared-secret value must be set in the configuration.
If it is not set, an error will be logged and influxd-meta will not start.
internal-shared-secret. The security risk was that an unset (empty) value could be used for the internal-shared-secret, seriously weakening the JWT authentication used for internode communication.The Production Installation
documentation has been updated to fix errors in configuration settings, including changing shared-secret to internal-shared-secret and adding missing steps for configuration settings of data nodes and meta nodes. All Enterprise users should review their current configurations to ensure that the configuration settings properly enable JWT authentication for internode communication.
The following summarizes the expected settings for proper configuration of JWT authentication for internode communication:
influxdb.conf)[http] section
auth-enabled = true
[meta] section
meta-auth-enabled = true
[meta] auth-enabled settings.meta-internal-shared-secret = "<long-pass-phrase>"
[meta] internal-shared-secret settings."".meta-influxdb.conf)[meta] section
auth-enabled = true
false .internal-shared-secret = "<long-pass-phrase>"
[meta] meta-internal-shared-secret
settings."".[!Note] To provide encrypted internode communication, you must enable HTTPS. Although the JWT signature is encrypted, the the payload of a JWT token is encoded, but is not encrypted.
influxd-ctl update-data from one existing host to another.internal-shared-secret if meta auth enabled.This release builds off of the InfluxDB OSS 1.6.0 through 1.6.2 releases. For details about changes incorporated from InfluxDB OSS releases, see the InfluxDB OSS release notes.
1.10./status endpoint.This release builds off of the InfluxDB OSS 1.5.4 release. Please see the InfluxDB OSS release notes for more information about the InfluxDB OSS release.
This release builds off of the InfluxDB OSS 1.5.3 release. Please see the InfluxDB OSS release notes for more information about the InfluxDB OSS release.
This release builds off of the InfluxDB OSS 1.5.2 release. Please see the InfluxDB OSS release notes for more information about the InfluxDB OSS release.
This release builds off of the InfluxDB OSS 1.5.1 release. There are no Enterprise-specific changes. Please see the InfluxDB OSS release notes for more information about the InfluxDB OSS release.
[!Note] This release builds off of the 1.5 release of InfluxDB OSS. Please see the InfluxDB OSS release notes for more information about the InfluxDB OSS release.
For highlights of the InfluxDB 1.5 release, see What's new in InfluxDB 1.5.
The default logging format has been changed. See Logging and tracing in InfluxDB for details.
LastModified fields to shard RPC calls./repair endpoint and update Swagger doc.SHOW TAG VALUESSHOW TAG KEYS with time supportrpc error: i/o deadline exceeded errors.stream closed error from logs and handle io.EOF as remote iterator interrupt.digest.merge(meta.UserInfo).acl)X-Influxdb-Build to http response headers so users can identify if a response is from an InfluxDB OSS or InfluxDB Enterprise service.cluster-tracing config option to enable meta HTTP request logging.influxd-ctl restore -newdb can't restore data.Len() in connection pool.yamux. This update reduces overall memory usage when streaming large amounts of data.createdatabase permissionIf you have been using the TSI preview with 1.3.6 or earlier 1.3.x releases, you will need to follow the upgrade steps to continue using the TSI preview. Unfortunately, these steps cannot be executed while the cluster is operating -- so it will require downtime.
stream closed error from logs and handle io.EOF as remote iterator interrupt.rpc error: i/o deadline exceeded errorspartial write errors to hinted handoff.If you have been using the TSI preview with 1.3.6 or earlier 1.3.x releases, you will need to follow the upgrade steps to continue using the TSI preview. Unfortunately, these steps cannot be executed while the cluster is operating -- so it will require downtime.
yamux resolves race condition when SYN is successfully sent and a write timeout occurs.rpc error: i/o deadline exceeded errors.The 1.3.7 release resolves a defect that created duplicate tag values in TSI indexes See Issues #8995, and #8998. However, upgrading to 1.3.7 cause compactions to fail, see Issue #9025. We will provide a utility that will allow TSI indexes to be rebuilt, resolving the corruption possible in releases prior to 1.3.7. If you are using the TSI preview, you should not upgrade to 1.3.7 until this utility is available. We will update this release note with operational steps once the utility is available.
This release builds off of the 1.3.5 release of OSS InfluxDB. Please see the OSS release notes for more information about the OSS releases.
This release builds off of the 1.3.4 release of OSS InfluxDB. Please see the OSS release notes for more information about the OSS releases.
This release builds off of the 1.3.3 release of OSS InfluxDB. Please see the OSS release notes for more information about the OSS releases.
CreateRemoteIterator RPC returns no iterators, resolved memory leakinfluxd-ctl restore -newdb unable to restore data.SHOW TAG VALUES.SHOW DIAGNOSTICS.[cluster] Sectionmax-remote-write-connections is deprecated and can be removed.pool-max-idle-streams and pool-max-idle-time configure the RPC connection pool.
See config.sample.toml for descriptions of these new options.The admin UI is removed and unusable in this release. The [admin] configuration section will be ignored.
influxd-ctl's copy-shard-status argument human readable.influxd-ctl remove-data -force.This release builds off of the 1.2.4 release of OSS InfluxDB. Please see the OSS release notes for more information about the OSS releases.
ALTER RETENTION POLICY query does not update the default retention policy.partial write are considered droppable.influxd-ctl remove-data -force command.This release builds off of the 1.2.1 release of OSS InfluxDB. Please see the OSS release notes for more information about the OSS release.
The following configuration changes may need to changed before upgrading to 1.2.2 from prior versions.
We've removed the data node's shard-writer-timeout configuration option from the [cluster] section.
As of version 1.2.2, the system sets shard-writer-timeout internally.
The configuration option can be removed from the data node configuration file.
In versions 1.2.0 and 1.2.1, the retention-autocreate setting appears in both the meta node and data node configuration files.
To disable retention policy auto-creation, users on version 1.2.0 and 1.2.1 must set retention-autocreate to false in both the meta node and data node configuration files.
In version 1.2.2, we’ve removed the retention-autocreate setting from the data node configuration file.
As of version 1.2.2, users may remove retention-autocreate from the data node configuration file.
To disable retention policy auto-creation, set retention-autocreate to false in the meta node configuration file only.
This change only affects users who have disabled the retention-autocreate option and have installed version 1.2.0 or 1.2.1.
shard not found error by making backups skip empty shardsshard not found error by making restore handle empty shards-db or rp flags) to be stores in the same directorySHOW TAG VALUES query even if the cluster includes an unreachable data nodeSHOW MEASUREMENTS query even if the cluster includes an unreachable data noderetryCAS code to wait for a newer snapshot before retryinginfluxd-ctl's join argument from completing a join when the command also specifies the help flag (-h)influxd-ctl's force removal of meta nodesThis release builds off of the 1.2.0 release of OSS InfluxDB. Please see the OSS release notes for more information about the OSS release.
retention-autocreate configuration option has moved from the meta node configuration file to the data node configuration file.
To disable the auto-creation of retention policies, set retention-autocreate to false in your data node configuration files.influxd-ctl force-leave command has been removed. The replacement command to remove a meta node which is never coming back online is influxd-ctl remove-meta -force.dir) from the backendmax-values-per-tag errorsinfluxd-ctl force-leave commandinfluxd-ctl show-shardsExecuteStatementRequestMessageThis release incorporates the changes in the 1.1.4 release of OSS InfluxDB. Please see the OSS changelog for more information about the OSS release.
GOMAXPROCS environment variable.This release was an internal release only. It incorporates the changes in the 1.1.3 release of OSS InfluxDB. Please see the OSS changelog for more information about the OSS release.
This release builds off of the 1.1.1 release of OSS InfluxDB. Please see the OSS release notes for more information about the OSS release.
This release is built with Go (golang) 1.7.4. It resolves a security vulnerability reported in Go (golang) version 1.7.3 which impacts all users currently running on the macOS platform, powered by the Darwin operating system.
This release builds off of the 1.1.0 release of InfluxDB OSS. Please see the OSS release notes for more information about the OSS release.
influxd-ctl join command has been renamed to influxd-ctl add-meta. If you have existing scripts that use influxd-ctl join, they will need to use influxd-ctl add-meta or be updated to use the new cluster setup command.The influxd-ctl join command has been changed to simplify cluster setups. To join a node to a cluster, you can run influxd-ctl join <meta:8091>, and we will attempt to detect and add any meta or data node process running on the hosts automatically. The previous join command exists as add-meta now. If it's the first node of a cluster, the meta address argument is optional.
Switches to journald logging for on systemd systems. Logs are no longer sent to /var/log/influxdb on systemd systems.
queueBytes to the hh_processor statisticsinfluxd-ctl show outputinfluxd-ctl show
Fixes any confusion between the correct command for showing detailed shard information (influxd-ctl show-shards) and the incorrect command (influxd-ctl show shards)/show-shards outputpprof-enabled configuration setting and enable it by default on meta nodespprof-enabled configuration setting on data nodesClone() during read-only operations for performance purposesErrNotLeader errorcopy-shard from retrying if the copy-shard command was killedinfluxd-ctl add-data command by making data nodes check for meta nodes before they join a clusterlastModifiedThis release builds off of the 1.0.2 release of OSS InfluxDB. Please see the OSS release notes for more information about the OSS release.
systemctl enable would throw an error if the symlink already existsThis release builds off of the 1.0.1 release of OSS InfluxDB. Please see the OSS release notes for more information about the OSS release.
runtime error: invalid memory address or nil pointer dereferenceruntime error: makeslice: len out of rangeThis release builds off of the 1.0.0 release of OSS InfluxDB. Please see the OSS release notes for more information about the OSS release.
Breaking Changes:
IF, EXISTS, and NOT were removed for this release. This means you no longer need to specify IF NOT EXISTS for DROP DATABASE or IF EXISTS for CREATE DATABASE. Using these keywords will return a query error.max-series-per-database was added with a default of 1M but can be disabled by setting it to 0. Existing databases with series that exceed this limit will continue to load, but writes that would create new series will fail.A number of changes to hinted handoff are included in this release:
SHOW MEASUREMENTS and SHOW TAG VALUES have been optimized to work better for multiple nodes and shardsDROP and DELETE statements run in parallel and more efficiently and should not leave the system in an inconsistent stateThe Cluster API used by influxd-ctl can not be protected with SSL certs.
Data nodes that can no longer be restarted can now be forcefully removed from the cluster using influxd-ctl remove-data -force <addr>. This should only be run if a grace removal is not possible.
Backup and restore has been updated to fix issues and refine existing capabilities.
-force option to the influxd-ctl remove-data commandstats service queriesSHOW MEASUREMENTS and SHOW TAG VALUES queriesmax-select-series is respectedpeer already known errorThe Enterprise Web Console has officially been deprecated and will be eliminated entirely by the end of 2017. No additional features will be added and no additional bug fix releases are planned.
For browser-based access to InfluxDB Enterprise, Chronograf is now the recommended tool to use.