Skip to content

Commit 578595a

Browse files
johnsmartcomsmygit
authored andcommitted
Expand load caveat about Java and Cassandra filters
1 parent f950fde commit 578595a

File tree

1 file changed

+4
-2
lines changed

1 file changed

+4
-2
lines changed

src/resources/cdm-detailed.properties

Lines changed: 4 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -254,8 +254,10 @@ spark.cdm.perfops.ratelimit.target 40000
254254

255255
#===========================================================================================================
256256
# Java Filters are applied on the client node. Data must be pulled from the origin cluster and then filtered,
257-
# but this may have a lower impact on the production cluster than the Cassandra Filters.
258-
# node may need to do a lot more work than is normal.
257+
# but this may have a lower impact on the production cluster than the Cassandra Filters. Java filters put
258+
# load onto the Cassandra Data Migrator processing node, by sending more data from Cassandra.
259+
# Cassandra filters put load on the Cassandra nodes, notably because Cassandra Data Migrator specifies
260+
# ALLOW FILTERING, which could cause the coordinator node to perform a lot more work.
259261
#
260262
# spark.cdm.filter.java
261263
# .token.percent : Percent (between 1 and 100) of the token in each Split that will be migrated.

0 commit comments

Comments
 (0)