We have noticed that a cluster we upgraded to 1.1.6 (from 1.0.*) still has a
single large (~4GB) row in system.Migrations on each cluster node.
There is some code in there to drop that CF at startup, but I’m not sure on the
requirements for it to run. if the time stamps have not been updated in
We have noticed that a cluster we upgraded to 1.1.6 (from 1.0.*) still has a
single large (~4GB) row in system.Migrations on each cluster node.
There is some code in there to drop that CF at startup, but I’m not sure on the
requirements for it to run. if the time stamps have not been updated
We have noticed that a cluster we upgraded to 1.1.6 (from 1.0.*) still has a
single large (~4GB) row in system.Migrations on each cluster node. We are also
seeing heap pressure / Full GC issues when we do schema updates to this
cluster. If the two are related, is it possible to somehow
