If I'm not mistaken, key-value operations (cache.get/put) and compute calls fail with an exception if the cluster is deactivated. Do those fail on your end?
As for the async and SQL operations, let's see what other community members say. - Denis On Fri, Aug 7, 2020 at 1:06 PM John Smith <java.dev....@gmail.com> wrote: > Hi any thoughts on this? > > On Thu, 6 Aug 2020 at 23:33, John Smith <java.dev....@gmail.com> wrote: > >> Here is another example where it blocks. >> >> SqlFieldsQuery query = new SqlFieldsQuery( >> "select * from my_table") >> .setArgs(providerId, carrierCode); >> query.setTimeout(1000, TimeUnit.MILLISECONDS); >> >> try (QueryCursor<List<?>> cursor = cache.query(query)) >> >> cache.query just blocks even with the timeout set. >> >> Is there a way to timeout and at least have the application continue and >> respond with an appropriate message? >> >> >> >> On Thu, 6 Aug 2020 at 23:06, John Smith <java.dev....@gmail.com> wrote: >> >>> Hi running 2.7.0 >>> >>> When I reboot a node and it begins to rejoin the cluster or the cluster >>> is not yet activated with baseline topology operations seem to block >>> forever, operations that are supposed to return IgniteFuture. I.e: >>> putAsync, getAsync etc... They just block, until the cluster resolves it's >>> state. >>> >>> >>>
