If you’re only creating index so that your query work, think again! You’ll be storing secondary index on each node , queries involving index could create issues (slowness!!) down the road the when index on multiple node Is involved and not maintained! Tables involving a lot of inserts/delete could easily ruin index performance.
You can get away the potential situation by leveraging composite key, if that is possible for you? From: techpyaasa . [mailto:techpya...@gmail.com] Sent: Monday, June 19, 2017 1:01 PM To: user@cassandra.apache.org Subject: Secondary Index Hi, I want to create Index on already existing table which has more than 3 GB/node. We are using c*-2.1.17 with 2 DCs , each DC with 3 groups and each group has 7 nodes.(Total 42 nodes in cluster) So is it ok to create Index on this table now or will it have any problem? If its ok , how much time it would take for this process? Thanks in advance, TechPyaasa
