Sounds like you have an older cassandra-env.sh that it's picking up
from a system directory.
2011/10/26 Amit Schreiber :
>
> Hi,
> After unpacking the 1.0.0 release and running:
> apache-cassandra-1.0.0$ ./bin/cassandra -f
> I get:Error opening zip file or JAR manifest missing :
> ./bin/../lib/ja
Hi,
After unpacking the 1.0.0 release and running:
apache-cassandra-1.0.0$ ./bin/cassandra -f
I get:Error opening zip file or JAR manifest missing :
./bin/../lib/jamm-0.2.2.jarError occurred during initialization of VMagent
library failed to init: instrument
A quick examination of the lib dire
On Tue, Oct 25, 2011 at 5:23 AM, Alexandru Sicoe wrote:
> At the moment I am partitioning the data in Cassandra in 75 CFs
You might consider not using so many column families. I am not a Cassandra
expert, but from what I've seen floated around, there is currently a unique
memtable, commit log,
I have a cluster of 8 nodes all running 1.0. The stats shown on the 1st node
on one of the CFs for the number of keys is much larger than expected. The
first node shows the key count estimate to be 9.2M whereas the rest report
~650K on each node. The 650K is in the correct neighborhood of the numbe
If you need to have this data available outside the private network
then why not create the cluster outside itself? It seems inefficient
that you would do bulk transfers. You might think of an alternate
design using queues, subscribers or exposing Cassandra over HTTP etc.
You could also look at ht
Thanks for the detailed answers Dan, what you said makes sense. I think my
biggest worry right now is making the correct preditions of my data storage
space based on the measurements with the current cluster. Other than that I
should be fairly comfortable with the rest of the HW specs.
Thanks for
This may help determining your data storage requirements ...
http://btoddb-cass-storage.blogspot.com/
On 10/25/11 11:22 AM, "Mohit Anchlia" wrote:
>On Tue, Oct 25, 2011 at 11:18 AM, Dan Hendry
>wrote:
>>> 2. ... So I am going to use rotational disk for the commit log and an
>>>SSD
>>> for da
Can you file a bug report on https://issues.apache.org/jira/browse/CASSANDRA ?
On Tue, Oct 25, 2011 at 1:27 PM, Andy Stec wrote:
> Hi Jonathan,
>
> We're using thrift interface with C++.
>
> Andy
>
> On Tue, Oct 25, 2011 at 12:47 PM, Jonathan Ellis wrote:
>>
>> Are you using the StorageProxy API
Hi Jonathan,
We're using thrift interface with C++.
Andy
On Tue, Oct 25, 2011 at 12:47 PM, Jonathan Ellis wrote:
> Are you using the StorageProxy API directly?
>
> On Tue, Oct 25, 2011 at 12:39 PM, Andy Stec wrote:
> > We're using version 1.0. The following exception shows up in the system
>
On Tue, Oct 25, 2011 at 11:18 AM, Dan Hendry wrote:
>> 2. ... So I am going to use rotational disk for the commit log and an SSD
>> for data. Does this make sense?
>
>
>
> Yes, just keep in mind however that the primary characteristic of SSDs is
> lower seek times which translates into faster rand
> 2. ... So I am going to use rotational disk for the commit log and an SSD
for data. Does this make sense?
Yes, just keep in mind however that the primary characteristic of SSDs is
lower seek times which translates into faster random access. We have a
similar Cassandra use case (time series da
Are you using the StorageProxy API directly?
On Tue, Oct 25, 2011 at 12:39 PM, Andy Stec wrote:
> We're using version 1.0. The following exception shows up in the system log
> periodically. What might be causing this exception? Attached is the full
> system.log.
>
> Thanks,
>
> Andy
>
>
> ERRO
I've removed conf/sample-schema.txt from the source tree; something
like that is better maintained in the wiki.
On Mon, Oct 24, 2011 at 11:04 PM, Maki Watanabe wrote:
> Hello, I'm writing CassandraCli wiki page draft (sorry to late,
> aaron), and found 2 problems in schema-sample.txt shipped wit
On Tue, Oct 25, 2011 at 7:44 AM, Brian O'Neill wrote:
> Sasha,
>
> Thinking a little more about "what problem the REST API solves"...
>
> To be honest, I agree completely. I don't think a REST layer that provides
> the same feature/function as CQL is all that valuable except in cases like I
> des
> of 2-300ms for getting a single row. This seems slow, but is it unusual?
What are those numbers? 2 ms being average? 300 ms a 95th/99th percentile? A
value you saw once? Yes, this *seems* slow given your row definition but
without knowing what the value represents it's almost impossible to ju
Hi everyone,
I am currently in the process of writing a hardware proposal for a Cassandra
cluster for storing a lot of monitoring time series data. My workload is
write intensive and my data set is extremely varied in types of variables
and insertion rate for these variables (I will have to handle
Sasha,
Thinking a little more about "what problem the REST API solves"...
To be honest, I agree completely. I don't think a REST layer that provides
the same feature/function as CQL is all that valuable except in cases like I
described (which may not be all that common). Also, to be honest, I d
Sasha,
Thanks for the feedback. I can appreciate your comment on connection
pooling, and it is certainly a matter of taste/purpose/perspective. In our
case, it helps to have the REST layer because its a more natural fit into
our platform/ecosystem (considering we use COTS ETL tools, workflows, e
Hi Brian,
It's an interesting one. Hope you don't mind some feedback .I see you
have been making rounds publicizing the concept and patch (like on my blog
; ) http://blog.sasha.dolgy.com/2011/05/apache-cassandra-restful-api.html)
For me, and the goals I have, I'm not sure this is fit for p
19 matches
Mail list logo
