NPE during schema upgrade from 2.2.6 -> 3.0.6

Hi Everyone, I’m getting a NullPointerException when I start up 3.0.6 for the first time with data from 2.2.6. Any ideas for how to fix this, or other troubleshooting strategies? This is just a single-node development box. Originally I tried upgrading from 2.1.13 to 3.0.6, but I ran into

C* working with Open JDK but not Oracle JDK

I am running C* 2.1.4 on an Ubuntu vagrant VM. When I use OpenJDK 8, C* works fine. However using Oracle JDK 8, I get the errors listed below. I have read that it is not recommended to use Open JDK so I would like to be able to use the Oracle JDK. I am stumped on this issue and haven’t been

Per node limit for Disk Space

Hi All, I have question regarding max disk space limit on a node. As per Data stax, We can have 1TB max disk space for rotational disks and up to 5 TB for SSDs on a node. Could you please suggest per your experience what would be limit for space on a single node with out causing so much stress

Re: Error while rebuilding a node: Stream failed

I am trying once more using more aggressive tcp settings, as recommended here sudo sysctl -w net.ipv4.tcp_keepalive_time=60 net.ipv4.tcp_keepalive_probes=3 net.ipv4.tcp_keepalive_intvl=10 (added to

Re: Internal Handling of Map Updates

If you aren't removing elements from the map, you should instead be able to use an UPDATE statement and append the map. It will have the same effect as overwriting it, because all the new keys will take precedence over the existing keys. But it'll happen without generating a tombstone first. If

Re: cqlsh problem

Can you do a netstat -lepunt and show the output? If Cassandra is running you aren't trying to connect to the ip/port it's bound to. Patrick On Monday, May 23, 2016, joseph gao wrote: > I used to think it's firewall/network issues too. So I make ufw to be > inactive. I

Re: Error while rebuilding a node: Stream failed

I'm afraid raising streaming_socket_timeout_in_ms won't help much in this case because the incoming connection on the source node is timing out on the network layer, and streaming_socket_timeout_in_ms controls the socket timeout in the app layer and throws SocketTimeoutException (not

Re: Error while rebuilding a node: Stream failed

Check ifconfig for dripped tpc messages. Let's rule out your network. all the best, Sebastián On May 27, 2016 10:45 AM, "George Sigletos" wrote: > Hello, > > No there is no version mix. The first stack traces were indeed from > 2.1.13. Then I upgraded all nodes to

Re: Error while rebuilding a node: Stream failed

Hello, No there is no version mix. The first stack traces were indeed from 2.1.13. Then I upgraded all nodes to 2.1.14. Still getting the same errors On Fri, May 27, 2016 at 4:39 PM, Eric Evans wrote: > From the various stacktraces in this thread, it's obvious you

Re: Error while rebuilding a node: Stream failed

>From the various stacktraces in this thread, it's obvious you are mixing versions 2.1.13 and 2.1.14. Topology changes like this aren't supported with mixed Cassandra versions. Sometimes it will work, sometimes it won't (and it will definitely not work in this instance). You should either

Re: Error while rebuilding a node: Stream failed

Still failing. Should I maybe set a higher value for streaming_socket_timeout_in_ms? Maybe 2-3 days? Source: node ERROR [STREAM-OUT-/54.172.235.227] 2016-05-27 14:30:34,401 StreamSession.java:505 - [Stream #45017970-234c-11e6-9452-1b05ac77baf9] Streaming error occurred java.lang.AssertionError:

Re: Out of memory issues

Paolo, try a few things in cassandra-env.sh 1. HEAP_NEWSIZE="2G". "The 100mb/core commentary in cassandra-env.sh for setting HEAP_NEWSIZE is *wrong*" ( https://tobert.github.io/pages/als-cassandra-21-tuning-guide.html) 2. MaxTenuringThreshold=8 3. enable GC logging (under "# GC logging options --

Re: Internal Handling of Map Updates

We are processing events in Spark and store the resulting entries (containing a map) in Cassandra. The results can be new (no entry for this key in Cassandra) or an Update (there is already an entry with this key in Cassandra). We use the spark-cassandra-connector to store the data in Cassandra.

Re: Out of memory issues

Hi, thanks for the answer. There were no large insertions and the saved_caches dir had a resonable size. I tried to delete the cashes and set key_cache_size_in_mb to zero, but it didn't help. Today our virtual hardware provided raised cpus to 4, memory to 32GB and doubled the disk size, and

Re: Thrift client creates massive amounts of network packets

Thanks Eric. Indeed it is the way Titan works during graph-traversal: https://groups.google.com/forum/#!topic/aureliusgraphs/IwzRMNB0zzM . Newer Titan versions attempt to batch the requests and reduce the number of network