Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Question: Issue with Remote Event listener on Cluster Nodes #11530

Open
ratadepally opened this issue Sep 12, 2024 · 2 comments
Open

Question: Issue with Remote Event listener on Cluster Nodes #11530

ratadepally opened this issue Sep 12, 2024 · 2 comments

Comments

@ratadepally
Copy link

ratadepally commented Sep 12, 2024

Hi

We are using ignite services to register Remote Events listener to listen to cache updates.

The behavior we are currently seeing with above design is when we deploy the service on one node cluster(1 Node only) the service functions as expected

but when we have more than one node in cluster and the service is deployed to one or more we are getting below ERROR

[sys-#51][GridDeploymentPerVersionStore] Failed to get resource from node [nodeId=d88e4292-49f7-408d-b410-b26f98df3335,
clsLdrId=28c72479191-d88e4292-49f7-408d-b410-b26f98df3335, resName=com/example/ignite/CacheRemoteEventService$$Lambda/0x00007f3b48717878.class,
classLoadersHierarchy=org.apache.ignite.internal.managers.deployment.GridDeploymentClassLoader->jdk.internal.loader.ClassLoaders$AppClassLoader->
jdk.internal.loader.ClassLoaders$PlatformClassLoader, msg=Requested resource not found (ignoring locally)
[originatingNodeId=f5b7438a-ebec-4d96-a55e-2e9fa1c6edb8, resourceName=com/example/ignite/CacheRemoteEventService$$Lambda/0x00007f3b48717878.class,
classLoaderId=28c72479191-d88e4292-49f7-408d-b410-b26f98df3335]]

Below is the sample configuration for Services

Service

We are converting the CacheRemoteEventService implementation into jar and uploading it to libs folder of every Ignite NODE.

Tried multiple scenarios to deploy and execute the service but all of them shows the same ERROR.

Scenarios tried which fails

  1. Uploading service library on all nodes and having service config on only one node that way service is only deployed in one node.
  2. Uploading service library on all nodes and having same service config on all available nodes that way service is deployed on each node in cluster.

Could you please suggest if we are doing something wrong with respect to the design or configuration.

@ratadepally
Copy link
Author

Hi - Any suggestions or feedback on this please?

@ptupitsyn
Copy link
Contributor

Not sure about the problem here, but a general recommendation is to use Continuous Query instead of Events to track data updates

https://ignite.apache.org/docs/latest/key-value-api/continuous-queries

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants