DSE 6.8.44 release notes #138
Conversation
DSE_6.8_Release_Notes.md
Outdated
| * Fixed nodetool viewbuildstatus to query the responsible replica. It prevents returning unknown status when system_distributed RF is smaller than the number of nodes in the cluster. (DSP-23806) | ||
|
|
||
| ## 6.8.44 DSE CVE | ||
| * Added possibility to close/block connection per role by specifying {{connection_idle_timeout_seconds}} and {{connection_idle_behavior}} via a role custom options. (DSP-23951) |
There was a problem hiding this comment.
| * Added possibility to close/block connection per role by specifying {{connection_idle_timeout_seconds}} and {{connection_idle_behavior}} via a role custom options. (DSP-23951) | |
| * Added possibility to close/block connection per role by specifying `connection_idle_timeout_seconds` and `connection_idle_behavior` via a role custom options. (DSP-23951) |
DSE_6.8_Release_Notes.md
Outdated
| * Added support for AWS Ec2 IMDSv2. Please beware that if you use Ec2Snitch or Ec2MultiRegionSnitch, by default it will communicate with AWS IMDS of version 2. This change is transparent, there does not need anything done upon upgrade. Furthermore, IMDS of version 2 can be configured to be required in AWS EC2 console. Consult cassandra-rackdc.properties for more details. (DSP-23995) | ||
| * Fixed nodetool viewbuildstatus to query the responsible replica. It prevents returning unknown status when system_distributed RF is smaller than the number of nodes in the cluster. (DSP-23806) | ||
|
|
||
| ## 6.8.44 DSE CVE |
There was a problem hiding this comment.
Likely DSE Security would be a more appropriate section for DSP-23951
DSE_6.8_Release_Notes.md
Outdated
| ## 6.8.44 DSE Search | ||
| * Fixed Solr credentials parsing. (DSP-24102) | ||
|
|
||
| ## 6.8.44 DSE Miscellaneous |
There was a problem hiding this comment.
It seems the release notes script wasn't able to figure out the most appropriate category for the below two tickets based on the Components field. I think both of these tickets would be a better fit for DSE Cassandra category.
There was a problem hiding this comment.
There's a warning when running release-notes-generator for when no component is matched. In cases like these we should fix the Jira issue and then re-generate the Release Notes.
DSE_6.8_Release_Notes.md
Outdated
| * Fixed Solr credentials parsing. (DSP-24102) | ||
|
|
||
| ## 6.8.44 DSE Miscellaneous | ||
| * Added support for AWS Ec2 IMDSv2. Please beware that if you use Ec2Snitch or Ec2MultiRegionSnitch, by default it will communicate with AWS IMDS of version 2. This change is transparent, there does not need anything done upon upgrade. Furthermore, IMDS of version 2 can be configured to be required in AWS EC2 console. Consult cassandra-rackdc.properties for more details. (DSP-23995) |
There was a problem hiding this comment.
I believe there are some subtle wording improvements to make in this release note. How about we try the following:
Added support for AWS EC2 IMDSv2. Please beware that if you use Ec2Snitch or Ec2MultiRegionSnitch, by default it will communicate with AWS IMDSv2. This change is transparent and does not need anything done upon upgrade. Furthermore, IMDSv2 can be configured to be required in AWS EC2 console. Consult cassandra-rackdc.properties for more details.
?
I am also wondering about the meaning and necessity of the following part Furthermore, IMDSv2 can be configured to be required in AWS EC2 console.
There was a problem hiding this comment.
the second statement is related to the fact that EC2 IMDSv2 is 2 parts: once in dse and we mentioned how to use it, second is in AWS. Probably the statement is not necessary since whoever needs this property will know the AWS part.
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:
Version supports 3 sets or 4 sets of digits.