I am running DSE 4.8.7 / Cassandra 2.1.14.
When I attempt to run nodetool cleanup on any node / any environment we are
managing, I get the following output:
Aborted cleaning up atleast one column family in keyspace ,
check server logs for more information.
error: nodetool failed, check server
By default, yes, nodetool connects to localhost, which your log entries
show. Use `nodetool -h $PRIV_IP cleanup ...` to connect to that private
IP it's listening on. `nodetool help cleanup` for all options.
--
Kind regards,
Michael
On 02/10/2017 02:22 PM, Simone Franzini wrote:
> I am running
Hi,
Cassandra's implementation of Paxos doesn't implement many optimizations
that would drastically improve throughput and latency. You need
consensus, but it doesn't have to be exorbitantly expensive and fall
over under any kind of contention.
For instance you could implement EPaxos
Thanks Ariel! Yes I knew there are so many variations and optimizations of
Paxos. I just wanted to see if we had any plans on improving the existing
Paxos implementation and it is great to see the work is under progress! I
am going to follow that ticket and read up the references pointed in it
I am trying to ingest some data from a cluster to a different cluster via
sstableloader. I am running DSE 4.8.7 / Cassandra 2.1.14.
I have re-created the schemas and followed other instructions here:
https://docs.datastax.com/en/cassandra/2.1/cassandra/tools/toolsBulkloader_t.html
I am initially
Thank you Michael.
Well, this was apparently my bad.
1. nodetool connects to the local JMX port 7199, which is indeed running on
localhost in my case.
2. I did a few more attempts, the message "Aborted cleaning up atleast one
column family in keyspace " only appears in the DC where
is not
The nodetool cleanup ran successfully after setting the CLASSPATH variable to
the kubernetes-cassandra.jar.
Thanks.
> On 09-Feb-2017, at 2:23 PM, Srinath Reddy wrote:
>
> Alex,
>
> Thanks for reply. I will try the workaround and post an update.
>
> Regards,
>
> Srinath
tx
2017-02-10 10:01 GMT+01:00 Benjamin Roth :
> you could write a custom trigger that logs access to specific CFs. But be
> aware that this may have a big performance impact.
>
> 2017-02-10 9:58 GMT+01:00 vincent gromakowski <
> vincent.gromakow...@gmail.com>:
>
>> GDPR
Hi Jon,
Thanks a lot for your response. I am well aware that the LWW != LWT but I
was talking more in terms of LWW with respective to LWT's which I believe
you answered. so thanks much!
kant
On Thu, Feb 9, 2017 at 6:01 PM, Jon Haddad
wrote:
> LWT != Last Write Wins.
On a cluster with just a little bit load, that would cause zillions of
petabytes of logs (just roughly ;)). I don't think this is viable.
There are many many JMX metrics on an aggregated level. But none per authed
used.
What exactly do you want to find out? Is it for debugging purposes?
GDPR compliancy...we need to trace user activity on personal data. Maybe
there is another way ?
2017-02-10 9:46 GMT+01:00 Benjamin Roth :
> On a cluster with just a little bit load, that would cause zillions of
> petabytes of logs (just roughly ;)). I don't think this is
you could write a custom trigger that logs access to specific CFs. But be
aware that this may have a big performance impact.
2017-02-10 9:58 GMT+01:00 vincent gromakowski :
> GDPR compliancy...we need to trace user activity on personal data. Maybe
> there is
If you want to audit write operations only, you could maybe use CDC, this
is a quite new feature in 3.x (I think it was introduced in 3.9 or 3.10)
2017-02-10 10:10 GMT+01:00 vincent gromakowski <
vincent.gromakow...@gmail.com>:
> tx
>
> 2017-02-10 10:01 GMT+01:00 Benjamin Roth
Hi all,
Is there any way to trace user activity at the server level to see which
user is accessing which data ? Do you thin it would be simple to implement ?
Tx
Hi Kant,
If you read the published papers about Paxos, you will most probably
recognize that there is no way to "do it better". This is a conceptional
thing due to the nature of distributed systems + the CAP theorem.
If you want A+P in the triangle, then C is very expensive. CS is made for
A+P
"That’s the safety blanket everyone wants but is extremely expensive,
especially in Cassandra."
yes LWT's are expensive. Are there any plans to make this better?
On Fri, Feb 10, 2017 at 12:17 AM, Kant Kodali wrote:
> Hi Jon,
>
> Thanks a lot for your response. I am well
16 matches
Mail list logo