am i correct that neither of Cassandra's UUIDTypes (at least in 0.7)
compare UUIDs according to RFC4122 (ie as two unsigned longs)?
A quick question, what if DC2 is down, and after a while it comes back on.
how does the data get sync to DC2 in this case? (assume hint is disable)
Thanks in advance.
On Thu, Nov 17, 2011 at 10:46 AM, Jeremiah Jordan
jeremiah.jor...@morningstar.com wrote:
Pretty sure data is sent to the
I am just curious about which partitioner you are using?
On Thu, Nov 17, 2011 at 4:30 PM, Philippe watche...@gmail.com wrote:
Hi Todd
Yes all equal hardware. Nearly no CPU usage and no memory issues.
Repairs are running in tens of minutes so i don't understand why
replication would be backed
On Sun, Nov 20, 2011 at 4:01 AM, Boris Yen yulin...@gmail.com wrote:
A quick question, what if DC2 is down, and after a while it comes back on.
how does the data get sync to DC2 in this case? (assume hint is disable)
Thanks in advance.
Manually, use nodetool repair in rolling fashion on all
If hinting is off. Read Repair and Manual Repair are the only ways data will
get there (just like when a single node is down).
On Nov 20, 2011, at 6:01 AM, Boris Yen wrote:
A quick question, what if DC2 is down, and after a while it comes back on.
how does the data get sync to DC2 in this
Hi all,
my question may be more philosophical than related technically
to Cassandra, but please bear with me.
Given that a young startup may not know its product full at the early
stages, but that it definitely points to ~200M users,
would Cassandra will be the right way to go?
That is, the
Dotan,
I think that if you're in the early stages you have a basic idea of what
your product is going to be, architecturally speaking. While you may
change your business model, or features at the display layer, I would think
the data models itself would remain relatively similar
if your startup is bootstrapping then cassandra is sometimes to heavy to
start with.
i.e. it needs to be fed ram... you're not going to seriously run it in less
than 1gb per node... that level of ram commitment can be too much while
bootstrapping.
if your startup has enough cash to pay for 3-5
Thanks David.
Stephen: thanks for the tip, we can run a recommended configuration, so
that wouldn't be an issue. I guess I can focus that my questions are on
complexity of development.
After digesting David's answer, I guess my follow up questions would be
- how would you process data in a
IMHO, you should start with something very simple RDBMS and meanwhile
getting handle over Cassandra or other noSql technology. Start out with
simple, but always be aware and conscious of the next thing you will have
in stack. It's timetaking to work with new technology if you are in the
phase of
There is something wrong with the system. Your benchmarks are way off. How
are you benchmarking? Are you using the stress lib included?
On Nov 19, 2011 8:58 PM, Kent Tong freemant2...@yahoo.com wrote:
Hi,
On my computer with 2G RAM and a core 2 duo CPU E4600 @ 2.40GHz, I am
testing the
Jahangir, thanks! however I've noted that we may very well need to scale to
200M users or entities within a short amount of time - say a year or two,
10M within few months.
--
Dotan, @jondot http://twitter.com/jondot
On Sun, Nov 20, 2011 at 11:14 PM, Jahangir Mohammed md.jahangi...@gmail.com
Sounds like you need to figure out what your product is going to do
and what technology will best fit those requirements. I know you're
worried about being agile and all that, but scaling requires you to
use the right tool for the job. Worry about new requirements when they
rear their ugly head
Mostly, they are I/O and CPU intensive during major compaction. If ganglia
doesn't have anything suspicious there, then what is performance loss ?
Read or write?
On Nov 17, 2011 1:01 PM, Maxim Potekhin potek...@bnl.gov wrote:
In view of my unpleasant discovery last week that deletions in
Thanks Aaron, I kept this use-case free as to focus on the higher level
description, it might have been a not a good idea.
But generally I think I got a better intuition from the various answers,
thanks!
--
Dotan, @jondot http://twitter.com/jondot
On Sun, Nov 20, 2011 at 11:52 PM, Aaron
For 99% of current applications requiing a persistent datastore, Oracle,
PgSQL and MySQL variants will suffice.
For the 1% of the applications, consider C* if
(a) you have given up on distributed transactions (ACIDLY; but
NOT BASEICLY)
(b) wondering about this new fangled
I'm using BOP.
Le 20 nov. 2011 13:09, Boris Yen yulin...@gmail.com a écrit :
I am just curious about which partitioner you are using?
On Thu, Nov 17, 2011 at 4:30 PM, Philippe watche...@gmail.com wrote:
Hi Todd
Yes all equal hardware. Nearly no CPU usage and no memory issues.
Repairs are
--- Sent with mail@metro - the new generation of mobile messaging
I will follow exactly this solution - thanks :)
On Fri, Nov 18, 2011 at 9:53 PM, David Jeske dav...@gmail.com wrote:
On Thu, Nov 17, 2011 at 1:08 PM, Maciej Miklas
mac.mik...@googlemail.comwrote:
A) Skinny rows
- row key contains login name - this is the main search criteria
- login
19 matches
Mail list logo
