Hello! It is hard to say what is happening here without full stack trace from all threads of both nodes. Can you provide that?
Regards, -- Ilya Kasnacheev пн, 8 июл. 2019 г. в 13:48, Oscar Torreno <[email protected]>: > Hello Ilya, > > > > Please find attached the docker compose log of both nodes (shapelets-1 and > shapelets-2). Shapelets-2 was the one able to start without problems in > this case. Attaching the output of jstack for the main Thread of the > shapelets-1 node. > > > > Regards, > > *--* > > *Oscar Torreno* > > > > *From: *Ilya Kasnacheev <[email protected]> > *Reply-To: *"[email protected]" <[email protected]> > *Date: *Monday, 8 July 2019 at 11:25 > *To: *"[email protected]" <[email protected]> > *Subject: *Re: IGFS block at startup > > > > Hello! > > > > Can you please provide complete logs and stack traces from both nodes? > > > > I guess we have a lot of tests where we start several IGFS nodes and they > finish just fine. > > > > Regards, > > -- > > Ilya Kasnacheev > > > > > > пн, 8 июл. 2019 г. в 10:16, Oscar Torreno <[email protected]>: > > Hi, > > > > I am trying to start a fresh 2 nodes Ignite 2.7.0 cluster (using > docker-compose) with 2 IGFS configured. When I start both nodes at the same > time, almost always one of them starts without problems, but the second one > hangs at line 120 of the IgfsMetaManager class (doing an await on a > CountDownLatch). Rarely, both nodes progress, so it seems to be a kind of > race condition/inconsistent state problem because of the simultaneous start. > > > > Have you experienced such issue before? If yes, is there any workaround to > overcome it? > > > > Best regards, thanks in advance. > > Oscar > > > > [image: Logo] <https://www.shapelets.io/> > > *Oscar Torreno* > > Software Engineer > > m: + 34 675 026 952 > > e: [email protected] > > C/ Puerta del Mar 18, 2º. 29005, Málaga,Spain > > [image: LinkedIn icon] <https://www.linkedin.com/company/shapelets/> [image: > Twitter icon] <https://twitter.com/shapelets> > > > >
