You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Previously, every configuration option set in a CCM cluster would
get passed as a separate call to "ccm updateconf". After
scylladb/scylla-ccm#410 was merged, this way stopped working correctly
as it seems like only the first "ccm updateconf" was correctly applied.
Moreover, during the investigation of the issue, it was found that
in case of Scylla, "ccm updateconf client_encryption_options.[OPTION]"
wouldn't get properly filled in (even before scylladb/scylla-ccm#410),
as only a single option from "client_encryption_options.*"
would get persisted.
This change fixes the issue by not issuing separate "ccm updateconf",
but by collecting all configuration options and batching them to
a single "ccm updateconf" call. This follows the implementation in
Java Driver 3.x.
0 commit comments