If I were starting a new project today, I'd go with 3.0. It's gotten over
half a year of bug fixes.
I personally would have a hard time putting a tick tock release into
production, as you're either getting new features or putting a version in
which won't receive any further bug fixes, so unless y
Hi,
I am new to Cassandra and a bit confused about how versioning works here.
I have recently started working on Cassandra clusters. I want to create a
Cassandra cluster and make it ready for production but I am not sure which
version is the right one. Some people mention that the most stable ver
If you migrate to the latest 2.1 first, you can make this a non-issue as
2.1.12 and above support simultaneous SSL and plain on the same port for
exactly this use case:
https://issues.apache.org/jira/browse/CASSANDRA-10559
On Thu, Jul 21, 2016 at 3:02 AM, sai krishnam raju potturi <
pskraj...@gmai
Yuan,
If you add a static key=value pair, you need to add it using the "fields="
section. However, when the "fields=" section is used, you must list all of
the fields that you want to appear in the POST data.
Here is an example that sends message_type and the message itself:
fields=message_type
Just to make sure I understand, you've got a queue where you can stand
missing processing the items in it?
On Wed, Jul 20, 2016 at 1:13 PM Kevin Burton wrote:
> On Wed, Jul 20, 2016 at 11:53 AM, Jeff Jirsa
> wrote:
>
>> Can you tolerate the value being “close, but not perfectly accurate”? If
>>
On Wed, Jul 20, 2016 at 11:53 AM, Jeff Jirsa
wrote:
> Can you tolerate the value being “close, but not perfectly accurate”? If
> not, don’t use a counter.
>
>
>
yeah.. agreed.. this is a problem which is something I was considering. I
guess it depends on whether they are 10x faster..
--
We’r
Just to pick this up: Did you see any system load spikes? I'm tracing a
problem on 2.2.7 where my cluster sees load spikes up to 20-30, when the
normal average load is around 3-4. So far I haven't found any good reason,
but I'm going to try otc_coalescing_strategy: disabled tomorrow.
- Garo
On F
Can you tolerate the value being “close, but not perfectly accurate”? If not,
don’t use a counter.
From: on behalf of Kevin Burton
Reply-To: "user@cassandra.apache.org"
Date: Wednesday, July 20, 2016 at 11:48 AM
To: "user@cassandra.apache.org"
Subject: Are counters faster than CAS or vi
We ended up implementing a task/queue system which uses a global pointer.
Basically the pointer just increments ... so we have thousands of tasks
that just increment this one pointer.
The problem is that we're seeing contention on it and not being able to
write this record properly.
We're just d
I just recently upgraded our cluster to 2.2.7 and after turning the cluster
under production load the instances started to show high load (as shown by
uptime) without any apparent reason and I'm not quite sure what could be
causing it.
We are running on i2.4xlarge, so we have 16 cores, 120GB of ra
I don't know if my perspective on this will assist, so YMMV:
Summary
1. Nodetool repairs are required when a node has issues and can't get
its (e.g. hinted handoff) resync done: culprit: usually network, sometimes
container/vm, rarely disk.
2. Scripts to do partition range are a pain
hi ;
if possible could someone shed some light on this. I followed a
post from the lastpickle which was very informative, but we had some
concerns when it came to enabling SSL on a live production cluster.
http://thelastpickle.com/blog/2015/09/30/hardening-cassandra-step-by-step-part-1-se
Hi Cyril,
What Cassandra version are you using?
There a lot of recent and ongoing work around LCS. Maybe one of these
tickets will be of interest to you:
https://issues.apache.org/jira/browse/CASSANDRA-10979
https://issues.apache.org/jira/browse/CASSANDRA-10862
C*heers,
---
Hi,
It seems that when LCS tables are used, sstables sent are not sent with the
level information which generates a lot of compaction tasks in some cases.
Don't you think that the level information should also be spent to avoid having
desynchronized replicas to compact sstables sent ?
Thanks
Hi Satoshi,
> Q1:
> According to the DataStax document, it's recommended to run full repair
> weekly or monthly. Is it needed even if repair with partitioner range
> option ("nodetool repair -pr", in C* v2.2+) is set to run periodically for
> every node in the cluster?
>
More accurately you need
Hi Jean,
This option is available in C* version 2.1.x & above, where you can specify
hosts in nodetool repair command . For more detail please visit the link below
:
https://docs.datastax.com/en/cassandra/2.1/cassandra/tools/toolsRepair.html
Regards
Amit Singh
From: Alain RODRIGUEZ [mailto:a
Hi Jean,
All the nodes are not necessary involved in a repair depending on vnodes
being enabled or not, on your topology, on the racks you are using etc.
This being said, if a node was supposed to be part of a repair process, the
repair of all the subranges including the down node will fail. That
Hi Aoi,
> since few weeks
> ago, all of the cluster nodes are hitting avg. 15-20 cpu load.
> These nodes are running on VMs(VMware vSphere) that have 8vcpu
> (1core/socket)-16 vRAM.(JVM options : -Xms8G -Xmx8G -Xmn800M)
I take my chance, a few ideas / questions below:
- What Cassandra versi
Hi Yuji Ito,
I don't know Cassandra 2.2 that much and I try to avoid using indexes, but
I imagine that what happened there is that creating the index took some
time, and all the newly created data went to L0 and compaction was
intensive as this node suddenly had a lot of pending compactions.
From
The problem you're seeing is because of the thrift max_message_length,
which is set to 16mb and is not configurable from outside / in the yaml
file.
If the JDBC wrapper supports paging, you might want to look into
configuring it.
On Tue, Jul 19, 2016 at 8:27 PM Saurabh Kumar wrote:
> Hi ,
>
> I
20 matches
Mail list logo
