Hi Ilya, I think you are missing the point. It is a chicken-and-egg problem.
I need to start Ignite so that I can do various things – like use some various “admin caches” to look up things, etc – BEFORE I can accept real load. But the way it stands today, Ignite _assumes_ that if it is started, then it must also be ready to participate in the ComputeGrid. That may be true for some, or even most, use cases, but it will NOT be true for all. These are separate lifecycle events. In my case, Ignite starts slamming the Node with load before it is fully initialized and ready for real load. Thus, I’ve had to reject all ComputeJobs in my implementation (in ComputeJob::execute()), and force them to be retried in ComputeTask:::result() (returning FAILOVER). This works, of course. But is pretty silly. And hurts performance badly during the transition period. What is needed is a simple gate. E.g “acceptComputeJobs” It could default to “true” at start-up. But, for those that need finer control of that lifecycle, it could allow you to start-up with acceptComputeJobs=false And, then flip it to true manually, when the Node is ready to participate. Make sense?? Thanks, -- Chris -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/
