Hi, Thank you for digging deeper! No good ideas about problems in curCrd.local().
Have you tried to reproduce a leak with starting/stopping huge amount of client nodes? вс, 17 нояб. 2019 г. в 13:16, mvkarp <[email protected]>: > > Only other thing I can think of if it's through onDiscovery() is that > curCrd.local() somehow is returning true. However I am unable to find > exactly how local() is determined since there appears to be a big chain. > > I know that the node uuid on the leaking server is on a different physical > node as well as has a completely different node ID > (bbbbb-bbbbb-bbbbb-bbbbb-bbbbb-bbbbb) to what the MVCC coordinator is > (mvccCrd=aaaaa-aaaa-aaaaa-aaaaa-aaaaa) > > Is there any way that the curCrd.local() could be returning True on the > leaking server JVM? I am trying to investigate how local() is determined and > what could cause it to be true. > > > Ivan Pavlukhin wrote > > But currently I suspect that you faced a leak in > > MvccProcessorImpl.onDiscovery on non MVCC coordinator nodes. Do you > > think that there is other reason in you case? > > > > > > -- > Sent from: http://apache-ignite-users.70518.x6.nabble.com/ -- Best regards, Ivan Pavlukhin
