[
https://issues.apache.org/jira/browse/IGNITE-3056?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15278050#comment-15278050
]
Semen Boikov commented on IGNITE-3056:
--------------------------------------
Artem,
I reviewed your fix, did several changes, please take a look.
Instead of adding new method 'deployLazy' let's add special system property,
something like 'service_compatibility_mode'.('false' by default). If this
property is 'true' then old ServiceConfiguration class is used, otherwise we
use new 'lazy' configuration class. All nodes in cluster should have the same
value of this propery (see for example how simila logic is implemented for
IgniteSystemProperties.IGNITE_OPTIMIZED_MARSHALLER_USE_DEFAULT_SUID ).
Thanks!
> Service implementation class is required even if it's not expected to be
> deployed on current node
> -------------------------------------------------------------------------------------------------
>
> Key: IGNITE-3056
> URL: https://issues.apache.org/jira/browse/IGNITE-3056
> Project: Ignite
> Issue Type: Bug
> Components: managed services
> Affects Versions: 1.5.0.final
> Reporter: Valentin Kulichenko
> Assignee: Artem Shutak
> Labels: community, customer, important
> Fix For: 1.6
>
>
> Currently the service instance is deserialized as part of
> {{GridServiceDeployment}} and {{GridServiceAssignment}} classes. Need to
> check if it's possible to deserialize only node filter first, and then
> deserialize the service itself only if needed. This will allow to use cluster
> groups with services and deploy the classes accordingly.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
