7;t seem to apply here)
* Using other certificates
* Running Cassandra outside of Intellij (starting the /bin/cassandra script)
Any help is really appreciated. Thanks!
BR,
Fredrik
Hi
Does anyone know what Cassandra uses WMI for when running on Windows? We have
some issues with high WMI CPU usage..
Yours sincerely / Med venlig hilsen
Fredrik Løkke (FRSKL)
Backend Architect, Application Development
Plant Application (PA)
Technology & Service Solutions (TSS)
Ve
Hi all.
Having two FSReadErrors:
FSReadError in
..\..\data\system\compaction_history-b4dbb7b4dc493fb5b3bfce6e434832ca\system-compaction_history-ka-329-CompressionInfo.db
FSReadError in
..\..\data\system\sstable_activity-5a1ff267ace03f128563cfae6103c65e\system-sstable_activity-ka-475-CompressionI
Thanks for the advice.
/Fredrik
> 7 mar 2015 kl. 02:25 skrev graham sanderson :
>
> Note for anyone who accidentally or otherwise ends up with 2.1.3 in a
> situation they cannot downgrade, feel free to look at
>
> https://github.com/vast-engineering/cassandra/tree/va
So no upgradeSSTables are required?
/Fredrik
> 6 mar 2015 kl. 15:11 skrev Carlos Rolo :
>
> I would not recommend an upgrade to 2.1.x for now. Do you have any specific
> reason to upgrade?
>
> For upgrading from 2.0.9 you can just do a direct upgrade.
>
> Regards,
ssible to just start the on 2.1.3 directly after 2.0.9.
Regards
Fredrik
ix similar problems e.g.
https://issues.apache.org/jira/browse/CASSANDRA-6283
<https://issues.apache.org/jira/browse/CASSANDRA-6283>
Are there any outstanding issues in 2.1.3 which specifically pinpoints manually
clearing snapshots on Windows?
Regards
Fredrik
1.0 is compatible with
1.0.5. But might there be problems/data incompatibility in the future when
upgrading Cassandra to a never version regarding *CompressionInfo.db files
etc..?
/Fredrik
Are there any official recomendations, validations/tests done with
Cassandra >= 2.0 on Java 8?
Regards
/Fredrik
ap is
>> kinda old school anyway at this point. It made sense when machines had 32MB
>> RAM.
>>
>> Keeping your read 95th percentile low is mostly about removing deviations
>> that cause requests to slow down, swap is one of the things that cause
>> fluctuati
at's swaped out?
Regards
/Fredrik
I don't have a current use-case. I was just curious how applications
handle and how to think when modelling, since I guess denormalization
might increase the complexity of the application.
Fredrik
2013/1/27 Hiller, Dean :
> There is a really a mix of denormalization and normalization. I
updating those user data properties
which might be spread out over many cf:s and many rows?
Regards
/Fredrik
I guess that the other nodes still gossips about the removed node. The
node isn't removed from gossiper in the cluster until some amount of
time have elapsed. My guess is that you haven't changed the cluster_name
property in the cassandra.yaml on the removed node.
Xu, Zaili skrev 2012-09-28
and thus be applied to the backuped data.
What is the recomended way to handle this situation? Removing the hints
cf from the system tables before restart of the cluster nodes?
Regards
/Fredrik
Wrong assumption of me. I found the answer in
GossipDigestSynVerbHandler. I forgot to change the cluster name of the
new cluster.
/Fredrik
2012/9/11 Fredrik :
> I've tested a scenario where I wanted to reuse a removed node in a new
> cluster with same IP, maybe not very common but an
a node out of
the cluster you must change IP on the removed node if you want to use it
in another cluster?
Please enlight me.
Regards
/Fredrik
apsed, will it be possible to run a
major compaction since there are only deletes which doesn't require
double amount of SStable size when merging tombstones with the large
SSTables?
Regards
/Fredrik
xtensive memory
requirements.
I'd be happy if someone could shed some light on this issue.
Regards
/Fredrik
ipv6 addresses with NIO
on Windows with Java < jdk7,
(https://issues.apache.org/jira/browse/CASSANDRA-4359) which isn't a
Cassandra issue anyway.
Regards
/Fredrik
nce Developer
> @aaronmorton
> http://www.thelastpickle.com
>
> On 26/04/2012, at 9:37 PM, Fredrik wrote:
>
> Exactly, but why would reads be significantly slower over time when
> including just one more, although sometimes large, SSTable in the read?
>
> Ji Cheng skrev
date workload itself may
result in reading multiple sstables for a single row key.
Please correct me if I am wrong.
Cheng
On Thu, Apr 26, 2012 at 3:50 PM, Fredrik
<mailto:fredrik.l.stigb...@sitevision.se>> wrote:
In the tuning documentation regarding Cassandra, it'
uot;.
From the doc:
"So while read performance will be good immediately following a major
compaction, it will continually degrade until the next major compaction
is manually invoked. For this reason, major compaction is NOT
recommended by DataStax."
Regards
/Fredrik
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 cassa
try
{
..
}
finally
{
*queuedDeliveries.remove(endpoint);*
}
}
Regards
/Fredrik
ble for deletion but would this be problem if we have
seldom updated column family that wont be compacted very often?
Is this considered a bug or is it something that won't be fixed due to
the way Windows handles hard links?
Regards
/Fredrik
CommitLog.java (line
497) Not safe to delete commit log
CommitLogSegment(/var/lib/cassandra/commitlog/CommitLog-1320176934665.log);
dirty is ; hasNext: false
Could someone please clarify the relationship between commit log
creation, removal/rotation and flush, drain.
Regards
/Fredrik
ation factor == no nodes in cluster.
Regards
/Fredrik
Thanks.
Will upgrade to 0.8.5.
Regards
/Fredrik
2011/9/13 Sylvain Lebresne
> This should be fixed in 0.8.5 (more precisely by
> https://issues.apache.org/jira/browse/CASSANDRA-3039)
>
> --
> Sylvain
>
> On Tue, Sep 13, 2011 at 12:53 PM, Fredrik Stigbäck
> wrote:
>
at java.util.concurrent.FutureTask.run(FutureTask.java:138)
at
java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886)
at
java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908)
at java.lang.Thread.run(Thread.java:662)
/Regards Fredrik
Does reading quorum mean only waiting for quorum respones or does it mean
quorum respones with same latest timestamp?
Regards
/Fredrik
31 matches
Mail list logo
