[
https://issues.apache.org/jira/browse/CASSANDRA-10404?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16222343#comment-16222343
]
Jason Brown commented on CASSANDRA-10404:
-----------------------------------------
bq. add a simple config validation in DatabaseDescriptor and throw a
ConfigurationException in case cassandra.yaml hasn't been updated correctly
during the upgrade
Done, and pushed up a commit
Also, I discovered a long dead config entry, {{Config#encryption_options}}.
Apparently, I deprecated that 5 years ago as part of CASSANDRA-4239 as it was
renamed to {{Config#server_encryption_options}}. Thus, I've removed it and the
{{DatabaseDescriptor}} check, as well. I knew someday I'd come back to get it!
[[email protected]] If the code is at this point, I'll move on to fixing up the
yaml comments and NEWS.txt. I'd like to create a separate ticket for updating
the docs page as I'd like to expand it, a lot. wdyt?
> Node to Node encryption transitional mode
> -----------------------------------------
>
> Key: CASSANDRA-10404
> URL: https://issues.apache.org/jira/browse/CASSANDRA-10404
> Project: Cassandra
> Issue Type: New Feature
> Reporter: Tom Lewis
> Assignee: Jason Brown
> Fix For: 4.x
>
>
> Create a transitional mode for encryption that allows encrypted and
> unencrypted traffic node-to-node during a change over to encryption from
> unencrypted. This alleviates downtime during the switch.
> This is similar to CASSANDRA-10559 which is intended for client-to-node
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
