[
https://issues.apache.org/jira/browse/IGNITE-7108?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16448404#comment-16448404
]
Max Shonichev commented on IGNITE-7108:
---------------------------------------
Same goes for update scenario. As we don't have rolling upgrade in the apache
ignite, IMO, we should stop running nodes but do not restart them automatically
after upgrade.
in case if some nodes of old version are currently running, print banner
{noformat}
===========================================================================
WARNING: All local running Apache Ignite nodes will be stopped.
===========================================================================
{noformat}
and also, no matter if nodes are running or not, print a banner with text:
{noformat}
===========================================================================
WARNING: To update Apache Ignite cluster you must update all cluster nodes
before starting grid.
===========================================================================
{noformat}
> Apache Ignite 2.5 RPM and DEB packages
> --------------------------------------
>
> Key: IGNITE-7108
> URL: https://issues.apache.org/jira/browse/IGNITE-7108
> Project: Ignite
> Issue Type: New Feature
> Components: binary
> Reporter: Peter Ivanov
> Assignee: Peter Ivanov
> Priority: Critical
> Labels: important
> Fix For: 2.5
>
>
> # (/) Update RPM build process to unify with DEB build.
> # (/) Prepare build of DEB package (using architecture and layout from RPM
> package).
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
