I tried with 2.8.1, same issue. Operations block indefinitely... 1- Start 3 node cluster 2- Start client application client = true with Ignition.start() 3- Run some cache operations, everything ok... 4- Shut down one node, run operation, still ok 5- Shut down 2nd node, run operation, still ok 6- Shut down 3rd node, run operation, still ok... Operations start failing with ClientDisconectedException... 7- Restart 1st node, run operation, operation fails with ClientDisconectedException but application still able to complete it's request. 8- Start 2nd node, run operation, from here on all operations just block.
Basically the client application is an HTTP Server on each HTTP request does cache exception. On Fri, 7 Aug 2020 at 19:46, John Smith <[email protected]> wrote: > No, everything blocks... Also using 2.7.0 just in case. > > Only time I get exception is if the cluster is completely off, then I get > ClientDisconectedException... > > On Fri, 7 Aug 2020 at 18:52, Denis Magda <[email protected]> wrote: > >> 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 <[email protected]> wrote: >> >>> Hi any thoughts on this? >>> >>> On Thu, 6 Aug 2020 at 23:33, John Smith <[email protected]> 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 <[email protected]> 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. >>>>> >>>>> >>>>>
