Falcon LogScale 1.157.0 GA (2024-09-24)
Version? | Type? | Release Date? | Availability? | End of Support | Security Updates | Upgrades From? | Config. Changes? |
---|---|---|---|---|---|---|---|
1.157.0 | GA | 2024-09-24 | Cloud | Next LTS | No | 1.112 | No |
Bug fixes and updates.
Deprecation
Items that have been deprecated and may be removed in a future release.
The lastScheduledSearch field from the
ScheduledSearch
datatype is now deprecated and planned for removal in LogScale version 1.202. The new lastExecuted and lastTriggered fields have been added to theScheduledSearch
datatype to replace lastScheduledSearch.The deprecated JDK-less
server.tar.gz
tarball release is no longer being published. Users should switch to eitherserver-linux_x64.tar.gz
orserver-alpine_x64.tar.gz
depending on their operating system.
Behavior Changes
Scripts or environment which make use of these tools should be checked and updated for the new configuration:
Storage
LogScale now avoids moving merge targets to the digest leader during digest reassignment if those segments are already in Bucket Storage.
During digest reassignment, LogScale will now ignore minisegments in Bucket Storage when deciding whether to switch merge targets because some minisegments are not present locally. This should slightly reduce the load on Global Database during digest reassignment.
Allow live query updates to run on a new thread pool
digestLive
, but only for datasources that spend more time on these updates than allowed in the digester pool on live queries, or for many datasources, if their total load exceeds time available for digesters. This frees up time for the digesters, provided there is available CPU on the node.LogScale now avoids moving minisegments to follow the digest nodes if the minisegments are available in Bucket Storage. Instead, minisegments will now be fetched as needed, when the digest leader is ready to merge them. This reduces the load on Global Database in some cases following a digest reassignment.
New features and improvements
GraphQL API
Field aliases now have API support for being exported and imported as YAML.
Fixed in this release
Dashboards and Widgets
Newline characters would not be escaped in the dashboard parameter input field, thus appearing as not being part of the value. This issue has now been fixed.
Queries
Stopping queries that use early stopping criteria were wrongly reported as
Cancelled
instead ofDone
. The query status has now been fixed.
Other
Off-heap memory limiting might not apply correctly.
Known Issues
Queries
Improvement
Ingestion
Data ingest rate monitoring has been adjusted to ensure it reports from nodes across all node roles. Additionally, the number of nodes reporting in large clusters has been raised.
Queries
Some internal improvements have been made to query coordination to make it more robust in certain cases — in particular with failing queries — with an impact on the timing of some API responses.