Release Announcement: InfluxDB OSS and InfluxDB Enterprise 1.8.6 

Navigate to:

A new maintenance release for both InfluxDB OSS and InfluxDB Enterprise are available now.

There are no specific improvements within InfluxDB OSS 1.8.6. We re-built the OSS edition to pair with the InfluxDB Enterprise edition.

CRITICAL SECURITY ISSUE

For InfluxDB Enterprise customers, please review the following.

If you are using the fine-grained authorization feature AND you have upgraded to InfluxDB Enterprise 1.8.5, it is critical that you upgrade to this release as soon as possible. An issue was reported in 1.8.5 where grants with specified permissions for users were not enforced. Versions prior to InfluxDB Enterprise 1.8.5 are not affected. This security update ensures that only users with sufficient permissions can read and write to a measurement.

InfluxDB Enterprise 1.8.6

This maintenance release of InfluxDB Enterprise on the 1.8 line builds upon the InfluxDB OSS 1.8.6 release. For the InfluxDB Enterprise 1.8.6 release, a number of Enterprise specific issues and improvements have been delivered. In addition to the fine-grained access issue described above, this release includes the following defect fixes:

  • Logging Improvements
    • When debug-level logging is set in the data node configuration, the Anti-Entropy service now reports reasons a shard is not idle, including:
      • active Cache compactions
      • active Level (Zero, One, Two) compactions
      • active Full compactions
      • active TSM Optimization compactions
      • cache size is nonzero
      • shard is not fully compacted
    • We also added information to log messages in copy-shard functions and additional error tests.
  • Other defect fixes
    • The proper TLS configuration is now used when a meta node makes a remote procedure call (RPC) to a data node. This fix addresses RPC call issues using the following influxd-ctl commands: copy-shard copy-shard-status kill-copy-shard  remove-shard
    • Previously, the Anti-Entropy service would loop trying to copy an empty shard to a data node missing that shard. Now, an empty shard is successfully created on a new node.
    • Again, the binaries for the latest open source release can be found on our downloads page.

For our InfluxDB Enterprise customers, log in to the InfluxDB Enterprise portal and download the binaries from there.  If you need more help?  Contact support.

If you find issues or have questions, please join our InfluxDB Community Slack, post them in our InfluxDB GitHub Repo or our Community Site and we will take a look.