Hi all! I'm new to Ignite.
Hi!
I agree that users shouldn't expect a non-proxy when invoking the
`IgniteServices#serviceProxy()` method. I think it's up to Ignite to return
a non-proxy instance here as possible optimisation. But users have to use
interfaces in any case. There is the `IgniteServices#service()` method for
Hi, Igniters.
I'd like to suggest modifying `/IgniteServices.serviceProxy(String name,
Class svcItf, boolean sticky)/` so that it may return proxy
even for local service. Motivation: service metrics [1]. To measure
method call we need to wrap service somehow. Also, the method name says
Thanks everybody for the opinions. Looks like we all agree on option 2, but
nevertheless I'll organize a formal vote after the New Year holidays.
On Wed, Dec 22, 2021 at 9:18 AM Ivan Pavlukhin wrote:
> Val,
>
> > Basically, what I'm suggesting is to accept non-nullable as default
>
> Sounds
Any inputs on this?
On Thu, 23 Dec, 2021, 17:31 Vishwas Bm, wrote:
> Hi,
>
> In the javadocs I see that the value of getCurrentCpuLoad is in the range
> [0,1]
>
>
Hello!
OK, I'm retracting my claim then. IP-finder may indeed be moved to
extensions.
Regards,
--
Ilya Kasnacheev
ср, 22 дек. 2021 г. в 14:00, Ivan Daschinsky :
> >> a lot of code in core code base is dedicated for enabling it.
> It is simply not true. ZookeeperDiscovery has nothing common
