OpsCenter 6.8.35 Release #134
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change | ||||
|---|---|---|---|---|---|---|
| @@ -1,11 +1,31 @@ | ||||||
| # Release notes for OpsCenter | ||||||
|
|
||||||
| # Release Notes for OpsCenter 6.8.35 | ||||||
| 22 Mar 2024 | ||||||
|
|
||||||
| ## Backup Service | ||||||
| * Fixed an issue with PIT restore when there is a schema mismatch. Added {{force_schema}} parameter to PIT Restore API to solve this issue. (OPSC-17486) | ||||||
| * Fixed the backup process to run post-backup script after the snapshot files are synchronised to the destinations (OPSC-17483) | ||||||
| * Fixed backup activity API memory and timeout issues using parameter {{backup_activity_query_batch_size}} configurable in {{[backup]}} section. (OPSC-17496) | ||||||
|
|
||||||
| ## Monitoring | ||||||
| * Fixed an issue in diagnostic tarball generation to use {{dse client-tool}} instead of {{dsetool}} to list output for {{sparkmaster}}. Removed the deprecated {{listjt}} file. (OPSC-11798) | ||||||
|
|
||||||
| ## Provisioning | ||||||
| * Added option to configure truststore location through LCM (OPSC-17395) | ||||||
|
|
||||||
| ## UI | ||||||
| * Added {{Materialized View}} restoration progress in the restore dialog. (OPSC-17263) | ||||||
|
|
||||||
| ## Core | ||||||
| * Fixed potential memory leak in the twisted library. (OPSC-17147) | ||||||
|
|
||||||
| # Release Notes for OpsCenter 6.8.34 | ||||||
| 22 Feb 2024 | ||||||
|
|
||||||
| ## Core | ||||||
|
There was a problem hiding this comment. Modified this based on request from support |
||||||
| * Fixed OpsCenter startup failure for customers using a separate storage cluster. Added `alert_on_no_host_available` to the `[storage_cassandra]` section of the cluster conf. When set to `true` triggers a message in the backup opscenter logs if *opscenterd* is unable to make a cql connection to the storage cluster. (OPSC-17488) | ||||||
|
There was a problem hiding this comment.
Suggested change
There was a problem hiding this comment. Spelling out abbreviation and fixed grammar. |
||||||
| * Added `heartbeat_warn_window` to the `[failover]` section of the `opscenterd.conf`. When set to non zero integer value (seconds), Backup OpsCenter triggers a message in the backup opscenter logs if it does not receive heartbeat from Primary OpsCenter in the given window and added `heartbeat_log_level` to the `[failover]` section of the opscenterd conf. When set to one of these values in `info`, `debug`, `trace` primary and backup OpsCenter logs all the heartbeat communication activities at the set level. (OPSC-17388) | ||||||
|
|
||||||
| # Release Notes for OpsCenter 6.8.33 | ||||||
| 15 Feb 2024 | ||||||
|
|
||||||
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
{{force_schema}}won't render properly on GitHub markdown files. Instead, start using it with backticket (i.e. the ` character)There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
ok