On Mon, Jan 27, 2014 at 5:44 AM, Erik Forsberg <forsb...@opera.com> wrote:
> On 2014-01-27 12:56, Erik Forsberg wrote: > > This is on Cassandra 1.2.1. I know that's pretty old, but I would like to > avoid upgrading until I have made this migration from old to new hardware. > Upgrading to 1.2.13 might be an option. > > > Update: Exactly the same behaviour on Cassandra 1.2.13. > If I were you, I would : 1) search for existing issues on JIRA 2) failing to find 1), file a JIRA with repro details =Rob