I am doing post-mortem on an issue with our cassandra cluster. One of our tables became corrupt and had to be restored via a backup. The table schema has been undergoing active development, so the number of "alter table" statements was quite large (300+). Currently, we use cqlsh to do schema loads. During the restore, the schema load alone took about 4 hours.
Our DBAs report that even under normal conditions they send alter table statements in small chunks or else the will see load times of 20-45 minutes. My question is two part. First, is cqlsh the best way to handle these types of loads? Second, any ideas what could be creating bottlenecks for schema alteration? Thanks! -- Mark Bidewell http://www.linkedin.com/in/markbidewell
