> Seeds will not auto-bootstrap themselves when you add them to the cluster.
And having a bunch of nodes that aren't even in the cluster (when you
move them around, decommission etc) seems like a bad idea.
As for amount: I would say definitely have at least RF seeds (for some
reason I haven't he
Hi is there any reason why configuring a partitioner per keyspace wouldn't
be possible technically ?
Thanks.
> I have changed absolutely nothing and the work load is perhaps even lower
> than before upgrading because I have paused most updates to the cluster. Did
> a log level change or does this have deeper meaning ?
You don't say which version you upgraded from but I suspect 0.7? JVM
options like heap
> I would think that compaction_throughput_kb_per_sec does have indirect impact
> on disk IO. High number means or setting it to 0 means there is no
> throttling on how much IO is being performed. Wouldn't it impact normal
> reads from disk during the time when disk IO or util is high which
> compa
looks like you are hitting this
https://issues.apache.org/jira/browse/CASSANDRA-3256
Does the repair complete ?
Cheers
-
Aaron Morton
Freelance Cassandra Developer
@aaronmorton
http://www.thelastpickle.com
On 28/09/2011, at 7:04 PM, Philippe wrote:
> Hello,
> Have just ran in
The first thing I can think of is the initial_token for the node must be a
valid token according to the configured partitioner, as the tokens created by
the partitioner are the things stored the distributed hash tree. If you had a
partitioner per KS you would need to configure the initial_token
On Wed, Sep 28, 2011 at 8:32 AM, Philippe wrote:
> Congrats.
> Is there a target date for the release. If not is it likely to be in
> October?
October 8th.
Of course, it's a target only, we make no guarantee. But the beta has been
rather calm (which isn't saying there wasn't a few bugs fixed) s
https://issues.apache.org/jira/browse/CASSANDRA-295
--
Sylvain
On Wed, Sep 28, 2011 at 10:06 AM, aaron morton wrote:
> The first thing I can think of is the initial_token for the node must be a
> valid token according to the configured partitioner, as the tokens created
> by the partitioner are
Thats just a warning, it should keep trying to connect. Does it make any
progress ?
After 8 attempts it should fail with an error.
With the debug option you should get a full stack trace printed if it fails,
can you send that along as well.
It's probably some sort of config problem.
Cheers
Thats the one I was thinking of.
Cheers
-
Aaron Morton
Freelance Cassandra Developer
@aaronmorton
http://www.thelastpickle.com
On 28/09/2011, at 9:12 PM, Sylvain Lebresne wrote:
> https://issues.apache.org/jira/browse/CASSANDRA-295
>
> --
> Sylvain
>
> On Wed, Sep 28, 2011 at
Thanks a lot Shyamal.
That was the solution. It works now :)
regards
Ramesh
On Tue, Sep 27, 2011 at 8:36 PM, Shyamal Prasad wrote:
>
> > "Ramesh" =3D=3D Ramesh S writes:
>
>Ramesh> Hello all, We installed Cassandra on our development
>Ramesh> server , which is a fresh Ubuntu s
On Wed, Sep 28, 2011 at 4:36 AM, aaron morton wrote:
> Thats the one I was thinking of.
>
> Cheers
>
> -
> Aaron Morton
> Freelance Cassandra Developer
> @aaronmorton
> http://www.thelastpickle.com
>
> On 28/09/2011, at 9:12 PM, Sylvain Lebresne wrote:
>
> > https://issues.apache.o
Thank you. You have been very helpful.
We stored only one day worth of data for now. However, we want to store 5 days
worth of data eventually.
That is 5 times more disk space.
That is our main reason for us to look at older SSTables that appears to be
holding only tombstones.
- yuki
___
thanks a lot for help! I don't know what exactly was wrong (because I deleted
everything including java and started from the very beginning) but now
everything seems to work perfectly and I'm doing first stepes with Cassandra.
By the way...
Maybe do you have some useful advices (or you know some
http://screenr.com/5G6
On Wed, Sep 28, 2011 at 11:56 AM, Julio Julio
wrote:
> thanks a lot for help! I don't know what exactly was wrong (because I
> deleted
> everything including java and started from the very beginning) but now
> everything seems to work perfectly and I'm doing first stepes wi
Hi everybody,
Apptegic is hiring software engineers and we are especially interested in
anybody who has developed with and used Cassandra in production.
We are based in Boston and are looking for local people. However, we would love
to hear from Cassandra experts anywhere in the United States.
Hi everyone!
I'm new user of Cassandra (I'm using Cassandra 0.8.6)
and I created CF by command:
create column family People with comparator=UTF8Type and
default_validation_class=UTF8Type;
and then I inserted some values like:
set People[wking][name]='ala';
set People[wking][sname]='sala';
set
I have an app polling a few CFs (select first N * from CF), there were
data in CFs but later were deleted so CFs were empty for a long time. I
found Cassandra CPU usage was getting high to 80%, normally it uses less
than 30%. I issued the select query manually and feel the response is
slow. I h
Well, we go live with our project very soon and we are now looking into what
we will be doing for the next phase. One of the enhancements we would like
to consider is an indexing platform to start building searches into our
application.
Right now we are just using column families to index the info
>From Anthony Ikeda :
> Well, we go live with our project very soon and we are now looking into what
> we will be doing for the next phase. One of the enhancements we would like to
> consider is an indexing platform to start building searches into our
> application.
>
>
> Right now we are just u
look at elasticsearch too. It shards differently.
On Wed, Sep 28, 2011 at 1:45 PM, Rafael Almeida wrote:
> From Anthony Ikeda :
>> Well, we go live with our project very soon and we are now looking into what
>> we will be doing for the next phase. One of the enhancements we would like
>> to con
For background:
Minor compaction will bucket files (see
https://github.com/apache/cassandra/blob/cassandra-0.8.6/src/java/org/apache/cassandra/db/compaction/CompactionManager.java#L989)
and then compact them if they have more than min_compaction_threshold set per
CF.
It will then purge tombst
Sounds like you have non-expired tombstones.
http://wiki.apache.org/cassandra/DistributedDeletes
On Wed, Sep 28, 2011 at 12:35 PM, Daning wrote:
> I have an app polling a few CFs (select first N * from CF), there were data
> in CFs but later were deleted so CFs were empty for a long time. I foun
7?
Sent from my iPhone
On Sep 28, 2011, at 4:18 PM, RAJASHEKAR REDDY wrote:
> ..Your friend wants to help you! Don’t ignore this letter!
> http://alexeist.euweb.cz/com.friend.php?baflucky=16uv0
You should have gotten an error from the CLI saying it cannot parse hex bytes,
because it would now know that the key you are passing is a utf8 / ascii string
to be converted into a bytes.
It's throwing on the 0.8 head, but not in the release. Will try to work out
why, anyway it should do this
if I had to guess I would say it was spending time handling tombstones. If you
see it happen again, and are interested, turn the logging up to DEBUG and look
for messages from something starting with "Slice"
Minor (automatic) compaction will, over time, purge the tombstones. Until then
reads mu
Hey guys,
I'm using a three node cluster running 0.8.6 with rf of 3. Its a freshly
installed cluster with no upgrade history.
I have 6 cfs and only one of them is written into. That cf has around one
thousand keys. A quick key_range_scan verifies this.
However when I do cfstats, I see the following
No it was an upgrade from 0.8.4 or 0.8.5 depending on the nodes.
No cassandra-env files were changed during the update.
Any other ideas? The cluster has just been weird ever since running 0.8.6 :
has anyone else upgraded and not run into this?
Le 28 sept. 2011 09:32, "Peter Schuller" a
écrit :
>>
28 matches
Mail list logo
