ignite-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Semen Boikov (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (IGNITE-3483) Regression: service is being deployed on a client
Date Mon, 18 Jul 2016 10:11:20 GMT

     [ https://issues.apache.org/jira/browse/IGNITE-3483?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Semen Boikov resolved IGNITE-3483.
----------------------------------
    Resolution: Won't Fix

It is not a regression, it always worked in this way - if service should not be deployed on
client node then this filtering should be implemented in ServiceConfiguration.nodeFitler.
Before there was another bug, so client did not deploy service on node start.

> Regression: service is being deployed on a client
> -------------------------------------------------
>
>                 Key: IGNITE-3483
>                 URL: https://issues.apache.org/jira/browse/IGNITE-3483
>             Project: Ignite
>          Issue Type: Bug
>            Reporter: Denis Magda
>            Assignee: Semen Boikov
>         Attachments: GridServiceClientNodeTest.java
>
>
> Seems that we got a regression. Presently if to start a service (defined in the configuration
of the server node) then it will be automatically deployed on client nodes as well. 
> I got the following exception on the client 
> {code}
> [14:44:45,074][SEVERE][srvc-deploy-#41%null%][GridServiceProcessor] Failed to initialize
service (service will not be deployed): FileLoaderServiceImpl
> class org.apache.ignite.binary.BinaryInvalidTypeException: be.ing.tds.shielding.core.service.FileLoaderServiceImpl
> 	at org.apache.ignite.internal.binary.BinaryContext.descriptorForTypeId(BinaryContext.java:636)
> 	at org.apache.ignite.internal.binary.BinaryReaderExImpl.deserialize(BinaryReaderExImpl.java:1452)
> 	at org.apache.ignite.internal.binary.GridBinaryMarshaller.deserialize(GridBinaryMarshaller.java:298)
> 	at org.apache.ignite.internal.binary.BinaryMarshaller.unmarshal(BinaryMarshaller.java:112)
> 	at org.apache.ignite.internal.processors.service.GridServiceProcessor.copyAndInject(GridServiceProcessor.java:1119)
> 	at org.apache.ignite.internal.processors.service.GridServiceProcessor.redeploy(GridServiceProcessor.java:1040)
> 	at org.apache.ignite.internal.processors.service.GridServiceProcessor.processAssignment(GridServiceProcessor.java:1662)
> 	at org.apache.ignite.internal.processors.service.GridServiceProcessor.onSystemCacheUpdated(GridServiceProcessor.java:1352)
> 	at org.apache.ignite.internal.processors.service.GridServiceProcessor.access$300(GridServiceProcessor.java:106)
> 	at org.apache.ignite.internal.processors.service.GridServiceProcessor$ServiceEntriesListener$1.run0(GridServiceProcessor.java:1319)
> 	at org.apache.ignite.internal.processors.service.GridServiceProcessor$BusyRunnable.run(GridServiceProcessor.java:1709)
> 	at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
> 	at java.util.concurrent.FutureTask.run(FutureTask.java:266)
> 	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
> 	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
> 	at java.lang.Thread.run(Thread.java:745)
> Caused by: java.lang.ClassNotFoundException: be.ing.tds.shielding.core.service.FileLoaderServiceImpl
> 	at java.net.URLClassLoader.findClass(URLClassLoader.java:381)
> 	at java.lang.ClassLoader.loadClass(ClassLoader.java:424)
> 	at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:331)
> 	at java.lang.ClassLoader.loadClass(ClassLoader.java:357)
> 	at java.lang.Class.forName0(Native Method)
> 	at java.lang.Class.forName(Class.java:348)
> 	at org.apache.ignite.internal.util.IgniteUtils.forName(IgniteUtils.java:8263)
> 	at org.apache.ignite.internal.MarshallerContextAdapter.getClass(MarshallerContextAdapter.java:185)
> 	at org.apache.ignite.internal.binary.BinaryContext.descriptorForTypeId(BinaryContext.java:627)
> 	... 15 more
> {code}
> Attaching the test. Run {{testNoDeployOnClient}} test to see the issue. Present test
check that {{ServiceDescriptors.topologySnapshot}} is 0 for a client node. However it's 1.

> I've checked previous version and saw that {{ServiceDescriptors.topologySnapshot}} is
not 1 as well for the client. However after debugging the sources I saw that no deploying
happened on the client in any case meaning that this {{ServiceDescriptors.topologySnapshot}}
 is broken as well.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message