ignite-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Michael Griggs (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (IGNITE-6069) Service versioning
Date Tue, 28 Nov 2017 09:45:00 GMT

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

Michael Griggs commented on IGNITE-6069:
----------------------------------------

It is essential that server nodes must need to be stopped in order to deploy a new service.
 This implies that we have peer-class loading for Service interfaces and implementations.

> Service versioning
> ------------------
>
>                 Key: IGNITE-6069
>                 URL: https://issues.apache.org/jira/browse/IGNITE-6069
>             Project: Ignite
>          Issue Type: New Feature
>          Components: general
>    Affects Versions: 2.1
>            Reporter: Ilya Lantukh
>            Assignee: Ilya Lantukh
>
> Make services upgradable -again-. 
> Main points:
> - compute binary type ID by (classname + version)
> - use serialVersionUuid as version ( ?)
> - all service instances with the same name must have the same version
> - make ServiceProxy aware of versions and upgrade process, pause requests while service
is being upgraded
> - extend Service interface (UpgradableService?) - add ability to collect state of previous
version before start.
> Once the feature is implemented, it has to be documented extensively. The ticket must
not be closed until this happens.



--
This message was sent by Atlassian JIRA
(v6.4.14#64029)

Mime
View raw message