Hi Jens,
Thank you for the tip!
ALL would definitely cure our hints issue, but as you note, it is not
optimal as we are unable to take down nodes without clients failing.
I am most probably overlooking something in the documentation, but I cannot
see any description of when hints are written othe
If the rack as defined in Cassandra stays the same (e.g.
cassandra-rackdc.properties), things will keep working as expected...
except when the actual rack (or fault domain) goes down and you are likely
to lose more nodes than expected.
If you change the rack as defined in Cassandra, the node will
Hello,
If a running node moves around and changes its rack in the process, when its
back in the cluster (through ignore-rack property), is it a correct statement
that queries will not see some data residing on this node until a repair is run
?
Or, is it more like the node may get requests for
how do you unsubscribe
From: Bo Finnerup Madsen
Sent: Wednesday, April 20, 2016 9:38 AM
To: user@cassandra.apache.org
Subject: When are hints written?
Hi,
We have a small 5 node cluster of m4.xlarge clients that receives writes from
~20 clients. The clients wi
Thanks Nate...
It works now..
On Wed, Apr 20, 2016 at 8:05 AM, Nate McCall wrote:
> You need to set LOCAL_JMX=false
>
> It will then read the rest of this stanza:
>
> https://github.com/apache/cassandra/blob/cassandra-2.2/conf/cassandra-env.sh#L284-L288
>
> Using the defaults above as-is, you wi
Can you show the output of a tpstats on one of the effected nodes? That
will give some indication where the trouble might be.
Patrick
On Tue, Apr 19, 2016 at 6:54 AM, sai krishnam raju potturi <
pskraj...@gmail.com> wrote:
> hi;
>do we see any hung process like Repairs on those 3 nodes? wha
I have a following table(using default sized tier compaction) that its column
get TTLed every hour(as we want to keep only the last 1 hour events)
And I do
Select * from mytable where object_id = ‘’ LIMIT 1;
And since query only interested in last/latest value, will cassandra need to
scan m
Hi, Paulo
Thank you for your help!
I'll try to use it.
Regards,
Satoshi
On Wed, Apr 20, 2016 at 8:43 PM, Paulo Motta
wrote:
> 2.2.6 should be released in the next couple of weeks, but I also attached
> a patch file to the issue if you want to patch 2.2.5 manually.
>
> 2016-04-20 0:19 GMT-03:0
Also, 3.0.3 is a very new Cassandra version. IMHO, you might want to
consider not using bleeding edge in production. See
https://www.eventbrite.com/engineering/what-version-of-cassandra-should-i-run/
and http://stackoverflow.com/q/25155916.
Cheers,
Jens
On Wed, Apr 20, 2016 at 3:39 PM Bo Finneru
Hi Bo,
> In our case, I would like for the cluster to wait for the write to be
persisted on the relevant nodes before returning an ok to the client. But I
don't know which knobs to turn to accomplish this? or if it is even
possible :)
This is what write consistency option is for. Have a look at
h
You need to set LOCAL_JMX=false
It will then read the rest of this stanza:
https://github.com/apache/cassandra/blob/cassandra-2.2/conf/cassandra-env.sh#L284-L288
Using the defaults above as-is, you will need to add JMX authentication.
Details are here:
https://docs.datastax.com/en/cassandra/2.2/c
Hi,
We have a small 5 node cluster of m4.xlarge clients that receives writes
from ~20 clients. The clients will write as fast as they can, and the whole
process is limited by the write performance of the cassandra cluster.
After we have tweaked our schema to avoid large partitions, the load is
goi
2.2.6 should be released in the next couple of weeks, but I also attached a
patch file to the issue if you want to patch 2.2.5 manually.
2016-04-20 0:19 GMT-03:00 Satoshi Hikida :
> Hi,
>
> I'm looking forward to a patch (file) for this bug(CASSANDRA-11344) to
> apply C* version 2.2.5. Is there
Hi Sam,
That's exactly what I was hoping for, but couldn't find in the docs. Thank you
very much!
-J
Sent via iPhone
> On Apr 20, 2016, at 02:05, Sam Tunnicliffe wrote:
>
> From 3.0, separate ports can be configured for encrypted & non-encrypted
> connections.
> See https://issues.apache.o
>From 3.0, separate ports can be configured for encrypted & non-encrypted
connections.
See https://issues.apache.org/jira/browse/CASSANDRA-9590
On Wed, Apr 20, 2016 at 8:51 AM, Jason J. W. Williams <
jasonjwwilli...@gmail.com> wrote:
> Hi Ben,
>
> Thanks for confirming what I saw occur. The Datas
Hi Ben,
Thanks for confirming what I saw occur. The Datastax drivers don't play
very nicely with Twisted Python so connection pooling is inconsistent and
makes always-on TLS a no-go performance-wise. The encryption overhead isn't
the problem, it's the build-up of the TLS session for every connecti
16 matches
Mail list logo
