Thanks Patrick...I searched in the archives and found the answer...tuning the akka and gc params....
On Fri, Apr 4, 2014 at 10:35 PM, Patrick Wendell <pwend...@gmail.com> wrote: > I answered this over on the user list... > > > On Fri, Apr 4, 2014 at 6:13 PM, Debasish Das <debasish.da...@gmail.com > >wrote: > > > Hi, > > > > Also posted it on user but then I realized it might be more involved. > > > > In my ALS runs I am noticing messages that complain about heart beats: > > > > 14/04/04 20:43:09 WARN BlockManagerMasterActor: Removing BlockManager > > BlockManagerId(17, machine1, 53419, 0) with no recent heart beats: > 48476ms > > exceeds 45000ms > > 14/04/04 20:43:09 WARN BlockManagerMasterActor: Removing BlockManager > > BlockManagerId(12, machine2, 60714, 0) with no recent heart beats: > 45328ms > > exceeds 45000ms > > 14/04/04 20:43:09 WARN BlockManagerMasterActor: Removing BlockManager > > BlockManagerId(19, machine3, 39496, 0) with no recent heart beats: > 53259ms > > exceeds 45000ms > > > > Is this some issue with the underlying jvm over which akka is run ? Can I > > increase the heartbeat somehow to get these messages resolved ? > > > > Any more insight about the possible cause for the heartbeat will be > > helpful... > > > > Thanks. > > Deb > > >
