On Mon, Mar 24, 2014 at 9:41 AM, Batranut Bogdan wrote:
> I am reposting a question about missing files on one of the nodes of my
> cluster.
> After I first saw that I was missing a ...-Data.db file, I decomissioned
> the node, deleted the data and added it back into the cluster. Now I see
> agai
On Mon, Mar 24, 2014 at 4:11 AM, prem yadav wrote:
> the nodes die *without * being under any load. Completely idle.
>
https://issues.apache.org/jira/browse/CASSANDRA-6541
?
=Rob
fyi.
On Mon, Mar 24, 2014 at 11:56 PM, Vivek Mishra
wrote:
> Hi All,
>
>
>
> We are happy to announce the Kundera 2.11 release.
>
>
>
> Kundera is a JPA 2.0 compliant, object-datastore mapping library for NoSQL
> datastores. The idea behind Kundera is to make working with NoSQL databases
> drop
Hello all,
I am reposting a question about missing files on one of the nodes of my cluster.
After I first saw that I was missing a ...-Data.db file, I decomissioned the
node, deleted the data and added it back into the cluster. Now I see again that
I am missing some files.
Do you have an ideea
The problem was one of my nodes was in some kind of bad Hinted-Handoff
loop. I looked at CASSANDRA-4740 which discusses this but to no solution
that I could see.
When I killed the server trying to do the hinted-handoffs the other nodes
stopped complaining...as soon as I restarted the node all the
I'm getting "messages dropped" messages in my cluster even when (like right
now) there are no clients running against the cluster.
1) who could be generating the traffic if there are no clients?
2) is there a way to list active clients...on the off chance that there is
a client I don't know about?
*@Jonathan Lacefield, *
Yes I am seeing the logs in system.log. I installed cassandra 2.0.6 using
latest Datastax Community package on Ubuntu 12.04. Its is packaged
installation.
I run cassandra using "sudo service cassandra start".
New Logs are written to /var/logs/cassandra/system.log but not to
Hi user 01, in older versions of the datastax Debian packages startup
information was written to output.log but that is no longer the case (and hasn't
been for a while): it is normal that you have no output.log.
Ciao, Duncan.
On 24/03/14 13:26, user 01 wrote:
Hints please, anyone ?
On Mon,
Hello,
Here are a few questions to help guide your troubleshooting efforts:
Do you have a cassandra system log file?
Did you use a packaged or binary installation?
What user are you using to start Cassandra?
Does the user have permissions to the log directory?
Hope that helps.
Hints please, anyone ?
On Mon, Mar 24, 2014 at 2:13 AM, user 01 wrote:
> No output.log is ever generated by my cassandra installation(DSC20 with C*
> 2.0.6 on Ubuntu 12.04). Do I need to configure anything to enable logs to
> output.log ?
>
4 GB is OK for a test cluster.
In the past we encountered a similar issue due to VMWare ESX's memory
overcommit (memory ballooning).
When you talk about overcommit, you talk about Linux (vm.overcommit_*) or
hypervisor (like ESX)?
prem yadav a écrit sur 24/03/2014 12:11:31 :
> De : prem yada
the nodes die *without * being under any load. Completely idle.
And 4 GB system memory is not low. or is it?
I have tried tweaking the overcommit memory. Tried disabling it,
under-committing and over-committing.
I also reduced rpc threads min and max. Will try other setting from that
link Michael
You have to tune Cassandra in order to run it under a low memory
environment.
Many settings must be tuned. The link that Michael mentions provides a
quick start.
There is a point that I haven't understood. *When* did your nodes die?
Under load? Or can they be killed via OOM killer even if they
If you just want to play with Cassandra then it's OK.
But for production, Cassandra needs some kernel tuning.
user 01 a écrit sur 23/03/2014 21:52:52 :
> De : user 01
> A : user@cassandra.apache.org,
> Date : 23/03/2014 21:53
> Objet : Can't modify 'vm.swapiness' or 'vm.max_map_count' for C
14 matches
Mail list logo
