[ https://issues.apache.org/jira/browse/CASSANDRA-18781?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17756933#comment-17756933 ]
Brandon Williams commented on CASSANDRA-18781: ---------------------------------------------- bq. However, for a Cassandra operator, there is no way to forcibly block this behavior. You should probably not expose the storage protocol to users, unless they need to bulk load. The native protocol should be enough for them to do normal things. bq. I am not completely sure how to implement this logic on a server reliably. What we could almost do is add a flag to not allow streaming from non-member nodes, but then bootstrap/replacement are a problem since by definition they are not yet members. But, I feel like properly securing the storage protocol is the best solution. > Add the ability to disable bulk load on server end and add metrics for bulk > load used > ------------------------------------------------------------------------------------- > > Key: CASSANDRA-18781 > URL: https://issues.apache.org/jira/browse/CASSANDRA-18781 > Project: Cassandra > Issue Type: Improvement > Reporter: Runtian Liu > Priority: Normal > > Currently, Cassandra database users can use sstableloader to bulk load data > into Cassandra. However, for a Cassandra operator, there is no way to > forcibly block this behavior. Additionally, there is no metric indicating > whether the bulk load is being used on the server side. If a client is using > sstableloader, they will also need to upgrade the sstableloader code to the > new major version. This lack of control and visibility can become a blocker > during a major version upgrade. > > 1. Can we add a config to disable bulk load feature? Or it falls into > https://issues.apache.org/jira/browse/CASSANDRA-8303 > 2. Can we add metrics for bulk load used on server end? -- 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