Maybe you're running out of file descriptors?
On 29 September 2014 01:31, Jay Patel wrote:
> Hey there,
>
> We've trying out Cassandra-2.1.1 and facing the below exception
> frequently, mainly during the node reboot. File is there with proper
> permissions (as below), not sure why C* is not able
Hey there,
We've trying out Cassandra-2.1.1 and facing the below exception frequently,
mainly during the node reboot. File is there with proper permissions (as
below), not sure why C* is not able to find it.
>>>
ERROR [OptionalTasks:1] 2014-09-27 16:00:20,888 CassandraDaemon.java:167 -
Exception
Hi Jens,
> Just making sure, have you set authenticator and authoriser in
cassandra.yml?
Yes.
Hi Philip,
I guess you are right. I will test that tomorrow morning, and confirm.
Thanks for the help guys.
On Mon, Sep 29, 2014 at 2:10 AM, Philip Thompson <
philip.thomp...@datastax.com> wrote:
>
Got it.. and it works too..
…. select * from foo where token(hashcode) >= -9223372036854775808 and
token(hashcode) <= -7378697629483820647 ;
this should allow me to an easy distributed scan and analyze all the data
in the database across machines..
On Sun, Sep 28, 2014 at 4:07 PM, graham sander
Looks like you are looking at old docs (pre Murmer3 partitioner). Latest are
here (don’t think it has changed in 2.1 from 2.0.x)
http://www.datastax.com/documentation/cassandra/2.1/cassandra/configuration/configGenTokens_c.html
Murmer3 is definitely 64 bits
On Sep 28, 2014, at 5:55 PM, Kevin Bu
Hm.. is it 64 bits or 128 bits?
I’m using Murmur3Partitioner
…
I can’t find any documentation on it (as usual.. ha)
This says:
http://www.datastax.com/docs/1.1/initialize/token_generation
> The tokens assigned to your nodes need to be distributed throughout the
entire possible range of tokens
You are running into https://issues.apache.org/jira/browse/CASSANDRA-7967 .
This is fixed in 2.0.11 and 2.1.1, until then I believe you will need to
explicitly grant select permission onto system.schema_triggers to the user
as a workaround.
On Sun, Sep 28, 2014 at 12:53 PM, Jens Rantil wrote:
>
It is expecting a 64 bit value … murmer3 partitioner uses 64 bit long tokens…
where did you get your 128 bit long from, and what partitioner are you using?
On Sep 28, 2014, at 1:39 PM, Kevin Burton wrote:
> I’m trying to query an entire table in parallel by splitting it up in token
> ranges.
>
I’m trying to query an entire table in parallel by splitting it up in token
ranges.
However, it’s not working because I get this:
cqlsh:blogindex> select token(hashcode), hashcode from source where
token(hashcode) >= 0 and token(hashcode) <=
17014118346046923173168730371588410572 limit 10;
Bad
Hi Pinak,
Just making sure, have you set authenticator and authoriser in cassandra.yml?
Cheers,
Jens
———
Jens Rantil
Backend engineer
Tink AB
Email: jens.ran...@tink.se
Phone: +46 708 84 18 32
Web: www.tink.se
Facebook Linkedin Twitter
On Sun, Sep 28, 2014 at 11:08 AM, Pinak Pani
wro
The vendor application is not likely to change a tad.
There are 200+ times more updates and 50x inserts than analytical loads.
I can simply remove the indexes (in the RDBMS) and thus avoid the issue
altogether, but I expect the analytical loads to suffer.
In Cassandra to just be able to query
More info: the RDBMS based db gets changed by writers in a vicinity of 40-50%
of all data e.g. 100GB a week.
The indexes can be defrugged, which is both expensive and time consuming. Many
indexes become quickly out of date.
Not sure what you mean in retrospect to consistency against indexes.
I
It’s always a tradeoff between the level of sophistication of the platform and
how much work you want to do in the application itself.
But, yes, secondary indexing is always added overhead, and added complexity.
And index tables are a viable approach as well. Again, trading off a simpler
platfo
Hi,
I think more information is needed before this question can be answered. In
many cases you manage the indexes by yourself. If that breaks, then you
have a consistency problem or a bug in your own code. Consistency is
tunable (trade off with performance and availability) and bugs can be
fixed.
Thank you Jack,
But I am afraid it may be an overhead. Added complexity.
/Arthur
Original Message
From: Jack Krupansky
To: user
Sent: Sun, Sep 28, 2014 11:03 am
Subject: Re: Indexes Fragmentation
Take a look at DataStax Enterprise as well, with its integrated Solr indexing
Take a look at DataStax Enterprise as well, with its integrated Solr indexing
of Cassandra data.
-- Jack Krupansky
From: Arthur Zubarev
Sent: Sunday, September 28, 2014 10:55 AM
To: user@cassandra.apache.org
Subject: Indexes Fragmentation
Hi all:
A client on a RDBMS faces quick index fragmen
Hi all:
A client on a RDBMS faces quick index fragmentations, statistics become
inaccurate. Many within 4 hours (fast updates + writes, but mostly updates).
I am looking into replacing the RDBMS with Cassandra.
Will I face the same issue with indexes with Cassandra?
Thank you!
Regards,
Art
Hi,
I see some data stored in Cassandra (2.0.7) being not readable from CQL;
this affects entire partitions, querying this partitions raise a Java
exception:
ERROR [ReadStage:540638] 2014-09-28 12:40:38,992 CassandraDaemon.java (line
198) Exception in thread Thread[ReadStage:540638,5,main]
java.l
Hi,all
after upgrading to 2.1.0, I found there are many exceptions in system.log.
It appears in nodes upgraded from 2.0 as well as in nodes newly added at
2.1.0. When I set the read repair chance to 0.0, it disappears.
ERROR [SharedPool-Worker-8] 2014-09-27 16:44:50,188 ErrorMessage.java:218 -
Un
Hi,
I have been toying around with CQL. I realized when I GRANT SELECT I lose
authentication. Here is the process: Can someone point out what is wrong?
➜ apache-cassandra-2.1.0 bin/cqlsh -u cassandra -p cassandra
Connected to Test Cluster at 127.0.0.1:9042.
[cqlsh 5.0.1 | Cassandra 2.1.0 | CQL
20 matches
Mail list logo
