This is an awesome effort. Thank you
Sent from my iPhone
> On Feb 27, 2018, at 1:17 PM, Carl Mueller
> wrote:
>
> Nice thanks
>
>
>> On Tue, Feb 27, 2018 at 12:03 PM, Jon Haddad wrote:
>> There’s a section dedicated to contributing to Cassandra documentation in
>> the docs as well:
>> htt
node with a 1 min. load avg of 140 that can still have a P99
>> read latency at 40ms. But I never saw a disappearing keyspace. There are
>> old tickets regarding C* 1.x but as far as I remember it was due to a
>> create/drop/create keyspace.
>>
>>
>> Le Vendredi 3
are in
> nanoseconds). You can override intervals via -Dcassandra.fd_initial_value_ms
> and -Dcassandra.fd_max_interval_ms properties. Are you sure you didn't have
> these lines in debug logs before? I used to see them a lot prior to
> increase intervals to 4 seconds.
>
> Best,
Hey Cassandra Users,
We recently encountered an issue with a keyspace just disappeared. I was
curious if anyone has had this occur before and can provide some insight.
We are using cassandra 3.10. 2 DCs 3 nodes each.
The data was still located in the storage folder but is not located inside
Cass
s potential JVM pressure. I did some some
> permutations of memory settings with the tests above. You can get a feel
> for rate + batch size and the jvm pressure it causes.
>
> On Mon, Oct 24, 2016 at 4:10 PM, George Webster
> wrote:
>
>> Hey cassandra users,
>>
>>
Hey cassandra users,
When performing writes I have hit an issue where the server is unable to
perform writes. The logs show:
WARN [MutationStage-1] 2016-10-24 22:05:52,592
AbstractLocalAwareExecutorService.java:169 - Uncaught exception on thread
Thread[MutationStage-1,5,main]: {}
java.lang.Illeg
e purged.
>
> The fact that you can see some rows then 0 rows mean that some of your
> replicas have missed the tombstones.
>
> "However, after about 20 attempts, all servers started to only return 0
> results. " --> Read-repair kicks in so the tombstones ar
l.
>
> Try the query again using CL = QUORUM, try on several nodes to see if the
> results are different
>
> On Tue, Aug 2, 2016 at 6:32 PM, George Webster
> wrote:
>
>> Hey DuyHai,
>> Thank you for your help.
>>
>> 1) Cassandra version
>> [
used for your SELECT
> 4) Replication factor
> 5) Are you creating the index when the table is EMPTY or have you created
> the index when the table already contains some data ?
>
> On Tue, Aug 2, 2016 at 4:05 PM, George Webster
> wrote:
>
>> Hey guys and gals,
>>
&g
Hey guys and gals,
I am having a strange issue with Cassandra SASI and I was hoping you could
help solve the mystery. My issue is inconsistency between returned results
and strange log errors.
The biggest issue is that when I perform a query I am getting back
inconsistent results. First few times
10 matches
Mail list logo
