nment?
Thanks,
Diane
On Fri, Jul 18, 2014 at 2:43 PM, Diane Griffith
wrote:
> Okay here are the data samples.
>
> Column Family Schema again:
> CREATE TABLE IF NOT EXISTS foo (key text, col_name text, col_value text,
> PRIMARY KEY(key, col_name))
>
> CQL Write:
>
> INSERT I
change the design requirements.
Thanks,
Diane
On Mon, Jul 21, 2014 at 8:15 PM, Robert Coli wrote:
> On Sun, Jul 20, 2014 at 6:12 PM, Diane Griffith
> wrote:
>
>> I am running tests again across different number of client threads and
>> number of nodes but this time I tweaked
those?
3. What are reasonable timeout values for smaller vm sizes (i.e. 8GB
RAM, 4 CPUs)?
If anyone has any insight it would be appreciated.
Thanks,
Diane
On Fri, Jul 18, 2014 at 2:23 PM, Tyler Hobbs wrote:
>
> On Fri, Jul 18, 2014 at 8:01 AM, Diane Griffith
> wrote:
>
>
with the data/schema?
Thanks,
Diane
On Fri, Jul 18, 2014 at 6:46 AM, Benedict Elliott Smith <
belliottsm...@datastax.com> wrote:
> How many columns are you inserting/querying per key? Could we see some
> example CQL statements for the insert/read workload?
>
> If you a
when you
> build your larger cluster this is lost so performance appears to degrade
> (for instance).
>
>
> On Fri, Jul 18, 2014 at 12:25 PM, Diane Griffith
> wrote:
>
>> The column family schema is:
>>
>> CREATE TABLE IF NOT EXISTS foo (key text, col_name text, co
g
> columns.
>
> -- Jack Krupansky
>
> *From:* Diane Griffith
> *Sent:* Thursday, July 17, 2014 6:21 PM
> *To:* user
> *Subject:* Re: horizontal query scaling issues follow on
>
> So do partitions equate to tokens/vnodes?
>
> If so we had configured all
there and that was the problem.
And if I do that do I need to do more than comment out num_tokens?
Thanks,
Diane
On Thu, Jul 17, 2014 at 6:58 PM, Robert Coli wrote:
> On Thu, Jul 17, 2014 at 3:21 PM, Diane Griffith
> wrote:
>
>> So do partitions equate to tokens/vnodes?
&
handle more data – more token values
> or partitions.)
>
> -- Jack Krupansky
>
> *From:* Diane Griffith
> *Sent:* Thursday, July 17, 2014 1:33 PM
> *To:* user
> *Subject:* horizontal query scaling issues follow on
>
>
> This is a follow on re-post to clarify wha
ry, beefier I/O and networking) to handle large queries, or
> maybe simple, Cassandra-style “horizontal scaling” (adding nodes) will be
> sufficient. Sure, you can tune Cassandra for single-node performance, but
> that seems lot a lot of extra work, to me, compared to adding more cheap
&g
This is a follow on re-post to clarify what we are trying to do, providing
information that was missing or not clear.
Goal: Verify horizontal scaling for random non duplicating key reads using
the simplest configuration (or minimal configuration) possible.
Background:
A couple years ago we
ame keys is not
long enough given the fact we are not doing different offsets for each
client thread.
Thanks,
Diane
On Thu, Jul 17, 2014 at 3:53 AM, Duncan Sands
wrote:
> Hi Diane,
>
>
> On 17/07/14 06:19, Diane Griffith wrote:
>
>> We have been struggling proving out linear re
We have been struggling proving out linear read performance with our
cassandra configuration, that it is horizontally scaling. Wondering if
anyone has any suggestions for what minimal configuration and approach to
use to demonstrate this.
We were trying to go for a simple set up, so on the keyspa
versus not.
Thanks,
Diane
On Wed, Jul 16, 2014 at 3:02 PM, Robert Coli wrote:
> On Wed, Jul 16, 2014 at 11:31 AM, Diane Griffith
> wrote:
>
>> Being a newbie, can you point out where in the documentation it talks of
>> waiting 2 minutes between starts of each node?
&
Being a newbie, can you point out where in the documentation it talks of
waiting 2 minutes between starts of each node?
I ask this because I had looked at what was documented for clustering and
even for backup and restore and did not feel I saw anything that mentioned
this. Remember I also posted
, Robert Coli wrote:
> On Wed, Jul 9, 2014 at 3:36 PM, Diane Griffith
> wrote:
>
>> Hope someone can help. We are having issues restoring all nodes of a
>> cassandra 2.0 cluster from a snapshot. I have reviewed the instructions
>> [Restoring from a snapshot][1]
>>
>
Hope someone can help. We are having issues restoring all nodes of a
cassandra 2.0 cluster from a snapshot. I have reviewed the instructions
[Restoring from a snapshot][1]
Specific steps done include:
1. All data had been flushed from the memtables.
2. All nodes were compacted down to 1 sst
16 matches
Mail list logo
