Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

OpsCenter 6.8.35 Release #134

Merged
merged 2 commits into from
Mar 25, 2024
Merged

OpsCenter 6.8.35 Release #134

merged 2 commits into from
Mar 25, 2024

Conversation

vimal-ds
Copy link
Contributor


Release Notes Automation

If you name your pull-request as "Product x.y.z Release ...", after merging the
PR, a GitHub Action will automatically create a product version tag "product-x.y.z".

Supported product names are:

  • DSE
  • OpsCenter
  • Studio
  • Luna Streaming

Version supports 3 sets or 4 sets of digits.

# Release Notes for OpsCenter 6.8.34
22 Feb 2024

## Core
* 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` an alert will be triggered if *opscenterd* is unable to make a cql connection to the storage cluster. (OPSC-17488)
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Modified this based on request from support
https://datastax.slack.com/archives/C13QK690C/p1710918069041959

@vimal-ds vimal-ds force-pushed the opscenter-6.8.35-release branch from d62e987 to fa1f57b Compare March 22, 2024 10:24
# Release Notes for OpsCenter 6.8.34
22 Feb 2024

## Core
* 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` an alert will be triggered if *opscenterd* is unable to make a cql connection to the storage cluster. (OPSC-17488)
* Added `heartbeat_warn_window` to the `[failover]` section of the `opscenterd.conf`. When set to non zero integer value (seconds), Backup OpsCenter triggers an alert 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)
* 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)

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
* 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)
* 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 configuration. A setting of `true` triggers a message in the backup opscenter logs when *opscenterd* is unable to make a cql connection to the storage cluster. (OPSC-17488)

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Spelling out abbreviation and fixed grammar.

Copy link

@annieden annieden left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Approved with suggestion applied.

@vimal-ds vimal-ds merged commit 15cf7b9 into master Mar 25, 2024
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)
Copy link
Collaborator

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)

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

ok

@msmygit msmygit deleted the opscenter-6.8.35-release branch March 25, 2024 11:31
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants