I have what I assume is a simple problem, most likely with Cassandra, however I am unsure how to debug it further. Whilst playing with the cassandra cluster (adding a node, then shutting it down) The API endpoints for CQS are now unable to display the Queues that have been created (both via the cqs GUI, and calls from a ruby script). Creating new queues appears to work (entries are created in Cassandra/CQS/CQSQueues, however they are still not returned to ListQueues.)
Using default limit of 100
Using default column limit of 100
-------------------
RowKey: 355970964474/TestQueue99
=> (column=arn, value=arn:cmb:cqs:ccp:355970964474:TestQueue99, timestamp=1356167766808007)
=> (column=createdTime, value=1356167766805, timestamp=1356167766808003)
=> (column=delaySeconds, value=0, timestamp=1356167766808009)
=> (column=maxMsgSize, value=65536, timestamp=1356167766805000)
=> (column=msgRetentionPeriod, value=345600, timestamp=1356167766808001)
=> (column=name, value=TestQueue99, timestamp=1356167766808004)
=> (column=ownerUserId, value=355970964474, timestamp=1356167766808008)
=> (column=policy, value=, timestamp=1356167766808006)
=> (column=region, value=ccp, timestamp=1356167766808000)
=> (column=visibilityTO, value=30, timestamp=1356167766808002)
Both Cassandra nodes appear to be returning the same data when queried with LIST <keys>.
I have checked in redis, and there are no entries cached there.
I am under the impression that there are no entries being returned to cmb/cqs when querying Casandra.
Any pointers would be appreciated.