Fixed issues
Splunk Enterprise 8.2.0 was released on May 12, 2021. This release includes fixes for the following issues.
Issues are listed in all relevant sections. Some issues might appear more than once.
Data input issues
Date resolved
|
Issue number
|
Description
|
2021-03-04 |
SPL-195024, SPL-195482, SPL-200120, SPL-202918, SPL-202919, SPL-202917 |
sometimes a HEC bundle reload can introduce HEC server DOS.
|
Search issues
Date resolved
|
Issue number
|
Description
|
2021-01-14 |
SPL-196040, SPL-212495 |
Excessive logging of 'Unable to parse site_label, label=invalid due to err="Invalid site id: invalid"' for SearchResultsFiles
|
Saved search, alerting, scheduling, and job management issues
Date resolved
|
Issue number
|
Description
|
2020-10-20 |
SPL-195481, SPL-207587, SPL-207588 |
Users are not able to open 'Advance Edit' feature while editing Alerts
|
Distributed search and search head clustering issues
Date resolved
|
Issue number
|
Description
|
2021-02-16 |
SPL-196300 |
Extremely rare user session management deadlock leading to high thread count and memory usage, and ultimately blocking external communication.
|
Indexer and indexer clustering issues
Date resolved
|
Issue number
|
Description
|
2021-03-11 |
SPL-197930 |
Splunk 8.1.0 post-upgrade indexer high memory usage with tsidxWritingLevel=4
|
2021-02-16 |
SPL-196300 |
Extremely rare user session management deadlock leading to high thread count and memory usage, and ultimately blocking external communication.
|
2021-01-14 |
SPL-196040, SPL-212495 |
Excessive logging of 'Unable to parse site_label, label=invalid due to err="Invalid site id: invalid"' for SearchResultsFiles
|
Distributed deployment, forwarder, deployment server issues
Date resolved
|
Issue number
|
Description
|
2021-02-25 |
SPL-184113, SPL-201518 |
when targetRepositoryLocation is set in a stanza in serverclass.conf, invalid key error is thrown on startup
|
Uncategorized issues
Date resolved
|
Issue number
|
Description
|
2022-02-01 |
SPL-171553, SPL-171647 |
Smartstore: S3 GET is being done before S3 PUT for the receipt.json causing 404 errors (Source peer should not check if the bucket/receipt exists during uploads)
|
2021-02-03 |
SPL-199630, SPL-198659 |
License warning '1 pool warning reported by 1 indexer' comes up on Licensing page
|
Feedback submitted, thanks!