May not be related to this, but for me precheckin took ~22 hrs to finish. Thanks Avinash
On Fri, Feb 16, 2018 at 3:14 AM, Bruce Schuchardt <bschucha...@pivotal.io> wrote: > If it happens again send comms a full log and maybe we can diagnose the > problem. I haven't had this happen on my mac. > > > > On 2/15/18 1:35 PM, Kirk Lund wrote: > >> I'm intermittently seeing dunit tests hang (actually fails after timing >> out) at this point in joining a cluster: >> >> [locator] [info 2018/02/15 12:56:25.583 PST <locator request thread[1]> >> tid=71] This member is becoming coordinator >> >> [vm0] [info 2018/02/15 12:56:25.584 PST <RMI TCP >> Connection(1)-10.118.20.39> tid=20] Probable coordinator is still >> 10.118.33.216(17575:locator)<ec><v0>:32769 - waiting for a join-response >> >> This is when running any dunit test that has a cluster in IntelliJ on my >> Mac. >> >> It's like the code just intermittently gets stuck in the join-response for >> coordinator. >> >> Any ideas if this is specific to Mac or something? I don't see this >> happing >> in precheckin on Linux. >> >> >
