Okay so as most know this practice is called a wide row - we use them quite a
lot. However, as your schema shows it will cache (while being active) all the
row in memory. One way we got around this issue was to basically create some
materialized views of any more common data so we can easily ge
We are using 0.8.6
On 29/09/2011, at 21:19 PM, Jonathan Ellis wrote:
> Are you on a current Cassandra release? If not you could be seeing
> https://issues.apache.org/jira/browse/CASSANDRA-2870
>
> On Thu, Sep 29, 2011 at 7:02 PM, Anthony Ikeda
> wrote:
>> We seem to be having issues with out
From a usability standpoint, elastic search is looking promising. I'll have to
get more info through use on it's distribution as well.
Thanks
:)
On 28/09/2011, at 14:01 PM, Mohit Anchlia wrote:
> look at elasticsearch too. It shards differently.
>
> On Wed, Sep 28, 2011 at 1:45 PM, Rafael Al
loser to
> 30MB. We see the same kind of variability in both clusters.
>
>
> For both clusters, we're running stress tests with the following options:
>
>
> --consistency-level=LOCAL_QUORUM --threads=4
> --replication-strategy=NetworkTopologyStrategy
> --str
What snitch do you have configured? We typically see a proper spread of data
across all our nodes equally.
Anthony
On 17/09/2011, at 10:06 AM, Chris Marino wrote:
> Hi, I have a question about what to expect when running a cluster across
> datacenters with Local Quorum consistency.
>
> My si
Okay, it looks like we have found the problem.
What had happened was that the infrastructure team had used the same image to
prepare the different nodes. Unfortunately because there was an issue with the
original image, the problem was migrated across to the other node thus breaking
the communi
Thanks Jonathan,
I just had one of our devs playing around with it and he said he had problems
with some of the column names of which we delimit using a dash (-) using the
JDBC drivers e.g.
SELECT m--hash(value) FROM column_family…..
If this is not a problem then I have my questions answered.
Speaking from personal experience (and believe me it all comes down to this) we
attempted a DAO approach as well. However, we found that based upon all the
mutator.addInsertion()s we were creating across column families everything
ended up in the same DAO - we only have 3 main Column Families th
