Idea:
Put only range end points in the table with primary key (part, remainder)
insert into location (part, remainder, city) values (100,10,Sydney) //
100.0.0.1-100.0.0.10 is Sydney
insert into location (part, remainder, city) values (100,50,Melbourne) //
100.0.0.11-100.0.0.5 is Melb
then
We are currently looking to deploy on the 2.0 line of cassandra, but obviously
are watching for bugs (we are currently on 2.0.2) - we are aware of a couple of
interesting known bugs to be fixed in 2.0.3 and one in 2.1, but none have been
observed (in production use cases) or are likely to
Our hosting provider has a cost effective server with 2 x 4TB disks
with a 16G (or 64G) USB thumb drive option. Would it make sense to put
the Cassandra commit log on the USB thumb disk and use RAID0 to use
both 4TB disks for data (and Ubuntu 12.04)?
Anyone know how long USB flash disks last when
Hi david, we tried it two years ago and the performance of the USB stick
was so dismal we stopped.
Cheers
Le 16 nov. 2013 15:13, David Tinker david.tin...@gmail.com a écrit :
Our hosting provider has a cost effective server with 2 x 4TB disks
with a 16G (or 64G) USB thumb drive option. Would
It's conceivable that one of the faster USB 3.0 sticks would be sufficient
for this. I wouldn't exactly call it an enterprise configuration, but
it's worth considering. Keep in mind that if you are comfortable using your
RF for durability, you can turn off durable_writes on your keyspace and not
It doesn't seem like a great idea. The USB drives typically use dynamic
wear leveling. See this analysis on wear:
In our testing USB tends to be slower. If there is something more integrated
internally would give you better performance
Sent from my iPhone
On Nov 16, 2013, at 8:30 AM, Dan Simpson dan.simp...@gmail.com wrote:
It doesn't seem like a great idea. The USB drives typically use dynamic wear
that is, data consists of of an account id with a timestamp column that
indicates when the account was updated. This is not to be confused with row
insertion/update times tamp maintained by Cassandra for conflict resolution
within the Cassanda Nodes. Furthermore the account has about 200 columns
This approach is similar to Janne's.
But I used a shard as an example to make more even rows, and just converted
each IP to an int.
-- put this in file and run using 'cqlsh -f file
DROP KEYSPACE jacob_test;
CREATE KEYSPACE jacob_test WITH replication = {
'class': 'SimpleStrategy',
Looks like someone has the same (1-4) questions:
https://issues.apache.org/jira/browse/CASSANDRA-6364
-M
graham sanderson wrote in message
news:7161e7e0-cf24-4b30-b9ca-2faafb0c4...@vast.com...
We are currently looking to deploy on the 2.0 line of cassandra, but
obviously are watching for
agreed; that was a parallel issue from our ops (I apologize and will try to
avoid duplicates) - I was asking the question from the architecture side as to
what should happen rather than describing it as a bug. Nonetheless, I/We are
still curious if anyone has an answer.
On Nov 16, 2013, at
Hi all. I'm in the bar napkin phase of coming up with a big app. The
application is going to be a large graph app so I was drawn to Cassandra
because of Titan and the replication of Cassandra is far superior to Neo4j
and other open source systems I have looked at.
The last issue i'm dealing
12 matches
Mail list logo
