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

Re: Thrift client creates massive amounts of network packets

If it's a single node cluster, then it's not consistency level related as all consistencies are essentially the same. This looks instead like a usage pattern that's entirely driven by Titan's read pattern which appears to be lots of tiny reads (probably not too surprising for a graph database).

Re: Thrift client creates massive amounts of network packets

Eric, thanks for the hint. Titan 0.5.4 uses ONE, not LOCAL_ONE. I can try and patch the version. Given that it is a single node cluster for the time being, would your remarks apply to that particular setup? Thanks again! Ralf > On 24.05.2016, at 19:18, Eric Stevens

Re: Thrift client creates massive amounts of network packets

I'm not familiar with Titan's usage patterns for Cassandra, but I wonder if this is because of the consistency level it's querying Cassandra at - i.e. if CL isn't LOCAL_[something], then this might just be lots of little checksums required to satisfy consistency requirements. On Mon, May 23, 2016

Re: Thrift client creates massive amounts of network packets

I remembered that Titan treats edges (and vertices?) as immutable and deletes the entity and re-creates it on every change. So I set the gc_grace_seconds to 0 for every table in the Titan keyspace and ran a major compaction. However, this made the situation worse. Instead of roughly 2’700 tcp

Thrift client creates massive amounts of network packets

Hi all, tl:dr The Titan 0.5.4 cassandrathrift client + C* 2.0.8/2.2.6 create massive amounts of network packets for multiget_slice queries. Is there a way to avoid the “packet storm”? Details... We are using Titan 0.5.4 with its cassandrathrift storage engine to connect to a single node