I am trying out Aggregations in a single node Cassandra 3.1
installation. The node has 4GB RAM. The table being aggregated on
contains ~45 rows. It contains information on US domestic flights
for a single month (from
http://www.transtats.bts.gov/DL_SelectFields.asp?Table_ID=236&DB_Sho
Thanks for the pointers! I edited jvm.options in
$CASSANDRA_HOME/conf/jvm.options to increase -Xms and -Xmx to 1536M.
The result is the same.
And in $CASSANDRA_HOME/logs/system.log, grep GC system.log produces this
(when jvm.options had not been changed):
INFO [Service Thread] 2015-12-1
Even if aggregation that forces a full table scan across partitions is
not recommended, the message/exception does seems unrelated to partitioning:
cqlsh:flightdata> select late_flights(uniquecarrier, depdel15) from
flightsbydate in ('2015-09-15', '2015-09-16',
'2015-09-17', '2015-09-
system.log to
chase down the root issue.
"Would trying the Datastax distribution offer any better chances?" -->
No, DSC is just a packaging of C* OSS
On Thu, Dec 24, 2015 at 7:07 AM, Dinesh Shanbhag
<mailto:dinesh.shanb...@isanasystems.com>> wrote:
Even if aggregat
