I agree with Tyler! Have you tries increasing the the client threads from 5
to a higher number?
On Nov 5, 2015 6:46 PM, "郝加来" wrote:
> right ,
> but wo want a node 's throught is above million , so if the system hava
> fifty table , a single table can achive 2/s .
>
>
> --
What is your replication factor and write consistency? :)
On Sep 23, 2015 7:28 AM, "Björn Hachmann"
wrote:
> Today I realized that one of the nodes in our Cassandra cluster (2.1.7) is
> storing a lot of hints (>80GB) and I fail to see a convincing way to deal
> with them.
>
> From the system.log:
I came across this article:
zdnet.com/article/kvm-creators-open-source-fast-cassandra-drop-in-replacement-scylla/
Tzach, I would love to know/understand moree about ScyllaDB too. Also the
benchmark seems to have only 1 DB Server. Do you have benchmark numbers
where more than 1 DB servers were invo
pply a mutation (write).
>
> That timestamp is the one returned by WRITETIME(), and visible in
> sstablemetadata – it’s not visible in the schema directly.
>
> Failing to have the proper unit (milliseconds vs microseconds) could
> certainly cause confusion.
>
>
>
> From: Ven
> 2.1.9)
>
>
> From: Venkatesh Arivazhagan
> Reply-To: "user@cassandra.apache.org"
> Date: Sunday, September 20, 2015 at 2:48 PM
> To: "user@cassandra.apache.org"
> Subject: Help with tombstones and compaction
>
> Hi Guys,
>
> I have a Cassa
