Re: Service not found for a deployed service
Hi!
> I deployed a service from a client node to our grid using the following code:
> IgniteCluster cluster = ignite.cluster();
> ClusterGroup group = cluster.forAttribute(…);
> Ignite.services(workerGroup).deployClusterSingleton(“blaze/hsbc”)
Calvin, please, pay attention to your code and make sure that you
define ClusterGroup in right way.
I think the problem may be in the empty cluster group, that means
Ignite can't define suitable nodes to deploy service.
On Fri, Sep 14, 2018 at 5:51 PM Denis Mekhanikov wrote:
>
> Did you manage to reproduce the problem?
>
> Denis
>
> пн, 6 авг. 2018 г. в 14:39, Calvin KL Wong, CLSA :
>>
>> Hi Denis,
>>
>>
>>
>> >> Did Service#init() method throw any exceptions?
>>
>> No, we didn’t see any exception.
>>
>>
>>
>> I will get a stack trace if I can reproduce it.
>>
>>
>>
>> Thanks,
>>
>> Calvin
>>
>>
>>
>> From: Denis Mekhanikov [mailto:dmekhani...@gmail.com]
>> Sent: Friday, August 03, 2018 8:08 PM
>>
>>
>> To: user@ignite.apache.org
>> Subject: Re: Service not found for a deployed service
>>
>>
>>
>> Calvin,
>>
>>
>>
>> Did Service#init() method throw any exceptions?
>>
>> If so, then you would see the same problem.
>>
>>
>>
>> Denis
>>
>>
>>
>> пт, 3 авг. 2018 г. в 14:13, Calvin KL Wong, CLSA :
>>
>> Actually, we deployed the service at 02:00, and didn’t use the service until
>> 16:27 the next day. Then got the error. There were more than 12 hours in
>> between.
>>
>> Does this still seem related to IGNITE-1478 ?
>>
>> If not, can you think of other possible reason?
>>
>>
>>
>> Thanks,
>>
>> Calvin
>>
>>
>>
>> From: Denis Mekhanikov [mailto:dmekhani...@gmail.com]
>> Sent: Thursday, August 02, 2018 11:45 PM
>> To: user@ignite.apache.org
>> Subject: Re: Service not found for a deployed service
>>
>>
>>
>> Calvin,
>>
>>
>>
>> You have this problem due to the following issue: IGNITE-1478
>>
>> A workaround here would be to retry method execution with some delay.
>>
>>
>>
>> This problem should be fixed under IEP-17, which is in progress right now.
>>
>>
>>
>> Denis
>>
>>
>>
>> чт, 2 авг. 2018 г. в 14:33, Calvin KL Wong, CLSA :
>>
>> Hi,
>>
>>
>>
>> I deployed a service from a client node to our grid using the following code:
>>
>>
>>
>> IgniteCluster cluster = ignite.cluster();
>>
>> ClusterGroup group = cluster.forAttribute(…);
>>
>> Ignite.services(workerGroup).deployClusterSingleton(“blaze/hsbc”)
>>
>>
>>
>> It is fine most of the time. However we just encountered a case where we
>> got an exception when some logic tried to use this service:
>>
>>
>>
>> 2018-08-02 16:27:57.713 processors.task.GridTaskWorker [sys-#29%mlog%] ERROR
>> - Failed to obtain remote job result policy for result from
>> ComputeTask.result(..) method (will fail the whole task): GridJobResultImpl
>> [job=C2 [c=ServiceProxyCallable [mtdName=execute, svcName=blaze/hsbc,
>> ignite=null]], sib=GridJobSiblingImpl
>> [sesId=f66f54be461-65c907a3-8fcf-4ddd-acb1-6553be3d1dc9,
>> jobId=076f54be461-65c907a3-8fcf-4ddd-acb1-6553be3d1dc9,
>> nodeId=236a47e9-7fdb-464e-be44-b24d0942d75c, isJobDone=false],
>> jobCtx=GridJobContextImpl
>> [jobId=076f54be461-65c907a3-8fcf-4ddd-acb1-6553be3d1dc9, timeoutObj=null,
>> attrs={}], node=TcpDiscoveryNode [id=236a47e9-7fdb-464e-be44-b24d0942d75c,
>> addrs=[10.23.8.165], sockAddrs=[zhkdlp1712.int.clsa.com/10.23.8.165:0],
>> discPort=0, order=37, intOrder=27, lastExchangeTime=1533148447088,
>> loc=false, ver=2.3.0#20180518-sha1:02cf6abf, isClient=true], ex=class
>> o.a.i.IgniteException: Service not found: blaze/hsbc, hasRes=true,
>> isCancelled=false, isOccupied=true]
>>
>> org.apache.ignite.IgniteException: Remote job threw user exception (override
>> or implement ComputeTask.result(..) method if you would like to have
>> automatic failover for this exception).
>>
>> at
>> org.apache.ignite.compute.ComputeTaskAdapter.result(ComputeTaskAdapter.java:101)
>> ~[liquid-logic.jar:2.0.10]
>>
>> at
>> org.apache.ignite.internal.processors.task.GridTaskWorker$5.apply(GridTaskWorker.java:1047)
>> [liquid-logic.jar:2.0.10]
>>
>> at
>> org.apache.ignite.internal.processors.task.GridTaskWorker$5.apply(GridTaskWorker.java:1040)
>> [liquid-logic.jar:2.0.10]
>>
>> at
>> org.apache.ignite.internal.util.IgniteUtils.wrapThreadLoader(IgniteUtils.java:6663)
>> [liquid-logic.jar:2.0.10]
>>
>> at
>> org.apache.ignite.internal.processors.task.GridTaskWorker.result(GridTaskWorker.java:1040)
>> [liquid-logic.jar:2.0.10]
>>
>> at
>> org.apache.ignite.internal.processors.task.GridTaskWorker.onResponse(GridTaskWorker.java:858)
>> [liquid-logic.jar:2.0.10]
>>
>> at
>> org.apache.ignite.internal.processors.task.GridTaskProcessor.processJobExecuteResponse(GridTaskProcessor.java:1066)
>> [liquid-logic.jar:2.0.10]
>>
>> at
>> org.apache.ignite.internal.processors.task.GridTaskProcessor$JobMessageListener.onMessage(GridTaskProcessor.java:1301)
>> [liquid-logic.jar:2.0.10]
>>
>> at
>> org.apache
Re: Using compute().call from a Service has P2P class loading feature?
Hi! Unfortunately, peer class loading doesn't work properly for Service Grid. Here is a task with the same issue [1]. I've done some tests and according to results, the peer class loading works in case of service's classes propagation from a coordinator to others node, but not vice versa. Possibly it will be implemented in future releases. [1] https://issues.apache.org/jira/browse/IGNITE-975 On Fri, Sep 14, 2018 at 8:59 PM xero wrote: > > Hello, > I have a question about p2p class loading. > > My topology is 1 dedicated server, 1 client. > I have deployed a Service in the ignite client node (selecting clusterGroup > forClients) from which I'm trying to execute a compute() to the server node. > The IgniteCallable that I'm sending to call() is referencing User's classes > I would expect that the p2p class loading will transfer that class to the > server node (As the service is running in a client node, the classpath has > the mentioned classes) > > This is not working. I'm getting ClassNotFoundException for the user class. > Should this be working? > > Thanks! > > > > -- > Sent from: http://apache-ignite-users.70518.x6.nabble.com/ -- Best Regards, Vyacheslav D.
Re: Ignite 2.1 build script issue
Hi Carsten. I had got such issue earlier. The build procedure has been changed for the release 2.1 Take a look in DEVNOTES.txt There are two mandatory steps: 1) mvn clean install -Pall-java,all-scala,licenses -DskipTests 2) mvn initialize -Prelease 2017-07-28 20:10 GMT+03:00 Carsten : > Hello guys, > > I am trying to build Ignite 2.1 on Linux, but > > "mvn clean package -DskipTests" > > does not seem to generate the target anymore. Worked in previous version. > > Anybody else seeing this issue. What am I doing wrong? > > Thanks, > > Carsten > > > > -- Best Regards, Vyacheslav D.
Re: Ignite 2.1?
As far as I know, It will be shortly after the end of the vote. [1] Of course only in case of vote success. Vote started yesterday, and must finish tomorrow. Let's hope to see the new release by the end of this week. [1] http://apache-ignite-developers.2346864.n4.nabble.com/VOTE-Apache-Ignite-2-1-0-RC2-td19767.html 2017-07-19 10:12 GMT+03:00 Muthu : > Folks, > > Any one knows when 2.1 would be coming out? > > As per this, the release date is July 17th...this past Monday, > > https://cwiki.apache.org/confluence/display/IGNITE/Apache+Ignite+2.1 > > Regards, > Muthu > > -- The real danger with modern technology isn't that machines will begin > to think like people, but that people will begin to think like machines. > -- Faith is to believe what you do not see; the reward of this faith is to > see what you believe. > -- Best Regards, Vyacheslav D.
Re: Offheap and max memory
> It looks like documentation is misleading. I partially agree. CacheConfiguration is validated during creation of a cache (when you call a ignite.getOrCreateCache) and some mismatches like OFFHEAP mode with offHeapMaxMemory equlas -1 will be resolved. Maybe it makes sense to add explanation to 'offHeapMaxMemory' field in Ignite 1.9. As far as I know Ignite-2.0 is moving to full-off-heap page memory model, and CacheConfiguration will be remade, including the removal of 'offHeapMaxMemory' field. 2017-04-27 2:39 GMT+03:00 javastuff@gmail.com : > It looks like documentation is misleading. > > Tried test program - > > - without setting offHeapMaxMemory, getOffHeapMaxMemory returns 0. > - Setting offHeapMaxMemory=-1, getOffHeapMaxMemory returns 0. > > Thanks, > -Sam > > > > > -- > View this message in context: http://apache-ignite-users. > 70518.x6.nabble.com/Offheap-and-max-memory-tp12275p12277.html > Sent from the Apache Ignite Users mailing list archive at Nabble.com. > -- Best Regards, Vyacheslav
Re: Offheap and max memory
Hi,
I've looked at sources.
If memMode == OFFHEAP_TIERED, but offHeapMaxMemory < 0
then offHeapMaxMemory will be setted to unlimited '0'.
Try to debug after starting a cache, and look at
IgniteCache#getConfiguration(CacheConfiguration.class) and
getOffHeapMaxMemory, it must be '0'
2017-04-26 21:16 GMT+03:00 javastuff@gmail.com
:
> Hi
>
> I am using Partitioned, Atomic, OffHeap cache, creating cache
> pragmatically.
>
> Recently noticed offHeapMaxMemory is not set because of glitch in my
> configuration and program. Based on java doc default offHeapMaxMemory value
> is -1, specified by DFLT_OFFHEAP_MEMORY constant which means that off-heap
> storage is disabled by default.
>
> I was not facing any issues for put, get and etc operation, so wondering
> where does data gets cached? OffHeap/OnHeap.
>
> / try (Ignite ignite = Ignition.start("config/example-ignite.xml"))
> {
> CacheConfiguration cacheCfg = new
> CacheConfiguration<>();
> cacheCfg.setName(CACHE_NAME);
> cacheCfg.setCacheMode(CacheMode.PARTITIONED);
> cacheCfg.setAtomicityMode(CacheAtomicityMode.ATOMIC);
> cacheCfg.setMemoryMode(CacheMemoryMode.OFFHEAP_TIERED);
>
> try (IgniteCache cache =
> ignite.getOrCreateCache(cacheCfg)) {
> putGet(cache);
> putAllGetAll(cache);
> } finally {
> ignite.destroyCache(CACHE_NAME);
> }
> }/
>
> Thanks,
> -Sam
>
>
>
> --
> View this message in context: http://apache-ignite-users.
> 70518.x6.nabble.com/Offheap-and-max-memory-tp12275.html
> Sent from the Apache Ignite Users mailing list archive at Nabble.com.
>
--
Best Regards, Vyacheslav
