Then this may be the issue. I'll see if I can regenerate something
with 10.0.0 version tomorrow.
On Mon, Aug 16, 2010 at 11:45 PM, Thorvaldsson Justus
wrote:
> Using beta, made a describe_version(), got 10.0.0 as reply, aint using gem
> though, just thrift from java
> /Justus
>
> -Ursprungl
Using beta, made a describe_version(), got 10.0.0 as reply, aint using gem
though, just thrift from java
/Justus
-Ursprungligt meddelande-
Från: Benjamin Black [mailto:b...@b3k.us]
Skickat: den 17 augusti 2010 08:37
Till: user@cassandra.apache.org
Ämne: Re: Cassandra gem
I'm testing wit
I'm testing with the default cassandra.yaml.
I cannot reproduce the output in that gist, however:
>> thrift_client = client.instance_variable_get(:@client)
=> nil
>>
Also, the Thrift version for 0.7 is 11.0.0, according to the code I
have. Can someone comment on whether 0.7 beta1 is at Thrift i
thrift (0.2.0.4)
thrift_client (0.4.6, 0.4.3)
On Mon, Aug 16, 2010 at 8:51 PM, Mark wrote:
> On 8/16/10 6:19 PM, Benjamin Black wrote:
>>
>> client = Cassandra.new('system', '127.0.0.1:9160')
>
> Brand new download of beta-0.7.0-beta1
>
> http://gist.github.com/528357
>
> Which thrift/thrift_cli
On 8/16/10 8:51 PM, Mark wrote:
On 8/16/10 6:19 PM, Benjamin Black wrote:
client = Cassandra.new('system', '127.0.0.1:9160')
Brand new download of beta-0.7.0-beta1
http://gist.github.com/528357
Which thrift/thrift_client versions are you using?
FYI also tested similar setup on another machi
On 8/16/10 6:19 PM, Benjamin Black wrote:
client = Cassandra.new('system', '127.0.0.1:9160')
Brand new download of beta-0.7.0-beta1
http://gist.github.com/528357
Which thrift/thrift_client versions are you using?
i followed the alternative approach for handling a failed node here:
http://wiki.apache.org/cassandra/Operations
i.e. bringing up a replacement node with the same ip, bootstrapping it
into the same token used by the failed node (using the InitialToken config
parameter), then doing a repair. a
Yes. definitely open a ticket.
Gary
On Mon, Aug 16, 2010 at 20:05, Arya Goudarzi wrote:
> While inserting into a 3 node cluster, one of the nodes got this exception in
> its log:
>
> ERROR [MIGRATION-STAGE:1] 2010-08-16 17:46:24,090 CassandraDaemon.java (line
> 82) Uncaught exception in thread
Thanks for this update.
After another day at work, and more reading into the Cassandra's underlying
model, I think the problem i am encountering is less due to HBase and more
with user error and a highly faulty cluster.
Cassandra's clean api and integration with thrift were the two biggest
factor
$ irb
>> require "lib/cassandra/0.7"
=> true
>> client = Cassandra.new('system', '127.0.0.1:9160')
=> #
>> client.keyspaces
=> ["system"]
>> client.partitioner
=> "org.apache.cassandra.dht.RandomPartitioner"
>>
On Mon, Aug 16, 2010 at 5:46 PM, Mark wrote:
> On 8/16/10 3:58 PM, Benjamin Black wro
can you gist the code?
On Mon, Aug 16, 2010 at 5:46 PM, Mark wrote:
> On 8/16/10 3:58 PM, Benjamin Black wrote:
>>
>> If you pulled before a couple hours ago and did not use the 'trunk'
>> branch, then you don't have current code. I merged the trunk branch
>> to master earlier today and sent a
While inserting into a 3 node cluster, one of the nodes got this exception in
its log:
ERROR [MIGRATION-STAGE:1] 2010-08-16 17:46:24,090 CassandraDaemon.java (line
82) Uncaught exception in thread Thread[MIGRATION-STAGE:1,5,main]
java.util.concurrent.ExecutionException: java.lang.IllegalArgument
On 8/16/10 3:58 PM, Benjamin Black wrote:
If you pulled before a couple hours ago and did not use the 'trunk'
branch, then you don't have current code. I merged the trunk branch
to master earlier today and sent a pull request for the fauna repo to
get the changes, as well. Also fixed a bug ano
If you pulled before a couple hours ago and did not use the 'trunk'
branch, then you don't have current code. I merged the trunk branch
to master earlier today and sent a pull request for the fauna repo to
get the changes, as well. Also fixed a bug another user found when
running with Ruby 1.9.
perhaps you have multiple cassandra.yaml on your classpath. if you
enable debug logging, it tells you the full path to the file it is
reading.
On Mon, Aug 16, 2010 at 4:05 PM, Peter Harrison wrote:
> Hi everyone,
>
> I'm trying to to get the beta of 0.7.0 up and running. I have had a
> previous
Just upgraded my cassandra gem today to b/cassandra fork and noticed
that the transport changed. I re-enabled TFramedTransport in
cassandra.yml but my client no longer works. I keep receiving the
following error.
Thrift::ApplicationException: describe_keyspace failed: unknown result
from
Hi everyone,
I'm trying to to get the beta of 0.7.0 up and running. I have had a
previous build from a couple of weeks ago working okay; one that I
built myself from source.
>From both a recent build of Cassandra from source and from the
distributed binaries I am getting the following on start:
#
Adam,
I built the latest from the 0.6 branch and it's working fine (no missing
keys or duplicates).
David
-Original Message-
From: David McIntosh [mailto:da...@radiotime.com]
Sent: Friday, August 13, 2010 4:20 PM
To: 'user@cassandra.apache.org'
Subject: RE: error using get_range_slice w
Useful config option, perhaps?
On Mon, Aug 16, 2010 at 8:51 AM, Jonathan Ellis wrote:
> That's a tough call -- you can also come up with scenarios where you'd
> rather have it read-only than completely dead.
>
> On Wed, Aug 11, 2010 at 12:38 PM, Ran Tavory wrote:
>> Due to administrative error o
Hello,
Anyone interested in doing map/reduce on Cassandra data should take a
look at Cassandra Storage Handler for Hive. Storage handlers give Hive
the ability to work with data outside HDFS in a more natural way.
Support is now in place for reading and writing to/from Standard
Column Families (no
That's a tough call -- you can also come up with scenarios where you'd
rather have it read-only than completely dead.
On Wed, Aug 11, 2010 at 12:38 PM, Ran Tavory wrote:
> Due to administrative error one of the hosts in the cluster lost permission
> to write to it's data directory.
> So I started
Rob Coli digg.com> writes:
> As I understand Julie's case, she is :
>
> a) initializing her cluster
> b) inserting some number of unique keys with CL.ALL
> c) noticing that more disk space (6x?) than is expected is used
> d) but that she gets expected usage if she does a major compaction
Yes, t
Well it depends on what you need and want. I didn't mean the round robin thing
because that part is really not very hard to make or understand. Hector uses a
smart one that tries to connect to other servers if it timeout and other
things. But with Hector as a whole I think you get so much featur
You mean list a few hosts and connect them in a round robin , like Tavory
said?
On Mon, Aug 16, 2010 at 8:36 PM, Thorvaldsson Justus <
justus.thorvalds...@svenskaspel.se> wrote:
> http://wiki.apache.org/cassandra/ClientOptions
>
>
>
> but I prefer writing my own code, trying to write something s
http://wiki.apache.org/cassandra/ClientOptions
but I prefer writing my own code, trying to write something simple API working
with 0.7.0beta1 amt though am I the only one that thinks NOT using clients like
hector is simpler (in a way, to feel in control at least)?
Från: Ying Tang [mailto:ivytan
Could you just recommond some higher lever libraries?
On Mon, Aug 16, 2010 at 6:25 PM, Ran Tavory wrote:
> The common practice is to connect to a few hosts and send request in round
> robin or other lb tactic. The hosts are symmetric so any host will do.
> There are also higher lever libraries
The common practice is to connect to a few hosts and send request in round
robin or other lb tactic. The hosts are symmetric so any host will do.
There are also higher lever libraries that help with that as well as
connection pooling and other goodies
On Mon, Aug 16, 2010 at 1:14 PM, Ying Tang wr
After reading the docs and the thrift demo , i found that if the demo
,if we want to connect to the database , we must first do "TTransport tr =
new TSocket("localhost", 9160) " .
Then we operate on the database through this TTransport .
But this operation assigns a fixed IP , so all r
Hi Eric,
no general problems per se with long rows. The only problem was that
retrieving the whole row took about 10-20 seconds and the timeouts I had
set (both the Cassandra RPC, as well as in the client library I used)
were slower, so these requests could never complete. This gave me a bit
29 matches
Mail list logo
