-
Notifications
You must be signed in to change notification settings - Fork 24
OPSC-17905 OpsCenter Java driver revert announcement #275
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
Merged
Merged
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or 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,6 +1,14 @@ | ||||||
| # Release notes for OpsCenter | ||||||
|
|
||||||
| # Release Notes for OpsCenter 6.8.50 | ||||||
| Due to numerous errors and customers reporting performance problems with the versions of OpsCenter released with the updated | ||||||
| java driver, we are going to release OpsCenter 6.8.51 with the driver update reverted as soon as possible. We will be removing | ||||||
| the OpsCenter versions with the driver issue and other significant issues from FixCentral. Those are 6.8.47, 6.8.48, 6.8.49, | ||||||
| and 6.8.50. We recommend customers encountering issues go back to 6.8.46 until a fixed version of OpsCenter is released. All | ||||||
| updates since 6.8.46 that are not related to the driver upgrade will remain in place. | ||||||
|
|
||||||
| The OpsCenter team is making significant improvements to the QA process to avoid mistakes like this in the future. | ||||||
|
Contributor
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more.
Suggested change
|
||||||
|
|
||||||
| # (Retracted) Release Notes for OpsCenter 6.8.50 | ||||||
| 13 May 2026 | ||||||
|
|
||||||
| ## Security | ||||||
|
|
@@ -21,7 +29,7 @@ | |||||
| ## Dashboard | ||||||
| * Fixed a regression introduced in the Java Driver 4.x migration where new-metrics requests took several minutes on large clusters. WrappedDriver.prepare() no longer issued a `PREPARE` command to Cassandra, resulting in every metrics query running unprepared and paying full parse + plan cost. Restored proper running of the prepared-statement, and closed a related CqlSession leak during coordinator reconnect. (OPSC-17887) | ||||||
|
|
||||||
| # Release Notes for OpsCenter 6.8.49 | ||||||
| # (Retracted) Release Notes for OpsCenter 6.8.49 | ||||||
| 23 April 2026 | ||||||
|
|
||||||
| ## Backup Service | ||||||
|
|
@@ -57,7 +65,7 @@ | |||||
| ## Monitoring | ||||||
| * Fixed Tiered Storage alerts to handle Java Driver 4.x (OPSC-17794) | ||||||
|
|
||||||
| # Release Notes for OpsCenter 6.8.48 | ||||||
| # (Retracted) Release Notes for OpsCenter 6.8.48 | ||||||
| 5 March 2026 | ||||||
|
|
||||||
| ## Backup Service | ||||||
|
|
@@ -90,7 +98,7 @@ | |||||
| * Fixed an issue where OpsCenter crashed with “index out of range: 1” when agents sent IPs in a single-element list format. (OPSC-17779) | ||||||
| * Fixed an issue where `connection_pool_size` in `opscenterd.conf` was silently ignored after the Java driver 4.x upgrade, causing slowdowns at scale. The setting is now honored for local and remote DC connections. (OPSC-17863) | ||||||
|
|
||||||
| # Release Notes for OpsCenter 6.8.47 | ||||||
| # (Retracted) Release Notes for OpsCenter 6.8.47 | ||||||
| 13 November 2025 | ||||||
|
|
||||||
| ## Monitoring | ||||||
|
|
||||||
Oops, something went wrong.
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.
Uh oh!
There was an error while loading. Please reload this page.
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.
Suggested change