Sasha, as far as exception we need to add checks and throw appropriate
exception on configuration validation step. Can you please file a ticket
and also point all the places known so far? I guess we already have lower
bound check. Let's add upper.
As far as long vs int - in Ignite each
Now in ignite configurations in many network related parameters (for
example: IgniteConfiguration.netTimeout, TcpDiscoverySpi.socketTimeout,
TcpDiscoverySpi.ackTimeout) used long. But network socket using int for
socket timeout, so we do simple "(int)timeout" type casting and if timeout
value >
