[
https://issues.apache.org/jira/browse/TRAFODION-3164?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16569450#comment-16569450
]
ASF GitHub Bot commented on TRAFODION-3164:
-------------------------------------------
Github user asfgit closed the pull request at:
https://github.com/apache/trafodion/pull/1672
> Phase out existing mxosrvrs on-demand
> -------------------------------------
>
> Key: TRAFODION-3164
> URL: https://issues.apache.org/jira/browse/TRAFODION-3164
> Project: Apache Trafodion
> Issue Type: Improvement
> Components: connectivity-mxosrvr
> Affects Versions: 2.1-incubating
> Reporter: Hans Zeller
> Assignee: Hans Zeller
> Priority: Major
> Fix For: 2.3
>
>
> In some cases, it would be very helpful if we could tell the DCS component to
> restart all of its mxosrvrs at the next opportunity.
> There are several reasons why one would want this:
> * We may have installed a temporary patch to the executable file and want to
> phase out any mxosrvrs using the old executable.
> * We may have changed the system defaults table and want all the mxosrvrs to
> pick up new system defaults
> * We may want to free up all the resources like ESPs, UDR servers, etc. held
> by the mxosrvrs
> With "restart at the next opportunity", what I mean by that is to restart all
> the servers in the AVAILABLE state immediately. The servers that are
> currently connected should be restarted once they become available after
> disconnecting.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
