I posted a PR + Jira ticket with the update:
https://github.com/apache/ignite/pull/10123
The PR checks are still running/pending. Any feedback/help is appreciated.
Art
On Tue, Jun 28, 2022 at 10:53 PM Pavel Tupitsyn
wrote:
> Thank you for tracking this down! An additional map by name is a g
Thank you for tracking this down! An additional map by name is a good idea
there.
> CONCURRENCY NOTE: these two maps need to update concurrently
All updates are triggered by discovery events, which are raised under
"synchronized (discoEvtMux)" in GridDiscoveryManager,
so it is safe to update two m
The following is taking most of the time:
@Nullable private ServiceInfo lookupInRegisteredServices(String name) {
for (ServiceInfo desc : registeredServices.values()) {
if (desc.name().equals(name))
return desc;
}
return null;
}
After changing that to use a Map l
Yes. The "services" in our case will be schedules that periodically
perform fast operations.
For example a service could be, "ping this device every seconds".
Art
On Tue, Jun 28, 2022 at 12:20 PM Pavel Tupitsyn
wrote:
> > we do not plan to make cross-cluster calls into the services
>
> If yo
> we do not plan to make cross-cluster calls into the services
If you are making local calls, I think there is no point in using Ignite
services.
Can you describe the use case - what are you trying to achieve?
On Tue, Jun 28, 2022 at 8:55 PM Arthur Naseef wrote:
> Hello - I'm getting started wi
Hello - I'm getting started with Ignite and looking seriously at using it
for a specific use-case.
Working on a Proof-Of-Concept (POC), I am finding a question related to
performance, and wondering if the solution, using Ignite Services, is a
good fit for the use-case.
In my testing, I am getting
