solution yet...
On Sun, Apr 17, 2011 at 9:17 PM, csharpplusproject
wrote:
Often, I see the following behavior:
(1) Cassandra works, all nodes are up etc
(2) a &
Often, I see the following behavior:
(1) Cassandra works, all nodes are up etc
(2) a 'move' operation is being run on one of the nodes
(3) following this 'move' operation, even after a couple of hours / days
where it is obvious the operation has ended, the node which had 'moved'
remains with a s
ently pack them up. Where "efficiently" means not using JSON.
http://wiki.apache.org/cassandra/LargeDataSetConsiderations
http://wiki.apache.org/cassandra/CassandraLimitations
Aaron
On 13 Apr 2011, at 15:48, csharpplusproject wrote:
> Aaron,
>
> Thank you so much for your he
t a small single node scale, most performance issues can be
solved.
Aaron
On 12 Apr 2011, at 15:34, csharpplusproject wrote:
> Hi Aaron,
>
> Yes, of course it helps, I am starting to get a flavor of
> Cassan
n and see if the data model works for you at a
small single node scale, most performance issues can be solved.
Aaron
On 12 Apr 2011, at 15:34, csharpplusproject wrote:
> Hi Aaron,
>
> Yes, of course it helps, I am starting to get a flavor of Cassandra --
> thank you very muc
Hi Aaron,
Yes, of course it helps, I am starting to get a flavor of Cassandra --
thank you very much!
First of all, by 'interactive' queries, are you referring to 'real-time'
queries? (meaning, where experiments data is 'streaming', data needs to
be stored and following that, the query needs to b
