You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@cassandra.apache.org by aaron morton <aa...@thelastpickle.com> on 2011/06/20 01:06:51 UTC
Re: Error trying to move a node - 0.7
I *think* someone had a similar problem once before, moving a node that was the only node in a DC.
Whats version are you using ?
-----------------
Aaron Morton
Freelance Cassandra Developer
@aaronmorton
http://www.thelastpickle.com
On 17 Jun 2011, at 07:42, Ben Frank wrote:
> Hi All,
> I'm getting the following error when trying to move a nodes token:
>
> nodetool -h 145.6.92.82 -p 18080 move 56713727820156410577229101238628035242
> cassandra.in.sh executing for environment DEV1
> Exception in thread "main" java.lang.AssertionError
> at
> org.apache.cassandra.locator.TokenMetadata.firstTokenIndex(TokenMetadata.java:393)
> at
> org.apache.cassandra.locator.TokenMetadata.ringIterator(TokenMetadata.java:418)
> at
> org.apache.cassandra.locator.NetworkTopologyStrategy.calculateNaturalEndpoints(NetworkTopologyStrategy.java:94)
> at
> org.apache.cassandra.service.StorageService.calculatePendingRanges(StorageService.java:807)
> at
> org.apache.cassandra.service.StorageService.calculatePendingRanges(StorageService.java:773)
> at
> org.apache.cassandra.service.StorageService.startLeaving(StorageService.java:1468)
> at
> org.apache.cassandra.service.StorageService.move(StorageService.java:1605)
> at
> org.apache.cassandra.service.StorageService.move(StorageService.java:1580)
> .
> .
> .
>
> my ring looks like this:
>
> Address Status State Load Owns Token
>
> 113427455640312821154458202477256070484
> 145.6.99.80 Up Normal 1.63 GB 36.05%
> 4629135223504085509237477504287125589
> 145.6.92.82 Up Normal 2.86 GB 1.09%
> 6479163079760931522618457053473150444
> 145.6.99.81 Up Normal 2.01 GB 62.86%
> 113427455640312821154458202477256070484
>
>
> '80' and '81' are configured to be in the East coast data center and '82' is
> in the West
>
> Anyone shed any light as to what might be going on here?
>
> -Ben
Re: Query indexed column with key filter
Posted by aaron morton <aa...@thelastpickle.com>.
Currently these are two different types of query, using a key range is equivalent to the get_range_slices() API function and column clauses is a get_indexed_slices() call. So you would be asking for a potentially painful join between.
Creating a column with the same value as the key sounds reasonable.
Cheers
-----------------
Aaron Morton
Freelance Cassandra Developer
@aaronmorton
http://www.thelastpickle.com
On 29 Jun 2011, at 05:31, Daning wrote:
> I found this code
>
> // Start and finish keys, *and* column relations (KEY> foo AND KEY< bar and name1 = value1).
> if (select.isKeyRange()&& (select.getKeyFinish() != null)&& (select.getColumnRelations().size()> 0))
> throw new InvalidRequestException("You cannot combine key range and by-column clauses in a SELECT");
>
> in
>
> http://svn.apache.org/repos/asf/cassandra/trunk/src/java/org/apache/cassandra/cql/QueryProcessor.java
>
>
> This operation is exactly what I want - query by column then filter by key. I want to know why this query is not supported, and what's the good work around for it? At this moment my workaound is to create a column which is exactly same as key.
>
> Thanks,
>
> Daning
Query indexed column with key filter
Posted by Daning <da...@netseer.com>.
I found this code
// Start and finish keys, *and* column relations (KEY> foo AND KEY< bar and name1 = value1).
if (select.isKeyRange()&& (select.getKeyFinish() != null)&& (select.getColumnRelations().size()> 0))
throw new InvalidRequestException("You cannot combine key range and by-column clauses in a SELECT");
in
http://svn.apache.org/repos/asf/cassandra/trunk/src/java/org/apache/cassandra/cql/QueryProcessor.java
This operation is exactly what I want - query by column then filter by
key. I want to know why this query is not supported, and what's the good
work around for it? At this moment my workaound is to create a column
which is exactly same as key.
Thanks,
Daning
Re: Error trying to move a node - 0.7
Posted by Ben Frank <be...@airlust.com>.
Hey Aaron,
I think you're right, I'm using version 0.7 and indeed the node I'm
trying to move is the only node in that data center - I'll steal some
hardware to add to the ring to confirm.
-Ben
On Sun, Jun 19, 2011 at 4:06 PM, aaron morton <aa...@thelastpickle.com>wrote:
> I *think* someone had a similar problem once before, moving a node that was
> the only node in a DC.
>
> Whats version are you using ?
>
> -----------------
> Aaron Morton
> Freelance Cassandra Developer
> @aaronmorton
> http://www.thelastpickle.com
>
> On 17 Jun 2011, at 07:42, Ben Frank wrote:
>
> > Hi All,
> > I'm getting the following error when trying to move a nodes token:
> >
> > nodetool -h 145.6.92.82 -p 18080 move
> 56713727820156410577229101238628035242
> > cassandra.in.sh executing for environment DEV1
> > Exception in thread "main" java.lang.AssertionError
> > at
> >
> org.apache.cassandra.locator.TokenMetadata.firstTokenIndex(TokenMetadata.java:393)
> > at
> >
> org.apache.cassandra.locator.TokenMetadata.ringIterator(TokenMetadata.java:418)
> > at
> >
> org.apache.cassandra.locator.NetworkTopologyStrategy.calculateNaturalEndpoints(NetworkTopologyStrategy.java:94)
> > at
> >
> org.apache.cassandra.service.StorageService.calculatePendingRanges(StorageService.java:807)
> > at
> >
> org.apache.cassandra.service.StorageService.calculatePendingRanges(StorageService.java:773)
> > at
> >
> org.apache.cassandra.service.StorageService.startLeaving(StorageService.java:1468)
> > at
> >
> org.apache.cassandra.service.StorageService.move(StorageService.java:1605)
> > at
> >
> org.apache.cassandra.service.StorageService.move(StorageService.java:1580)
> > .
> > .
> > .
> >
> > my ring looks like this:
> >
> > Address Status State Load Owns Token
> >
> > 113427455640312821154458202477256070484
> > 145.6.99.80 Up Normal 1.63 GB 36.05%
> > 4629135223504085509237477504287125589
> > 145.6.92.82 Up Normal 2.86 GB 1.09%
> > 6479163079760931522618457053473150444
> > 145.6.99.81 Up Normal 2.01 GB 62.86%
> > 113427455640312821154458202477256070484
> >
> >
> > '80' and '81' are configured to be in the East coast data center and '82'
> is
> > in the West
> >
> > Anyone shed any light as to what might be going on here?
> >
> > -Ben
>
>