Cassandra TimeUUID flood file descriptor when use uuid in default

Question

I have Cassandra model as

import uuid
from cassandra.cqlengine import columns
from cassandra.cqlengine.models import Model

class MyModel(Model):
    ...
    ..         


        

Answer 1

Are you certain you're hitting the libuuid issue you linked? Your code snippet shows the standard library uuid, which probably doesn't have that issue. Is it possible there's a different file descriptor leak in your program?

If it is libuuid, the easiest course would be to use the standard library implementation. If speed is a major concern for you, you might look into building a different version of libuuid to use with python-libuuid. I tried this one quickly and didn't notice any file descriptors leaking: http://www.ossp.org/pkg/lib/uuid/

I also want to know, what is the advantage of using TimeUUID instead of timestamp ?

You won't be able to change the type of the column on your existing table, but to answer your question: TimeUUID is usually used to avoid collisions where multiple events could be written in the same timestamp value.