Hi Vladimir,
I think that var 3. is OK. Currently `clusterStates` javadocs declares
`IgniteCheckedException` but actually throws `IgniteException`. So this is
a bug in any case, so I think we can just replace it with JMException.
I'd like to propose to use the same approach for other JMX methods
Hi, I have a similar issue for my PR [1]:
1. Github shows that the previous commit check is not completed yet. But on
Travis' side I see that it actually has already finished [2].
2. There is a new commit after the previous and Travis ignores it and
doesn't schedule a new build.
Should I add this
>> Should I add this info for the INFRA ticket?
Please do
On Fri, Feb 4, 2022 at 1:52 PM Maksim Timonin
wrote:
> Hi, I have a similar issue for my PR [1]:
>
> 1. Github shows that the previous commit check is not completed yet. But on
> Travis' side I see that it actually has already finished [2
https://issues.apache.org/jira/browse/IGNITE-16480 -- I've filed ticked.
пт, 7 янв. 2022 г. в 23:44, Valentin Kulichenko <
valentin.kuliche...@gmail.com>:
> Doesn't look like there are any objections - it's been a month since you
> started this thread. Let's create a ticket.
>
> -Val
>
>
> On Thu
Hi Pavel,
Thanks for starting this thread! Can I ask some questions here to get the
feature more clearly?
As I understand it correctly, half-state is a possible situation when an
Ignite node goes down or somehow removes connection to a thin client. But
with enabled (true by default) partitionAwar
