[
https://issues.apache.org/jira/browse/CASSANDRA-19656?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17848742#comment-17848742
]
Brandon Williams commented on CASSANDRA-19656:
----------------------------------------------
bq. Would be supportive of revisiting alternate libs in a future major to avoid
the need to explicitly disable as well.
I am in agreement there, it would be best to not have to do this again. For
now, I have again confirmed nothing is phoning home while capturing packets
during manual tests, unit tests, in-jvm dtests, and the fql and auditlog
python dtests.
[Here|https://github.com/driftx/cassandra/tree/CASSANDRA-19656-5.0] is a branch
that revives my patch from CASSANDRA-18538 to disable in the server options,
and takes [~aweisberg]'s suggestion of also disabling in static init in
DatabaseDescriptor.
If that looks agreeable I will merge up and run CI.
> Revisit disabling chronicle analytics
> -------------------------------------
>
> Key: CASSANDRA-19656
> URL: https://issues.apache.org/jira/browse/CASSANDRA-19656
> Project: Cassandra
> Issue Type: Task
> Components: Local/Other
> Reporter: Brandon Williams
> Assignee: Brandon Williams
> Priority: Normal
> Fix For: 5.0.x, 5.x
>
>
> We first considered this in CASSANDRA-18538 but determined it wasn't a
> problem. We have upgraded chronicle in CASSANDRA-18049 so we should
> reconfirm with packet analysis that nothing is phoning home, and perhaps
> consider taking further precautions by proactively disabling it.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscr...@cassandra.apache.org
For additional commands, e-mail: commits-h...@cassandra.apache.org
