Hello! Ignite operations will use built-in locks even if you don't explicitly use any. If you have uncommitted transactions or something like that, checkpoint can't start (and other operations are waiting for it too).
How big are we talking about? I recommend capturing several thread dumps after (or, even better, before) getting this message. Regards, -- Ilya Kasnacheev пт, 18 окт. 2019 г. в 19:20, ihalilaltun <ibrahim.al...@segmentify.com>: > Hi Ilya, > > Sorry for the late response. We don't use lock mechanism in our > environment. > We have a lot of put, get operaitons, as far as i remember these operations > does not hold the locks. In addition to these operations, in many > update/put > operations we use CacheEntryProcessor which also does not hold the locks. > > My guess would be this; sometimes we put big objects to cache. I know using > big objects causes this kind of problems but can you confirm this also? > > Regards. > > > > ----- > İbrahim Halil Altun > Senior Software Engineer @ Segmentify > -- > Sent from: http://apache-ignite-users.70518.x6.nabble.com/ >
