scratch or can I include parts of the Apache Cassandra
documentation in my manual ?
Mikael
-
To unsubscribe, e-mail: user-unsubscr...@cassandra.apache.org
For additional commands, e-mail: user-h...@cassandra.apache.org
Hi I'm having a problem after upgrading Cassandra 3.0.14 to 3.11.1.
When running a repair the node I'm issuing the repair starts to use use all
available memory and then the GC grinds it to death. I'm seeing with
nodetool compactionstats that there is a lot of (> 100) active concurrent
compaction
embedded and are working directly against the internal APIs).
Regards
Mikael Wikblom
On 05/02/2012 03:03 PM, Sylvain Lebresne wrote:
On Wed, May 2, 2012 at 2:42 PM, Mikael Wikblom
wrote:
Given an IOException in writeSortedContents the latch.countDown() will not
be called. Wouldn't it be b
d hangs in
ColumnFamilyStore.forceBlockingFlush waiting for future.get() because
the latch.await() in ColumnFamilyStore.maybeSwitchMemtable never completes.
Regards
--
Mikael Wikblom
Software Architect
SiteVision AB
019-217058
mikael.wikb...@sitevision.se
http://www.sitevision.se
@aaronmorton
http://www.thelastpickle.com
On 16/03/2012, at 8:56 PM, Mikael Wikblom wrote:
ok, thank you both for the clarification. So the correct approach
would be to bootstrap the new node and run repair on each of the
nodes in the cluster.
I'm a bit puzzled though, I just tried to in
ciiribbon.org> - against
proprietary attachments
--
Mikael Wikblom
Software Architect
SiteVision AB
019-217058
mikael.wikb...@sitevision.se
http://www.sitevision.se
. Every node is now a replica for every key.
5. Roll back the CL change.
6. Repair the new node.
7. Turn on the clients for the new node.
Hope that helps.
-
Aaron Morton
Freelance Developer
@aaronmorton
http://www.thelastpickle.com
On 15/03/2012, at 9:50 PM, Mikael Wikblom wrote:
eated
after the bootstrap process finishes?
scenario:
1. a running cluster of N=3, R=3
2. upgrade R to 4
3. bootstrap the new node
I would like to avoid having to do the required repair on each node if I
upgrade R to 4 after bootstrapping the new node.
Thanks
Regards
--
Mikael Wikblom
Sof
salt. Just my knee-jerk reaction from what I've read so far.
Yes. Maybe it is time to investigate the possibilities to change the
store / retrieval patterns of our framework to match cassandra instead
of the other way around :)
Thanks again for your time
Kind regards
--
Mikael Wik
the nodes in the cluster are wide apart
(e.g. different DC:s), for the writes to be a significant problem for
latency?
No gigabit network between the nodes, same net etc.
Kind regards
--
Mikael Wikblom
Software Architect
SiteVision AB
019-217058
mikael.wikb...@sitevision.se
http://www.sitevision.se
e that the local node has returned before sending the condition
signal. Can anyone see any drawbacks with this approach? I realize this
will only work as long as the replication factor is the same as the
number of nodes, but that is ok for our scenario.
Kind regards
--
Mikael Wikblom
Softwar
fix for the file name issue would be quite simple.
Thanks and regards
Mikael Wikblom
Hi,
is there a maven repository where I can download the latest version of
cassandra? I've found a few versions at riptano
http://mvn.riptano.com/content/repositories/riptano/org/apache/cassandra/apache-cassandra/
but note the latest 0.7.4
regards
Mikael Wikblom
--
Mikael Wikblom
Sof
rt up. It starts up again after I've manually deleted the commit log
files.
I have failed to reproduce the problem with a non empty byte array.
I'm using cassandra 0.7
Is there a way to recover from such errors without loosing the entries
in the commit log?
Regards
Mikael Wikblom
14 matches
Mail list logo
