Hi
I used cassandra driver provided by datastax (3.5.0) library in nodejs.
I've 5 nodes cluster. I'm writing to a table with quorum.
I observed that there is some spike in write. In ~20 writes, 2-5 writes are
taking longer(~200ms). I debugged one of the node process with strace and
found that lon
Hi Tarun,
There are a ton of factors that can impact query performance.
The cassandra native protocol supports multiple simultaneous requests per
connection. Most drivers by default only create one connection to each C*
host in the local data center. That being said, that shouldn't be a
problem
ability to delete an specific appointment
Note: The bucket column is intended to allow date querying and to help spread
data evenly around the cluster. The bucket value is composed by year+month+day
sample bucket value: 20181104 )
CREATE TABLE appointment_by_invitee(
objectid timeuuid,
organizerid
delete an specific appointment
>
> Note: The bucket column is intended to allow date querying and to help
> spread data evenly around the cluster. The bucket value is composed by
> year+month+day sample bucket value: 20181104 )
>
>
> CREATE TABLE appointment_by_invitee(
>
ty to update(date, location, status) of an specific appointment.
4)The ability to delete an specific appointment
Note: The bucket column is intended to allow date querying and to help spread
data evenly around the cluster. The bucket value is composed by year+month+day
sample bucket val
he start date
>>
>> 2)The ability to select all appointments by organizer and by date range
>> on the start date
>>
>> 3)The ability to update(date, location, status) of an specific
>> appointment.
>>
>> 4)The ability to delete an specific appoi
Hi Onmstester,
Thank you all. Now I understand whether to use batch or asynchronous writes
really depends on use case. Till now batch writes work for me in a 8 nodes
cluster with over 500 million requests per day.
> Did you compare the cluster performance including blocked natives, dropped
> m
On Sat, Nov 3, 2018 at 1:13 AM Brian Spindler
wrote:
> That wasn't horrible at all. After testing, provided all goes well I can
> submit this back to the main TWCS repo if you think it's worth it.
>
> Either way do you mind just reviewing briefly for obvious mistakes?
>
>
> https://github.com/bs
