I think he meant "I have never seen a GC pause that long". I'm in the same boat, that's an insanely long pause.
So when I say this, keep in mind I am java guy who is pretty new to akka and scala, so this isn't expert advice. :) But tuning akka doesn't seem like the appropriate place for this. Either there is something in your application layer that requires this massive heap that could be re-evaluated or there is tuning you can do at the JVM layer that well help it handle GCs better. I'm going to guess the majority of that heap is living in swap and that's why your GCs are so long? On Monday, May 18, 2015 at 8:04:26 AM UTC-6, seetaramayya vadali wrote: > > Thanks Martynas for pointing me to heartbeat configuration property. I'll > try and get back to you. > > > @Soumya, I didn't understand your question. Based on my understanding I am > answering, if you have terribly huge (not very huge it is just 1 TB) heap > space then JVM is very tired to clean it up. > > > > On Sunday, May 17, 2015 at 3:05:57 AM UTC+2, Soumya Simanta wrote: >> >> How do you know that GC is taking 30 minutes ? I have seen a GC pause >> that long. Just curious. >> >> On Friday, May 15, 2015 at 9:51:43 AM UTC-4, seetaramayya vadali wrote: >>> >>> Hi Akka Team, >>> >>> I am not expert in akka echo system. I am facing the following >>> challenge, please advise me what to do. >>> >>> I have akka cluster with two nodes(say *node1* and *node2*). Both >>> of them seed nodes (I really don’t care who is leading). Node2 is very >>> very big machine. GC takes 30 mins (during this period machine hangs). >>> Please don’t suggest for distributed application which I know (I am working >>> in crawling environment so it takes ages to go to distributed environment). >>> >>> If I set `auto-down-unreachable-after = 1800s` in akka >>> configuration, what I understood is, there are high chances two clusters >>> will be formed in case of network partition. That means messages from node1 >>> to node2 (or vice versa) will not happen. >>> >>> What do you suggest in this scenario? >>> >>> *What is important for me is* >>> >>> · The order of node1 and node2 start up should not matter. (In >>> my application messages are guaranteed ) >>> >>> · If GC happens (30mins system hangs), after GC node2 >>> automatically be available in the cluster. >>> >>> >>> >>> I hope I explained well. Thanks a lot for your help. >>> >>> >>> >>> Regards, >>> Seeta Vadali >>> >> -- >>>>>>>>>> Read the docs: http://akka.io/docs/ >>>>>>>>>> Check the FAQ: >>>>>>>>>> http://doc.akka.io/docs/akka/current/additional/faq.html >>>>>>>>>> Search the archives: https://groups.google.com/group/akka-user --- You received this message because you are subscribed to the Google Groups "Akka User List" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/akka-user. For more options, visit https://groups.google.com/d/optout.
