Hi,
We,re running cassandra 1.0.3.
I've done some testing with 2 nodes (node A, node B), replication factor 2.
I take node A down, writing some data to node B and then take node A up.
Sometimes hints aren't delivered when node A comes up.
I've done some debugging in org.apache.cassandra.db.Hinted
You're right, good catch.
Do you mind opening a ticket on jira
(https://issues.apache.org/jira/browse/CASSANDRA)?
--
Sylvain
On Thu, Dec 1, 2011 at 10:03 AM, Fredrik L Stigbäck
wrote:
> Hi,
> We,re running cassandra 1.0.3.
> I've done some testing with 2 nodes (node A, node B), replication facto
Hello everyone,
4 node Cassandra 0.8.5 cluster with RF =2.
One node started throwing exceptions in its log:
ERROR 10:02:46,837 Fatal exception in thread Thread[FlushWriter:1317,5,main]
java.lang.RuntimeException: java.lang.RuntimeException: Insufficient disk
space to flush 17296 bytes
at
Yes, I'll do that.
/Fredrik
Sylvain Lebresne skrev 2011-12-01 11:10:
You're right, good catch.
Do you mind opening a ticket on jira
(https://issues.apache.org/jira/browse/CASSANDRA)?
--
Sylvain
On Thu, Dec 1, 2011 at 10:03 AM, Fredrik L Stigbäck
wrote:
Hi,
We,re running cassandra 1.0.3.
I'v
In my application, I need to store the total scores/reputation of the users
as counters and want to show sorted(by score) lists of users. Also want to
implement a name search facility on top of that. Could you suggest any
schema to achieve that using cassandra.
On Wed, Nov 30, 2011 at 12:53 PM,
Unfortunately no.
Second time I did the test:
Restore 4 nodes to a new Cassandra cluster (0.7.8)
Upgrade to 1.0.0
Run nodetool scrub on each node after upgrade before upgrading next node.
Upgrade to 1.0.3
Upgrade to 1.0.5
Run nodetool repair on all nodes.
All process was successful.
What does th
On Thu, Dec 1, 2011 at 11:58 AM, Michael Vaknine wrote:
> Unfortunately no.
>
> Second time I did the test:
>
> Restore 4 nodes to a new Cassandra cluster (0.7.8)
> Upgrade to 1.0.0
> Run nodetool scrub on each node after upgrade before upgrading next node.
> Upgrade to 1.0.3
> Upgrade to 1.0.5
>
Assume for now we have 1 DC and 1 rack with 3 nodes. Ring will look like:
(we use own snitch, which returns DC=0, Rack=0 for this case).
AddressDC Rack Token
1
Sorry, the bug was in our snitch. We're using getHostName() instead of
getCanonicalHostName() to determine DC & Rack and since for local it returns
alias, instead of reverse DNS, DC & Rack numbers are not as expected.
Best regards/ Pagarbiai
Viktor Jevdokimov
Senior Developer
Email:
Hi,
After upgrading cluster to 1.0.5
I am having problems connecting to the cluster using hector
Any help will be aprichiated.
Thanks
Michael
me.prettyprint.hector.api.exceptions.HTimedOutException: TimedOutException()
at
me.prettyprint.cassandra.service.ExceptionsTranslatorImpl.translate
Hi,
I want to use Cassandra for (fast) unit testing with a small number of data.
So, I imagined the Cassandra embedded server I plan to use would start faster
and would be more portable (because no file path depending on OS), without disk
storage mode (so, diskless if you want).
Is there some
If you are writing data with QUORUM or ALL you should be safe to restart
cassandra on that node. If the extra space is all from *tmp* files from
compaction they will get deleted at startup. You will then need to run
repair on that node to get back any data that was missed while it was
full.
Hi,
We have 2 nodes have been decommissioned from the cluster running 1.0.3.
However, the live nodes still making references to the decommissioned nodes
3 days after the nodes were decommissioned. Nodetool does not show the
decommissioned noes. Here are sample log entries:
INFO [GossipStage:1]
On Thu, Dec 1, 2011 at 12:26 PM, huyle wrote:
> Hi,
>
> We have 2 nodes have been decommissioned from the cluster running 1.0.3.
> However, the live nodes still making references to the decommissioned nodes
> 3 days after the nodes were decommissioned. Nodetool does not show the
> decommissioned
I know I've been spamming the list a bit with new features for Virgil, but
this one is actually really cool...
Enamored with what Riak provides as far as map/reduce via HTTP,
http://wiki.basho.com/MapReduce.html#MapReduce-via-the-HTTP-API
We implemented the same thing for Virgil/Cassandra. Simp
Hello,
Is 'garbage collecting tombstones ' a different operation than the JVM GC.
Garbage collecting tombstones is controlled by gc_grace_seconds which
by default is set to 10 days. But the traditional GC seems to happen
much more frequently (when observed through jconsole) ?
How can I force the g
The clocks are very sync'ed between the nodes as they have ntp running
hitting our time servers.
Huy
--
View this message in context:
http://cassandra-user-incubator-apache-org.3065146.n2.nabble.com/decommissioned-nodes-still-being-gossipped-tp7051526p7051701.html
Sent from the cassandra-u...@
On Thu, Dec 1, 2011 at 1:10 PM, huyle wrote:
> The clocks are very sync'ed between the nodes as they have ntp running
> hitting our time servers.
Maybe they weren't 3 days after the token left, which
https://issues.apache.org/jira/browse/CASSANDRA-2961 requires.
If a node sees the token you can
I am not sure of no disk option, but as for fast unit testing, you can try
RAM disk for storage.
Huy
--
View this message in context:
http://cassandra-user-incubator-apache-org.3065146.n2.nabble.com/is-there-a-no-disk-storage-mode-tp7051192p7051728.html
Sent from the cassandra-u...@incubator.apa
Hi Jeremiah,
My commitlog was indeed on another disk. I did what you said and yes the
node restart brings back the disk size to the around 50 GB I was expecting.
Still I do not understand how the node managed to get itself in the
situation of having these tmp files? Could you clarify what these ar
Hi Dominique,
I don't think there is a way to run cassandra without disk storage. But
running it embedded can be very useful for unit testing. I'm using
cassandra-unit (https://github.com/jsevellec/cassandra-unit) to
integrate it in my tests. You don't need to configure any file paths; it
wor
Tombstone is a marker indicating the record to be deleted.
"gc_grace_seconds" is the time after which the record will be deleted
physically from the node.
There is no ad-hoc way of gc'ing tombstones. Only after "gc_grace_seconds"
the tombstones will be gc'ed.
Thanks,
Jahangir Mohammed.
On Thu,
Yes, mostly sounds like it. In our case failed repairs were causing
accumulation of the tmp files.
Thanks,
Jahangir Mohammed.
On Thu, Dec 1, 2011 at 2:43 PM, Alexandru Dan Sicoe <
sicoe.alexan...@googlemail.com> wrote:
> Hi Jeremiah,
> My commitlog was indeed on another disk. I did what you sai
On Thu, Dec 1, 2011 at 2:45 PM, Jahangir Mohammed
wrote:
> Tombstone is a marker indicating the record to be deleted.
> "gc_grace_seconds" is the time after which the record will be deleted
> physically from the node.
> There is no ad-hoc way of gc'ing tombstones. Only after "gc_grace_seconds"
> t
> Our largest dataset has 1200 billion rows.
Radim, out of curiosity, how many nodes is that running across?
Bill
On 28/11/11 13:44, Radim Kolar wrote:
I understand that my computer may be not as powerful as those used in
the other benchmarks,
but it shouldn't be that far off (1:30), right?
+1
After upgrade to 1.0.5 also have Timeout exception on Secondary Index
search (get_indexed_slices API) .
After upgrade to 1.0.5 RangeSlice got timeout. Ticket
https://issues.apache.org/jira/browse/CASSANDRA-3551
On Dec 1, 2011, at 5:43 PM, Evgeniy Ryabitskiy wrote:
> +1
> After upgrade to 1.0.5 also have Timeout exception on Secondary Index search
> (get_indexed_slices API) .
Sorry for not checking source to see if things have changed but i just
remembered an issue I have forgotten to make jira for.
In old days, nodes would periodically try to deliver queues.
However, this was at some stage changed so it only deliver if a node is being
marked up.
However, you can d
if you're in java land there's a maven plugin -
http://mojo.codehaus.org/cassandra-maven-plugin/
On 12/1/2011 12:13 PM, Tom van den Berge wrote:
Hi Dominique,
I don't think there is a way to run cassandra without disk storage.
But running it embedded can be very useful for unit testing. I'm
Nope, that's a separate issue.
https://issues.apache.org/jira/browse/CASSANDRA-3554
On Thu, Dec 1, 2011 at 5:59 PM, Terje Marthinussen
wrote:
> Sorry for not checking source to see if things have changed but i just
> remembered an issue I have forgotten to make jira for.
>
> In old days, nodes w
Hello，everyone!
In this
doc(http://www.datastax.com/dev/blog/leveled-compaction-in-apache-cassandra),I
found a conclusion "Only enough space for 10x the sstable size needs to be
reserved for temporary use by compaction".I don't know how can we got this
conclusion,but I guess the author of this d
31 matches
Mail list logo
