I am working on a patch for you.
On Thu, Jan 14, 2010 at 9:21 PM, JKnight JKnight wrote:
> Dear all,
>
> This is my data model
>
>
>
>
>
> Could you help me to detect problem?
>
> Thank a lot for support
>
> On Wed, Jan 13, 2010 at 10:49 AM, Jonathan Ellis wrote:
>>
>> What is your CF
Dear all,
This is my data model
Could you help me to detect problem?
Thank a lot for support
On Wed, Jan 13, 2010 at 10:49 AM, Jonathan Ellis wrote:
> What is your CF definition in your config file?
>
> On Sun, Jan 10, 2010 at 7:59 PM, JKnight JKnight
> wrote:
> > The attachment
On Thu, Jan 14, 2010 at 9:02 PM, Michael Lee
wrote:
> If a node's data has been damaged, you cannot use new node replace old one
> directly, unless 'removetoken' first.
>
> But, (suppose node A is dead)
> 'removetoken' will complement missing replica due A's death first, it will
> generate lot d
I' am Pan's collogue, allow me make it clear...
Pan's problem is:
If a node's data has been damaged, you cannot use new node replace old one
directly, unless 'removetoken' first.
But, (suppose node A is dead)
'removetoken' will complement missing replica due A's death first, it will
generate l
--
| Range changes |
| Bootstrap |
| Adding new nodes is called "bootstrapping." |
-
Do you mea
2010/1/14 shiv shivaji
> I have looked at performance posts in the forum but was wondering if there
> are general suggestions for using cassandra in production.
>
I'd say pretty obvious stuff:
- Performance test as much as you can
- Choose the following carefully as they're difficult to change:
2010/1/14 Ted Zlatanov :
> On Wed, 13 Jan 2010 13:22:02 -0800 Tatu Saloranta
> wrote:
>
> TS> I think there are 2 separate questions:
>
> TS> (a) Would a path language make sense, and
> TS> (b) How would that be exposed
>
> TS> So I think more developers would be opposed to part (b) of exposing
>
We are looking at using cassandra in production to store close to a billion
documents. Wondering if there are best practices or war room stories that
people can relate to.
Things that are of interest:
1. Low latency for reads, reasonable latency for writes.
2. Supporting up to say 100-1000 writ
On Thu, Jan 14, 2010 at 6:30 AM, XL.Pan wrote:
> *Why not the standard boostrap?
http://wiki.apache.org/cassandra/Operations says that boostrap is the
preferred method for handling node replacement. Please read how that
describes how to handle things because your description of how
bootstrap wor
On Wed, 13 Jan 2010 13:22:02 -0800 Tatu Saloranta wrote:
TS> I think there are 2 separate questions:
TS> (a) Would a path language make sense, and
TS> (b) How would that be exposed
TS> So I think more developers would be opposed to part (b) of exposing
TS> path queries using opaque things like
Ah, yes, the enum thing changed in trunk too. We upgraded our version of
the Thrift compiler for trunk, after 0.5. So 0.4 to 0.5 upgrading does not
need to worry.
On Thu, Jan 14, 2010 at 8:31 AM, Hernan Badenes wrote:
> Yes, ConsistencyLevel was an enum already -- but the thrift generated api,
Yes, ConsistencyLevel was an enum already -- but the thrift generated api,
at that version, generated methods that received an int where a
ConsistencyLevel was declared. (I am looking at
gen-java/.../Cassandra.java from a downloaded 0.4.2). Then one needs to
change the client, assuming you are
On Thu, Jan 14, 2010 at 6:04 AM, Sylvain Lebresne wrote:
> Created, #699 (I have yet to figure out how to assign it to me though).
Added you as a "contributor" so you can do this.
This is not correct. ConsistencyLevel was already an enum in 0.4, and the
constructors don't change until the release after 0.5.
On Thu, Jan 14, 2010 at 7:10 AM, Hernan Badenes wrote:
> I think you also need to upgrade your thrift jar, since the version in 0.5
> is different. And this brings a
I think you also need to upgrade your thrift jar, since the version in 0.5
is different. And this brings a change in enums, which are no longer plain
int values but classes. Constructors of most thrift-generated classes also
change (e.g. new ColumnPath(cf, null, colName) -> new
ColumnPath(cf).s
Hi ALL:
*My issues:
I have a few high-capacity servers, which has about 5T disk space. I know there
are 2 solutions for handling failure, through the wiki. But it's not very
conveninte for me. That is :
Solution 1: new node + removetoken
Add a new node will make lots of data transfer between mach
On Thu, Jan 14, 2010 at 12:15 PM, Kelvin Kakugawa wrote:
> If you're interested, why don't you create a new ticket and assign it
> to yourself. I'd be happy to help you figure out which parts of the
> codebase need to be touched.
Created, #699 (I have yet to figure out how to assign it to me tho
Sylvain,
If you're interested, why don't you create a new ticket and assign it
to yourself. I'd be happy to help you figure out which parts of the
codebase need to be touched.
-Kelvin
btw, I'm working on Issue #580 which will add versioning to Cassandra.
An aspect of this feature is that I am
On Thu, Jan 14, 2010 at 6:46 AM, August Zajonc wrote:
> I personally like this last option of expiring entire sstables. It seems
> significantly more efficient then scrubbing data. The granularity might be a
> bit high, but by columnfamily seems a reasonable trade-off in the short run
> for an eas
19 matches
Mail list logo
