Release Announcement: InfluxDB OSS 1.7.10

Navigate to:

A new maintenance release for InfluxDB OSS is available now.

This maintenance release of InfluxDB OSS includes the following fixes:

  • Fix to address corrupt TSM data file renaming failure. When the InfluxDB engine detects a corrupt TSM data file upon startup, the renaming of that file was failing due to a file lock on the data file created by the engine itself.  
  • Concurrent calls to tsm1.Engine.Digest() result in a Digest aborted, problem renaming tmp digest error message. Delivered fix makes digest safe for concurrent use.
  • Fixed a defect in the TSI1 index where a filter using the negated equality (!=) operator could result in no matching series being returned for any series stored within the IndexFile portions of the index.
  • Fixed compaction logic on infrequent cache snapshots. If the cache snapshot was occurring at a frequency longer than than specified by the compact-full-write-cold-duration,  a full compaction would be triggered despite newer data which remained in the cache snapshot. This fix ensures that the documented compaction behavior is followed.
  • Addressed an issue where multiple blocks for the same series key were having values truncated when they were being read into an empty buffer. The cursor reader code had an optimization that incorrectly assumed the incoming array will be limited to 1,000 values (the maximum block size), but arrays can contain values from multiple matching blocks for the same index entry. Therefore, it's possible for the array being read to have more than 1,000 values and not fit entirely into the buffer. 
  • Skip TSM files with block read errors — when InfluxDB finds a bad TSM file during compaction, the error is now logged and the bad file is moved aside. The engine will disregard the file so the next compaction will not hit the same error.

The binaries for the latest open source release can be found on our downloads page.

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.