Thats not right
since 1.1.X it will used
my hint:
take a look at
commitlog_total_space_in_mb
it seams to be maped to off heap usage
the fix for taking the whole off-heap-memory is included in 1.1.3
the next parameter you have to take a look
disk_access_mode: mmap_index_only
#disk_access_mode:
Hi all,
What are the advantages of allocating a cluster for a single application vs
running multiple applications on the same cassandra cluster? Is any of the
models suggested over the other?
Thanks.
--
Ersin Er
Hi!
I am running 1.0.8.
So if I understand correctly both Memtable and Key cache are stored in the
heap. (I don't have row cache)
SSTables are mapped to operating system's virtual memory system, so if I
increase heap I guess there will be less memory for this?
I have seen the changes in 1.1, but
4. Prepared Statements
It should be possible to prepare statements that do not take any arguments. This
simplifies the client development significantly (otherwise everybody
has to write
his own parser to determine the number of arguments) and might also speed up
common queries. The current
Just an opinion here as we are having to do this ourselves loading tons of
researchers datasets into one clusters. We are going the path of one keyspace
as it makes it easier if you ever want to mine the data so you don't have to
keep building different clients for another keyspace. We ended
We are running Cassandra 1.1.2 on EC2. Our database is primarily all
counters and we don't do any
deletes.
Does nodetool repair do anything for such a database. All the docs I read
for nodetool repair suggests
that nodetool repair is needed only if there is deletes.
Thanks,
Senthil
On Wed, Aug 22, 2012 at 8:37 AM, Senthilvel Rangaswamy
senthil...@gmail.com wrote:
We are running Cassandra 1.1.2 on EC2. Our database is primarily all
counters and we don't do any
deletes.
Does nodetool repair do anything for such a database. All the docs I read
for nodetool repair suggests
If you are staring out small one logical/physical cluster is probably
the best and only approach.
Long term this is very case by case dependent but I generally believe
Cluster per Application is the best approach. Although I consider it
Cluster per QOS
For our use cases I find that two
I get this:
InvalidRequestException(why:invalid operation for commutative columnfamily
Any thoughts ?
We use Pelops...
On Sun, Aug 19, 2012 at 11:09 AM, Peter Morris mrpmor...@gmail.com wrote:
Is the Windows community edition crippled for network use perhaps, or could
the problem be something else?
It's not crippled but it underperforms Cassandra on Linux. Cassandra
contains various Linux specific optimizations
True, all in one cluster is very comparable to putting your application on
amazon's cloud. When you have lots of apps, you can benefit from a batch
job at night using resources that are not used by your day job apps.
Always tradeoffs of course as if both apps go off at the same timeŠ.well,
you get
We are in the process of building out a new DR system in another Data Center,
and we want to mirror our Cassandra environment to that DR. I have a couple
questions on the best way to do this after reading the documentation on the
Datastax website. We didn't initially plan for this to be a DR
On Wed, Aug 22, 2012 at 2:12 AM, Christoph Hack christ...@tux21b.org wrote:
4. Prepared Statements
FWIW, while I suppose a client author is technically a user of
Cassandra, you appear to be making suggestions related to the
development of Cassandra. As I understand the conceptual seperation
On Wed, Aug 22, 2012 at 11:00 PM, Rob Coli rc...@palominodb.com wrote:
FWIW, while I suppose a client author is technically a user of
Cassandra, you appear to be making suggestions related to the
development of Cassandra. As I understand the conceptual seperation
between lists, you probably
If you didn't see this particular section, you may find it useful:
http://www.datastax.com/docs/1.1/operations/cluster_management#adding-a-data-center-to-a-cluster
Some comments inline:
On Wed, Aug 22, 2012 at 3:43 PM, Bryce Godfrey bryce.godf...@azaleos.comwrote:
We are in the process of
15 matches
Mail list logo