I am running 2.0.6 and I use /etc/init.d/cassandra start / stop . Also before
stopping I do :
nodetool disablegossip
nodetool disablethrift
nodetool drain
after that /etc/init.d/cassandra stop
On Monday, March 24, 2014 9:48 PM, Robert Coli rc...@eventbrite.com wrote:
On Mon, Mar 24, 2014 at
Hi,
I am quite new to Cassandra and trying to evaluate its feasibility for our
application.
In our application, we need to insert roughly 30 sensor data every 30
seconds (basically we need to store time-series data). I wrote a simple
java code to insert 30 random data every 30 seconds
Hi,
What is your hardware, C* version, data structure and typical data size ?
On 03/25/2014 06:36 PM, shahab wrote:
Hi,
I am quite new to Cassandra and trying to evaluate its feasibility
for our application.
In our application, we need to insert roughly 30 sensor data every
30 seconds
On 03/25/2014 10:36 AM, shahab wrote:
In our application, we need to insert roughly 30 sensor data
every 30 seconds (basically we need to store time-series data). I
wrote a simple java code to insert 30 random data every 30
seconds for 10 iterations, and measured the number of entries
Thanks.
I run it on a Linux Server, Dual Processor, Intel(R) Xeon(R) CPU E5440 @
2.83GHz, 4 core each and 8 GM RAM.
Just to give an example of data inserted:
INSERT INTO traffic_by_day(segment_id, day, event_time, traffic_value)
VALUES (100, 84, '2013-04-03 07:02:00', 79);
Here is the
Hi Shalab,
Are you using anything in your WHERE clause of the query?
If not, you are doing a full scan of your data. In iteration 8 it will scan 1
500 000 entries, and the default time out value is pretty low.
If you do select count(*) from traffic_by_day where segment_id = 1 and day = 1
it
On Tue, Mar 25, 2014 at 8:36 AM, shahab shahab.mok...@gmail.com wrote:
But after iteration 8, (i.e. inserting 150 sensor data), the select
count(') ...) throws time-out exception and doesn't work anymore. I even
tried to execute select count(*)... using Datastax DevCenter GUI, but I
On Tue, Mar 25, 2014 at 5:36 AM, Batranut Bogdan batra...@yahoo.com wrote:
I am running 2.0.6 and I use /etc/init.d/cassandra start / stop . Also
before stopping I do :
nodetool disablegossip
nodetool disablethrift
nodetool drain
after that /etc/init.d/cassandra stop
This seems
Note that drain stops gossip and thrift anyway, so they are redundant.
On 25 March 2014 18:30, Robert Coli rc...@eventbrite.com wrote:
On Tue, Mar 25, 2014 at 5:36 AM, Batranut Bogdan batra...@yahoo.comwrote:
I am running 2.0.6 and I use /etc/init.d/cassandra start / stop . Also
before
On Tue, Mar 25, 2014 at 11:34 AM, Benedict Elliott Smith
belliottsm...@datastax.com wrote:
Note that drain stops gossip and thrift anyway, so they are redundant.
While we're noting implementation details... none of these functions
necessarily stop writes to your node, which is probably what
Hi,
On 25/03/14 19:30, Robert Coli wrote:
On Tue, Mar 25, 2014 at 5:36 AM, Batranut Bogdan batra...@yahoo.com
mailto:batra...@yahoo.com wrote:
I am running 2.0.6 and I use /etc/init.d/cassandra start / stop . Also
before stopping I do :
nodetool disablegossip
nodetool
Sigh, so I am back to where I started from...
I did lower gc_grace...
jmap -histo:live shows heap is stuffed with DeletedColumn and
ExpiringColumn
This is extremely frustrating.
On 2014-03-11 19:24:50 +, Oleg Dulin said:
Good news is that since I lowered gc_grace period it
Sorry to hear about the frustration. How often are you deleting data/what
are you setting for ttl on cols?
Jonathan Lacefield
Solutions Architect, DataStax
(404) 822 3487
http://www.linkedin.com/in/jlacefield
http://www.datastax.com/what-we-offer/products-services/training/virtual-training
I believe that no matter how I stop cassandra, I should not be missing data.
Even if compaction is in progress. As far as I can tell during compaction cassa
reads from some files and creates a new temp file. Here I believe that it
stores the info and after the new file is complete it should
On Tue, Mar 25, 2014 at 1:55 PM, Batranut Bogdan batra...@yahoo.com wrote:
I believe that no matter how I stop cassandra, I should not be missing
data. Even if compaction is in progress.
Well, excepting that what you describe is impossible if you crash
cassandra (kill -9, etc.), I agree. It's
What message would be on the log, or not on the log, what would you be
grep-ing for?
Also, why were you interested in startup procedure? Is there some best
practices: for that which could impact this?
On Tue, Mar 25, 2014 at 2:55 PM, Robert Coli rc...@eventbrite.com wrote:
On Tue, Mar 25,
On Tue, Mar 25, 2014 at 3:24 PM, James Rothering jrother...@codojo.mewrote:
What message would be on the log, or not on the log, what would you be
grep-ing for?
You'd be looking for the broken SSTable to appear in either a
MemtableFlusher line or a compaction line.
Also, why were you
I thought someone asked what was your startup/shutdown procedure, and I
didn't see how startup could impact it. Maybe I mis-rememberd.
On Tue, Mar 25, 2014 at 3:36 PM, Robert Coli rc...@eventbrite.com wrote:
On Tue, Mar 25, 2014 at 3:24 PM, James Rothering jrother...@codojo.mewrote:
What
Well grepping the logs for a file resulted in this:
During startup that file was opened OK.
During runtime the compactionexecutor tried to compact more files that included
this one but threw and exception for another one that is first in that list. So
I do not have more info. In one particular
19 matches
Mail list logo
