I'm testing streaming input data and call a service deployed. Two things happened quite confusing and could someone in the community help?
1. I print a '.' in StreamVisitor.from method to show it's running, and call service via proxy. It actually ran for over 17K but then stopped/stuck. The file I used to stream data in has over 1M records in it.
2. I also print a '.' in the service method to show it's being called. It only printed couple dots and seemed to stuck as well.
First I thought, the message queue was too small, but increasing it to 10240 didn't change the behavior. <property name="messageQueueLimit" value="10240"/>
What shall I do next to see where it might have got stuck?
Btw, the memory policy looks like this
<bean class="org.apache.ignite.configuration.MemoryPolicyConfiguration"> <property name="name" value="customRegion"/>
I noticed that when I try to create a atomic sequence in service init method, it hangs. Is there any reason that atomicSequence cannot be used in service.init? If not, what'd be the alternative? AffinityUUID?
"guid", // Sequence name.
start, // Initial value for sequence.
true // Create if it does not exist.
Hello there, please my test project. You can see 1) The initialization seem didn't finish 2) the streaming client stopped after a while.
If you take out the Atomic sequence part, the stream start to work.
Thank you for helping.
Unfortunately I don't have an existing AtomicLong or AtomicSequence to work with... What if I need to initiate one, where shall I initiate it? We have a small cluster, sometime I only have one node for dev/test. It's a bit surprising why initiate an AtomicSequence would need to wait so long, because there's no other node to wait for...
I now put the stream visitor code in a different model and packaged it in a different jar with dependencies.
Interestingly, when I ran the program again, the server node has weird error messages.
The FileConnector is a class in the client jar. Why would the service needs the caller's signature?
Btw, I turned enablePeerClassLoader on, but I still have the same error.
Caused by: java.lang.ClassNotFoundException: com.sample.client.FileConnector
at java.net.URLClassLoader.findClass(URLClassLoader.java:381) ~[?:1.8.0_
at java.lang.ClassLoader.loadClass(ClassLoader.java:424) ~[?:1.8.0_91]
at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:331) ~[?:1.8
at java.lang.ClassLoader.loadClass(ClassLoader.java:357) ~[?:1.8.0_91]
at java.lang.Class.forName0(Native Method) ~[?:1.8.0_91]
at java.lang.Class.forName(Class.java:348) ~[?:1.8.0_91]