of
> (CQL) rows, to distinguish from the pre-CQL3 concept of a partition being
> treated as a single row.
>
> -- Jack Krupansky
>
> On Mon, Apr 11, 2016 at 11:46 AM, Emīls Šolmanis > wrote:
>
>> Wouldn't the "number of keys" part of *nodetool cfstats* run
Wouldn't the "number of keys" part of *nodetool cfstats* run on every node,
summed and divided by replication factor give you a decent approximation?
Or are you really after a completely precise number?
On Mon, 11 Apr 2016 at 16:18 Jack Krupansky
wrote:
> Agreed, that anything requiring a full t
That said, if you *really* want transactionality other than what's provided
by batches, you should probably look into a more suitable solution. Using
Cassandra exclusively with lightweight transactions at quorum writes will
put serious load on it, and you probably won't achieve decent write
through
r or Cassandra proper.
>
> -- Jack Krupansky
>
> On Thu, Mar 10, 2016 at 12:39 PM, Emīls Šolmanis > wrote:
>
>> In case someone stumbles upon this same thing later.
>>
>> Ended up being a collection item that was too big (i.e., larger than
>> 64K). Something to do wi
particular instance. The error message could
definitely be better though, and I'll raise it with the devs.
Regards,
Emils
On Wed, 9 Mar 2016 at 20:31 Emīls Šolmanis wrote:
> Hey Alex,
>
> I did do a grep for that message in the driver code base and it seems like
> it's not the
tps://groups.google.com/a/lists.datastax.com/forum/#!forum/java-driver-user
>
> (as a side note, I haven't seen this one before)
>
> On Wed, Mar 9, 2016 at 11:52 AM, Emīls Šolmanis
> wrote:
>
>> Hello,
>>
>> I kee
Hello,
I keep getting an exception about a clustering key being too long, like
com.datastax.driver.core.exceptions.InvalidQueryException: The sum of
all clustering columns is too long (72650 > 65535)
at
com.datastax.driver.core.Responses$Error.asException(Responses.java:136)
at
t; Emils,
>
> I realize this may be a big downgrade, but are you timeouts reproducible
> under Cassandra 2.1.4?
>
> Mike
>
> On Thu, Feb 25, 2016 at 10:34 AM, Emīls Šolmanis > wrote:
>
>> Having had a read through the archives, I missed this at first, but th
l.
On Thu, 25 Feb 2016 at 14:55 Emīls Šolmanis
wrote:
> Hello,
>
> We're having a problem with concurrent requests. It seems that whenever we
> try resolving more
> than ~ 15 queries at the same time, one or two get a read timeout and then
> succeed on a retry.
>
> We&
Hello,
We're having a problem with concurrent requests. It seems that whenever we
try resolving more
than ~ 15 queries at the same time, one or two get a read timeout and then
succeed on a retry.
We're running Cassandra 2.2.4 accessed via the 2.1.9 Datastax driver on AWS.
What we've found while
10 matches
Mail list logo
