>
>
> Any ideas what might be wrong or which prerequisites need to be met? This
> is the first request for a connection.
>
>
>
Sam makes a good point. Make sure you have the username and password
properties set in the configuration file:
https://github.com/apache/incubator-usergrid/blob/master/sta
I don't know Usergrid at all, but the error can be reproduced with cqlsh by
supplying an empty string for the username, e.g bin/cqlsh -u "" -p
cassandra
So I guess something in Usergrid is not setting it correctly.
On Sat, Jul 25, 2015 at 5:22 PM, Andreas Schlüter <
dr.andreas.schlue...@gmx.de> wr
Update: I've reverted hinted_handoff_enabled back to its default value of
true and the errors stopped. Is this just a coincidence, or could be
related?
On Sun, Oct 6, 2013 at 7:23 PM, Ran Tavory wrote:
> Pardon me, now with the appropriate subject line...
>
> Hi, I have a small cluster of 1.2.
More to add on this:
This is happening for column families created via CQL3 with collection type
columns and without "WITH COMPACT STORAGE".
On Fri, Sep 20, 2013 at 12:51 AM, Yuki Morishita wrote:
> Sounds like a bug.
> Would you mind filing JIRA at
> https://issues.apache.org/jira/browse/CASS
Sounds like a bug.
Would you mind filing JIRA at https://issues.apache.org/jira/browse/CASSANDRA?
Thanks,
On Thu, Sep 19, 2013 at 2:12 PM, Vivek Mishra wrote:
> Hi,
> I am trying to use sstableloader to load some external data and getting
> given below error:
> Established connection to initial
Hi,
On Mon, Jul 29, 2013 at 11:23 AM, aaron morton wrote:
> The error is because the underlying CF is not defined using a composite type
> for the comparator.
>
> CREATE TABLE "RRD" (
> key text,
> column1 blob,
> value blob,
> PRIMARY KEY (key, column1)
> ) WITH COMPACT STORAGE AND
>
> Looks
Also it is probably worth to mention:
1. I see no other errors in logs except that one;
2. Sometimes connected clients receive "Request did not complete within
rpc_timeout.", even if they are accessing other tables.
3. Sometimes, some cells from another tables may read as NULL when they are
in fact
Cassandra 1.2.8 still have this issue.
Possible recipe to reproduce: create the table as described in the first
message of this thread; write 3000 rows of 10MB each at the rate about
0.1..1 request per second.
Maybe this behavior is caused by incremental compaction of large rows...
On Mon, Jul 2
wrong?
Adriano.
From: aaron morton [mailto:aa...@thelastpickle.com]
Sent: Lunes, 29 de Julio de 2013 05:23 a.m.
To: user@cassandra.apache.org
Subject: Re: AssertionError during ALTER TYPE in 1.2.5
The error is because the underlying CF is not defined using a composi
The error is because the underlying CF is not defined using a composite type
for the comparator.
> CREATE TABLE "RRD" (
> key text,
> column1 blob,
> value blob,
> PRIMARY KEY (key, column1)
> ) WITH COMPACT STORAGE AND
Looks like this PRIMARY KEY (key, column1) is incorrect.
That says "Th
Great. Let me know what you find!
Thanks!
Paul
Sent from my iPhone
On Jul 27, 2013, at 2:47 AM, Pavel Kirienko
wrote:
> Hi Paul,
>
> I checked out your issue, looks the same indeed. Probably this can be reproed
> simply by writing large rows (> 10MB) on high rates.
> I'm going to try 1.2.7
Hi Paul,
I checked out your issue, looks the same indeed. Probably this can be
reproed simply by writing large rows (> 10MB) on high rates.
I'm going to try 1.2.7 then will be back with results.
On Sat, Jul 27, 2013 at 12:18 AM, Paul Ingalls wrote:
> This is the same issue we have been seeing.
This is the same issue we have been seeing. Still no luck getting a simple
repro case for creating a JIRA issue. Do you have something simple enough to
drop in a JIRA report?
Paul
On Jul 26, 2013, at 8:06 AM, Pavel Kirienko
wrote:
> Hi list,
>
> We run Cassandra 1.2 on three-node cluster.
0/src/java/org/apache/cassandra/service/StorageService.java#L549
-Wei
- Original Message -
From: "Dean Hiller"
To: user@cassandra.apache.org, "Wei Zhu"
Sent: Monday, June 24, 2013 12:04:10 PM
Subject: Re: AssertionError: Unknown keyspace?
Yes, it would be ni
.org>"
mailto:user@cassandra.apache.org>>, Wei Zhu
mailto:wz1...@yahoo.com>>
Date: Monday, June 24, 2013 12:36 PM
To: "user@cassandra.apache.org<mailto:user@cassandra.apache.org>"
mailto:user@cassandra.apache.org>>
Subject: Re: AssertionError: Unknown keyspace?
I h
user@cassandra.apache.org
Sent: Monday, June 24, 2013 10:34 AM
Subject: Re: AssertionError: Unknown keyspace?
On Mon, Jun 24, 2013 at 6:04 AM, Hiller, Dean wrote:
> Oh shoot, this is a seed node. Is there documentation on how to bootstrap
> a seed node? If I have seeds of A, B, C for every mac
On Mon, Jun 24, 2013 at 6:04 AM, Hiller, Dean wrote:
> Oh shoot, this is a seed node. Is there documentation on how to bootstrap
> a seed node? If I have seeds of A, B, C for every machine on the ring and
> I am bootstrapping node B, do I just modify cassandra.yaml and remove node
> B from the y
Oh shoot, this is a seed node. Is there documentation on how to bootstrap
a seed node? If I have seeds of A, B, C for every machine on the ring and
I am bootstrapping node B, do I just modify cassandra.yaml and remove node
B from the yaml file temporarily and boot it up (Note, I still received
th
Ah, so digging deeper, it is not bootstrapping. How do I force the node
to bootstrap? (this is version 1.2.2 and the other nodes somehow knew to
bootstrap automatically but this one I need to force for some reason). I
remember there was a property for this.
NOTE: I enabled some debug logs and a
Would you mind creating a new one? Since that former issue has been closed
a long time ago (and I highly suspect that the use of vnodes is not
irrelevant here, so this is kind of new (it may not be a new bug per-se,
but vnodes may make if way more likely to reproduce)).
Thanks,
Sylvain
On Tue, F
https://issues.apache.org/jira/browse/CASSANDRA-4206
Regards,
Patrik
On Tue, May 1, 2012 at 03:46, Jonathan Ellis wrote:
> On Mon, Apr 30, 2012 at 2:11 PM, Patrik Modesto
> wrote:
>> I think the problem is somehow connected to an IntegerType secondary
>> index.
>
> Could be, but my money is on
On Mon, Apr 30, 2012 at 2:11 PM, Patrik Modesto
wrote:
> I think the problem is somehow connected to an IntegerType secondary
> index.
Could be, but my money is on the supercolumns in the HH data model.
Can you create a jira ticket?
--
Jonathan Ellis
Project Chair, Apache Cassandra
co-founder
The schema for the user defined CF's should not matter. The exceptions has to
do with compacting the HintedHandoff CF.
With regard to the failed read, is this happening at CL QUOURM ?
Can you remember if the assertion was raised while the cluster was still under
load ?
Cheers
--
Hi Aaron,
it's still an issue. However it's difficult to reproduce because I'd
need to insert data to Cassandra for day or more which is not
possible.
I think the problem is somehow connected to an IntegerType secondary
index. I had a different problem with CF with two secondary indexes,
the firs
Looks a bit like https://issues.apache.org/jira/browse/CASSANDRA-3579 but that
was fixed in 1.0.7
Is this still an issue ? Are you able to reproduce the fault ?
Cheers
-
Aaron Morton
Freelance Developer
@aaronmorton
http://www.thelastpickle.com
On 27/04/2012, at 6:56 PM, Patr
https://issues.apache.org/jira/browse/CASSANDRA-3579
thanks
Ramesh
On Tue, Dec 6, 2011 at 2:16 AM, Sylvain Lebresne wrote:
> Do you mind opening a ticket on
> https://issues.apache.org/jira/browse/CASSANDRA ?
>
> Thanks
>
> --
> Sylvain
>
> On Tue, Dec 6, 2011 at 12:52 AM, Ramesh Natarajan wro
Do you mind opening a ticket on
https://issues.apache.org/jira/browse/CASSANDRA ?
Thanks
--
Sylvain
On Tue, Dec 6, 2011 at 12:52 AM, Ramesh Natarajan wrote:
> Hi,
>
> We are running a 8 node cassandra cluster running cassandra 1.0.5.
> All our CF use leveled compaction. We ran a test where we
Looks like a bug. I've created
https://issues.apache.org/jira/browse/CASSANDRA-3440.
On Tue, Nov 1, 2011 at 5:50 PM, Ramesh Natarajan wrote:
> We have a 8 node cassandra cluster running 1.0.1. After running a load
> test for a day we are seeing this exception in system.log file. At
> this time w
This (https://issues.apache.org/jira/browse/CASSANDRA-2653) is fixed
in 0.7.7, which will be out soon.
On Tue, Jul 12, 2011 at 9:13 PM, Kyle Gibson
wrote:
> Running version 0.7.6-2, recently upgraded from 0.7.3.
>
> I am get a time out exception when I run a particular
> get_indexed_slices, which
Great! I'm not using PIG.
Thanks.
-Original Message-
From: Sylvain Lebresne [mailto:sylv...@datastax.com]
Sent: Wednesday, May 18, 2011 3:07 PM
To: user@cassandra.apache.org
Subject: Re: AssertionError
The compose() and decompose() methods of AbstractType are used only by th
> will query for a lot of data of that type.
>
> Ignace
>
>
> -Original Message-
> From: Desimpel, Ignace [mailto:ignace.desim...@nuance.com]
> Sent: Tuesday, May 17, 2011 3:33 PM
> To: user@cassandra.apache.org
> Subject: RE: AssertionError
>
> Seems li
ect if it is not really needed since I know that I will query
for a lot of data of that type.
Ignace
-Original Message-
From: Desimpel, Ignace [mailto:ignace.desim...@nuance.com]
Sent: Tuesday, May 17, 2011 3:33 PM
To: user@cassandra.apache.org
Subject: RE: AssertionError
Seems
paramT){
return
((ReverseCFFloatValues)paramT).paramByteBuffer.duplicate();
}
-Original Message-
From: Sylvain Lebresne [mailto:sylv...@datastax.com]
Sent: Tuesday, May 17, 2011 2:50 PM
To: user@cassandra.apache.org
Subject: Re: AssertionError
On Tue, May 17
nal Message-
> From: Sylvain Lebresne [mailto:sylv...@datastax.com]
> Sent: Tuesday, May 17, 2011 1:16 PM
> To: user@cassandra.apache.org
> Subject: Re: AssertionError
>
> First thing to do would be to update to 0.7.5.
>
> The assertionError you're running into is
?
Ignace
-Original Message-
From: Sylvain Lebresne [mailto:sylv...@datastax.com]
Sent: Tuesday, May 17, 2011 1:16 PM
To: user@cassandra.apache.org
Subject: Re: AssertionError
First thing to do would be to update to 0.7.5.
The assertionError you're running into is a assertion whe
nting the integer value -1) , the finish is set the highest possible
> value (32 bytes with value 7F, …)
>
>
>
> I tested the same code but with a small data set and all seemed to be OK.
> Even on the same database I get back results without exception if I use
> different String values. I’m
:33 PM
To: user@cassandra.apache.org
Subject: Re: AssertionError
The code is trying to follow the column index for a row in an sstable, but it
cannot skip as many bytes as it would like to to get to the column. Helpfully
the help says running out of bytes is only one of the reasons why this
The code is trying to follow the column index for a row in an sstable, but it
cannot skip as many bytes as it would like to to get to the column. Helpfully
the help says running out of bytes is only one of the reasons why this could
happen:)
Can you provide some more information about the query
No data corruption. There was a bug in the way that the index was
scanned that was manifesting itself when when the index got bigger
than 2GB.
Gary.
On Thu, Apr 15, 2010 at 08:03, Ran Tavory wrote:
> yes, this looks like the same issue, thanks Gary.
> Other than seeing the errors in the log I
yes, this looks like the same issue, thanks Gary.
Other than seeing the errors in the log I haven't seen any other
irregularities. (maybe there are, but they haven't surfaced). Does this
assertion mean data corruption or something else that's worth waiting to
0.6.1 for?
On Thu, Apr 15, 2010 at 2:
Ran,
It looks like you're seeing
https://issues.apache.org/jira/browse/CASSANDRA-866. It's fixed in
0.6.1.
Gary
On Thu, Apr 15, 2010 at 04:06, Ran Tavory wrote:
> When restarting one of the nodes in my cluster I found this error in the
> log. What does this mean?
>
> INFO [GC inspection] 2010
41 matches
Mail list logo
