Dne 18.10.2011 22:35, aaron morton napsal(a):
Looks like the column meta for the CF specifies a column name that is
not a valid Long. I seem to remember a bug like this something in the
past.
but why are columns in system tables untyped? if it was declared as
long, its impossible to insert bad
Anthony,
We're in exactly the same boat. We are waiting on DataStax Enterprise to
see if it can ease the pain of SOLR schemas.
In the meantime, I just submitted a native REST layer for Cassandra.
https://issues.apache.org/jira/browse/CASSANDRA-3380
(Hopefully, it will get integrated soon. Vote i
I'm using a cassandra version compiled from 1.0.0 github HEAD.
I have 3 nodes, A B and C, on node A I run a client, which talks only
to B as the coordinator.
the performance is pretty good, a QUORUM read+write takes < 10ms.
but then I shutdown C, quickly the performance starts to degrade, and
Hi, what is your replication_factor?
2011/10/19 Yang
> I'm using a cassandra version compiled from 1.0.0 github HEAD.
>
> I have 3 nodes, A B and C, on node A I run a client, which talks only
> to B as the coordinator.
>
> the performance is pretty good, a QUORUM read+write takes < 10ms.
>
>
3
sorry forgot this important info
On Oct 19, 2011 11:31 AM, "Jérémy SEVELLEC" wrote:
> Hi, what is your replication_factor?
>
> 2011/10/19 Yang
>
>> I'm using a cassandra version compiled from 1.0.0 github HEAD.
>>
>> I have 3 nodes, A B and C, on node A I run a client, which talks only
>> t
The current version scheme in the "riptano" repository puts 1.0.0rc2 as
the successor to 1.0.0 final. I think this will resolve itself with the
1.0.1 release (or later), but it's broken right now.
[root@david-onebox ~]# yum -y update
Loaded plugins: presto
Setting up Update Process
Resolving Depen
Thanks for pointing this out - we'll get it re-rolled shortly.
On Wed, Oct 19, 2011 at 2:54 PM, David Strauss wrote:
> The current version scheme in the "riptano" repository puts 1.0.0rc2 as
> the successor to 1.0.0 final. I think this will resolve itself with the
> 1.0.1 release (or later), but
Greets,
As you may have heard, we're having a Cassandra meetup during
ApacheCon next month in Vancouver[1]. This meetup is 100% free, 100%
open to everyone (whether you're registered for the conference, or
not), and 110% Cassandra. If that's not enough, come for the beer.
This year we're aiming
Updated the RPM release tag to *-2 and that straightened everything
out. Thanks again for bringing this up. Please let me know if there
are any other issues.
On Wed, Oct 19, 2011 at 2:54 PM, David Strauss wrote:
> The current version scheme in the "riptano" repository puts 1.0.0rc2 as
> the succe
Ok.
I think a degration could be normal because your cluster is in a degraded
state when a node is down.
With a replication_factor of 3 and with a 3 nodes cluster, each data you
write is replicated on each node. As One node is down, when writing, it's
impossible to send a replica on the down node
Hi,
Cassandra 1.0. I am getting the following exception from a simple map
reduce job. It seems like the local mapper is working.
I tried many combinations of hostname, localhost, ip in /etc/hosts vs
listen_address. Didn't seem to resolve this.
Any inputs will be appreciated.
Thanks,
-gabe
W
11 matches
Mail list logo
