Re: Not timing out some queries (Java driver)

The replication factor is the default - I haven't changed it. Would tweaking it help? On Thu, Dec 22, 2016 at 8:41 PM, Ali Akhtar wrote: > Vladimir, > > I'm receiving a batch of messages which are out of order, and I need to > process those messages in order. > > My

Re: Not timing out some queries (Java driver)

Vladimir, I'm receiving a batch of messages which are out of order, and I need to process those messages in order. My solution is to write them to a cassandra table first, where they'll be ordered by their timestamp. Then read them back from that table, knowing that they'll be ordered. But for

Re: Not timing out some queries (Java driver)

What is replication factor? Why not use CONSISTENCY QUORUM? It's faster and safe enough. Best regards, Vladimir Yudovin, Winguzone - Cloud Cassandra Hosting On Thu, 22 Dec 2016 10:14:14 -0500 Ali Akhtar ali.rac...@gmail.com wrote Is it possible to provide these options

Re: Not timing out some queries (Java driver)

Is it possible to provide these options per query rather than set them globally? On Thu, Dec 22, 2016 at 7:15 AM, Voytek Jarnot wrote: > cassandra.yaml has various timeouts such as read_request_timeout, > range_request_timeout, write_request_timeout, etc. The driver

Re: Not timing out some queries (Java driver)

cassandra.yaml has various timeouts such as read_request_timeout, range_request_timeout, write_request_timeout, etc. The driver does as well (via Cluster -> Configuration -> SocketOptions -> setReadTimeoutMillis). Not sure if you can (or would want to) set them to "forever", but it's a starting

Not timing out some queries (Java driver)

I have some queries which need to be processed in a consistent manner. I'm setting the consistently level = ALL option on these queries. However, I've noticed that sometimes these queries fail because of a timeout (2 seconds). In my use case, for certain queries, I want them to never time out