ignite-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Valentin Kulichenko (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (IGNITE-3056) Service implementation class is required even if it's not expected to be deployed on current node
Date Wed, 11 May 2016 03:22:12 GMT

    [ https://issues.apache.org/jira/browse/IGNITE-3056?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15279433#comment-15279433
] 

Valentin Kulichenko commented on IGNITE-3056:
---------------------------------------------

Agree with Semen. Adding new method looks dirty, because it's really hard to understand its
purpose. System property is better, but if it's {{false}} by default, we should make sure
that {{true}} value on new nodes and no value on old nodes are compatible and pass the consistency
check.

> 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)

Mime
View raw message