nodetool status high load info

Hello, Nodetool status shows much more than actual data size. When I restart node, it shows normal a while and increase load in time. Where should I look? Cassandra 3.0.8, jdk 1.8.121 Regards, Osman This e-mail message, including any attachments, is for the sole use of the person to whom it

Re: [Marketing Mail] Re: nodetool status high load info

Hello, Here is the problem loads, first node shows 206TB data. After cassandra restart it shows 51TB, like df shows. Status=Up/Down |/ State=Normal/Leaving/Joining/Moving -- Address Load Tokens Owns (effective) Host ID Rack UN x.x.x.1 206 TB 256 50.6%

Re: nodetool status high load info

Try nodetool tpstats - it can lead you to where your threads are stuck. There could be various reasons for load factor to go high like disk/cpu getting choked, you'll probably need to check dstat & iostat output along with Cassandra Threadpool stats to get a decent idea. On Wed, Apr 12, 2017 at

Re: WriteTimeoutException with LWT after few milliseconds

sorry .. ignore my comment ... i missed your comment that the record is in the table ... On Wed, 2017-04-12 at 16:48 +0200, Roland Otta wrote: Hi Benjamin, its unlikely that i can assist you .. but nevertheless ... i give it a try ;-) whats your consistency level for the insert? what if one

Re: WriteTimeoutException with LWT after few milliseconds

Hi Benjamin, its unlikely that i can assist you .. but nevertheless ... i give it a try ;-) whats your consistency level for the insert? what if one ore more nodes are marked down and proper consistency cant be achieved? of course the error message does not indicate that problem (as it says its

Re: WriteTimeoutException with LWT after few milliseconds

You can try to use TRACING to debug the situation, but for a LWT to fail so fast, the most probable cause is what you stated: "It is possible that there are concurrent inserts on the same PK - actually thats the reason why I use LWTs." AKA, someone inserted first. Regards, Carlos Juzarte Rolo

Re: [Marketing Mail] Re: nodetool status high load info

Do you perform a lot of deletes or updates on your database? On restart, it performs major compaction which can reduce the load on your node by removing stale data. Try configuring compaction in you conf to perform minor compaction i.e. compactions at a regular interval. Thanks, Anuja On Wed,

Re: [Marketing Mail] Re: [Marketing Mail] Re: nodetool status high load info

Actually there is no delete right now. Only inserts. I use twcs and not much compaction occurs. It just miscalculates sstable sizes. On 12-04-2017 14:58, anuja jain wrote: Do you perform a lot of deletes or updates on your database? On restart, it performs major compaction which can reduce the

WriteTimeoutException with LWT after few milliseconds

Hi folks, Can someone explain why that occurs? Write timeout after 0.006s Query: 'INSERT INTO log_moment_import ("source", "reference", "user_id", "moment_id", "date", "finished") VALUES (3, '1305821272790495', 65675537, 0, '2017-04-12 13:00:51', NULL) IF NOT EXISTS Primary key and parition key

Re: Can we get username and timestamp in cqlsh_history?

Thanks Nicolas. That is exactly what I was looking for. On Tue, Apr 4, 2017 at 12:08 AM, Durity, Sean R wrote: > Sounds like you want full auditing of CQL in the cluster. I have not seen > anything built into the open source version for that (but I could be >

How to change frozen to non frozen columns in cassandra

Hi , I have a table with columns of type frozen I want to convert it to simple list How can I do that without droping existing column? I have data in that column. I am using dse 4.8.11 Thanks, Anuja

Re: IPv6-only host, can't seem to get Cassandra to bind to a public port

From: sai krishnam raju potturi > We have included the IPV6 address with scope GLOBAL, and not IPV6 with SCOPE > LINK in the YAML and TOPOLOGY files.  > > inet6 addr: 2001: *** : ** : ** : * : * : :  Scope:Global > inet6 addr: fe80 :: *** : : :

Constant MemtableFlushWriter Messages Following upgrade from 2.2.5 to 2.2.8

In the process of upgrading our cluster. Nodes that go upgraded are constantly emitting these messages. No impact, but wanted to know what they mean and why after the upgrade only. Any feedback will be appreciated. 17-04-10 20:18:11,580 Memtable.java:352 - Writing

Re: Multiple nodes decommission

But it seems OK to add multiple nodes at once, right? On Tuesday, April 11, 2017 8:38 PM, Jacob Shadix wrote: Right! Another reason why I just stick with sequential decommissions. Maybe someone here could shed some light on what happens under the covers if

Re: WriteTimeoutException with LWT after few milliseconds

Hi Roland, LWTs set consistency level implicitly to SERIAL which requires at least QUORUM. No, no node is/was down. If that happens the query will fail with "Could not achieve consistency level QUORUM ..." 2017-04-12 16:48 GMT+02:00 Roland Otta : > Hi Benjamin, > > its

Re: Multiple nodes decommission

It's still not recommended to start at the same time. Stagger by 2 minutes is what the following documentation suggests; along with additional steps. re. version 2.1 https://docs.datastax.com/en/cassandra/2.1/cassandra/operations/ops_add_node_to_cluster_t.html -- Jacob Shadix On Wed, Apr 12,

Re: Multiple nodes decommission

Interesting, there is no such explicit warning for v.3 https://docs.datastax.com/en/cassandra/3.0/cassandra/operations/opsAddNodeToCluster.html It says - Start the bootstrap node. - verify that the node is fully bootstrapped and all other nodes are up (UN) Does it mean that we should

Re: IPv6-only host, can't seem to get Cassandra to bind to a public port

From: "Khaja, Raziuddin (NIH/NLM/NCBI) [C]" > Maybe you have to escape the IPV6 addresses in the cassandra.yaml in the same > way. > I think it’s worth a try. Nope, no luck. You get an error instead: ERROR [main] 2017-04-12 20:03:46,899 CassandraDaemon.java:752 -

Re: IPv6-only host, can't seem to get Cassandra to bind to a public port

Are you specifying both the listen_address and listen_interface, or just one of the two? Send, an example of the following 3 lines. Here is what I have on my 2.1.16 cluster that uses ipv6: listen_address: ::hhh::h::hhh:h # listen_interface: eth0 #

Re: IPv6-only host, can't seem to get Cassandra to bind to a public port

See this note in cassandra-topology.properties: # Native IPv6 is supported, however you must escape the colon in the IPv6 Address # Also be sure to comment out JVM_OPTS="$JVM_OPTS -Djava.net.preferIPv4Stack=true" # in cassandra-env.sh fe80\:0\:0\:0\:202\:b3ff\:fe1e\:8329=DC1:RAC3 Maybe