RE: Can't modify 'vm.swapiness' or 'vm.max_map_count' for Cassandra
If you just want to play with Cassandra then it's OK. But for production, Cassandra needs some kernel tuning. user 01 user...@gmail.com a écrit sur 23/03/2014 21:52:52 : De : user 01 user...@gmail.com A : user@cassandra.apache.org, Date : 23/03/2014 21:53 Objet : Can't modify 'vm.swapiness' or 'vm.max_map_count' for Cassandra While installing Datastax community Cassandra I got the error: error: permission denied on key 'vm.max_map_count' Because I 'm running cassandra in an OpenVZ container my host does not allow changing vm.swapiness or vm.max_map_count due to shared kernel. Is it OK to ignore these errors ?
Re: Kernel keeps killing cassandra process - OOM
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 are not loaded? If the nodes are VM you have to pay attention to hypervisor memory overcommit. Laing, Michael michael.la...@nytimes.com a écrit sur 22/03/2014 22:25:30 : De : Laing, Michael michael.la...@nytimes.com A : user@cassandra.apache.org, Date : 22/03/2014 22:26 Objet : Re: Kernel keeps killing cassandra process - OOM You might want to look at: http://www.opensourceconnections.com/2013/08/31/building-the- perfect-cassandra-test-environment/
Re: Kernel keeps killing cassandra process - OOM
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 has given. On Mon, Mar 24, 2014 at 10:26 AM, Romain HARDOUIN romain.hardo...@urssaf.fr wrote: 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 are not loaded? If the nodes are VM you have to pay attention to hypervisor memory overcommit. Laing, Michael michael.la...@nytimes.com a écrit sur 22/03/2014 22:25:30 : De : Laing, Michael michael.la...@nytimes.com A : user@cassandra.apache.org, Date : 22/03/2014 22:26 Objet : Re: Kernel keeps killing cassandra process - OOM You might want to look at: http://www.opensourceconnections.com/2013/08/31/building-the- perfect-cassandra-test-environment/
Re: Kernel keeps killing cassandra process - OOM
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 ipremya...@gmail.com a écrit sur 24/03/2014 12:11:31 : De : prem yadav ipremya...@gmail.com A : user@cassandra.apache.org, Date : 24/03/2014 12:12 Objet : Re: Kernel keeps killing cassandra process - OOM 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 has given.
Re: No output.log is ever generated
Hints please, anyone ? On Mon, Mar 24, 2014 at 2:13 AM, user 01 user...@gmail.com 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 ?
Re: No output.log is ever generated
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. Jonathan Jonathan Lacefield Solutions Architect, DataStax (404) 822 3487 http://www.linkedin.com/in/jlacefield http://www.datastax.com/what-we-offer/products-services/training/virtual-training On Mon, Mar 24, 2014 at 8:26 AM, user 01 user...@gmail.com wrote: Hints please, anyone ? On Mon, Mar 24, 2014 at 2:13 AM, user 01 user...@gmail.com 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 ?
Re: No output.log is ever generated
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, Mar 24, 2014 at 2:13 AM, user 01 user...@gmail.com mailto:user...@gmail.com 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 ?
Re: No output.log is ever generated
*@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 output.log. Infact ouput.log is not even generated. Permissions are Ok, verified that cassandra is owner also there are Ok since system.log is getting written. *@Duncan Sands,* Ok in that case , wont output.log be generated anytime now ? Besides startup information what all was output.log supposed to contain? Is it completely a deprecated now ? I am surprised why does this page exists : http://www.datastax.com/documentation/cassandra/2.0/cassandra/configuration/configOutputLog_t.html On Mon, Mar 24, 2014 at 6:27 PM, Duncan Sands duncan.sa...@gmail.comwrote: 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, Mar 24, 2014 at 2:13 AM, user 01 user...@gmail.com mailto:user...@gmail.com 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 ?
getting dropped messages in log even with no one running
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? 3) why is messages dropped an INFO rather than a WARNING? I'm running 1.2.13 on a six node AWS cluster on m2-2xlarge servers. Any help is appreciated. Brian
Re: getting dropped messages in log even with no one running
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 other nodes went right back into the dropping messages state. Help please. Brian On Mon, Mar 24, 2014 at 10:01 AM, Brian Tarbox tar...@cabotresearch.comwrote: 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? 3) why is messages dropped an INFO rather than a WARNING? I'm running 1.2.13 on a six node AWS cluster on m2-2xlarge servers. Any help is appreciated. Brian
FileNotFoundException ...-Data.db
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 on how to fix this?
Re: {kundera-discuss} Kundera 2.11 released
fyi. On Mon, Mar 24, 2014 at 11:56 PM, Vivek Mishra vivek.mis...@impetus.co.inwrote: 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-dead simple and fun. It currently supports Cassandra, HBase, MongoDB, Redis, OracleNoSQL, Neo4j,ElasticSearch,CouchDB and relational databases. Major Changes: == 1) Support added for Cassandra datastax java driver. 2) Support added for in clause with setParameter on collection object. Github Bug Fixes = https://github.com/impetus-opensource/Kundera/issues/542 https://github.com/impetus-opensource/Kundera/issues/538 https://github.com/impetus-opensource/Kundera/issues/537 https://github.com/impetus-opensource/Kundera/issues/536 https://github.com/impetus-opensource/Kundera/issues/530 https://github.com/impetus-opensource/Kundera/issues/520 https://github.com/impetus-opensource/Kundera/issues/519 https://github.com/impetus-opensource/Kundera/issues/512 https://github.com/impetus-opensource/Kundera/issues/510 https://github.com/impetus-opensource/Kundera/issues/506 https://github.com/impetus-opensource/Kundera/issues/501 https://github.com/impetus-opensource/Kundera/issues/500 https://github.com/impetus-opensource/Kundera/issues/496 https://github.com/impetus-opensource/Kundera/issues/483 https://github.com/impetus-opensource/Kundera/issues/482 https://github.com/impetus-opensource/Kundera/issues/385 https://github.com/impetus-opensource/Kundera/issues/226 https://github.com/impetus-opensource/Kundera/issues/151 How to Download: To download, use or contribute to Kundera, visit: http://github.com/impetus-opensource/Kundera Latest released tag version is 2.11 Kundera maven libraries are now available at: https://oss.sonatype.org/content/repositories/releases/com/impetus Sample codes and examples for using Kundera can be found here: https://github.com/impetus-opensource/Kundera/tree/trunk/src/kundera-tests Survey/Feedback: http://www.surveymonkey.com/s/BMB9PWG Thank you all for your contributions and using Kundera! *PS: Group artifact Id has been changed with 2.9.1 release onward. Please refer https://github.com/impetus-opensource/Kundera/blob/trunk/src/README.md#note https://github.com/impetus-opensource/Kundera/blob/trunk/src/README.md#note for the same.* Regards, Kundera Team -- NOTE: This message may contain information that is confidential, proprietary, privileged or otherwise protected by law. The message is intended solely for the named addressee. If received in error, please destroy and notify the sender. Any use of this email is prohibited when received in error. Impetus does not represent, warrant and/or guarantee, that the integrity of this communication has been maintained nor that the communication is free of errors, virus, interception or interference. -- You received this message because you are subscribed to the Google Groups kundera-discuss group. To unsubscribe from this group and stop receiving emails from it, send an email to kundera-discuss+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
Re: Kernel keeps killing cassandra process - OOM
On Mon, Mar 24, 2014 at 4:11 AM, prem yadav ipremya...@gmail.com wrote: the nodes die *without * being under any load. Completely idle. https://issues.apache.org/jira/browse/CASSANDRA-6541 ? =Rob
Re: FileNotFoundException ...-Data.db
On Mon, Mar 24, 2014 at 9:41 AM, Batranut Bogdan batra...@yahoo.com 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 again that I am missing some files. Do you have an ideea on how to fix this? What version of Cassandra? How are you stop and starting cassandra? =Rob
